bgpreport

Network · data from 2026-11-12

AS4711 Intec

Registry name: INTEC - INTEC Inc., JP · PeeringDB

20IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
21No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS4711, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS4711, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

203.139.144.0/21 No ROA Other IRR onlyJPIRR 673 100% 67
203.139.152.0/21 No ROA Other IRR onlyJPIRR 673 100% 67
101.53.96.0/23 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
101.53.98.0/23 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
101.53.112.0/20 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
101.53.112.0/22 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
101.53.116.0/22 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
101.53.120.0/22 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
101.53.124.0/22 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
150.48.0.0/17 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
150.48.0.0/18 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
150.48.64.0/18 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
202.222.64.0/19 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
202.222.64.0/20 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
202.222.80.0/20 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
202.222.96.0/20 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
202.222.96.0/21 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
202.222.104.0/21 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
203.139.144.0/20 No ROA Other IRR onlyJPIRR, NTTCOM 671 100% 67
101.53.96.0/22 No ROA Other IRR onlyJPIRR, NTTCOM 669 99% 67
2406:1000::/32 No ROA Other IRR onlyJPIRR, NTTCOM 631 99% 70

AS-SET

AS4711's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 58 are in fix.csv.

  • ROA: none21
  • Route object: RIR21
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none203.139.144.0/21No ROA covers it. Add a ROA for AS4711, maxLength 21.673 of 673
Route object: RIR203.139.144.0/21Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none203.139.152.0/21No ROA covers it. Add a ROA for AS4711, maxLength 21.673 of 673
Route object: RIR203.139.152.0/21Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
ROA: none101.53.96.0/23No ROA covers it. Add a ROA for AS4711, maxLength 23.671 of 673
Route object: RIR101.53.96.0/23Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none101.53.98.0/23No ROA covers it. Add a ROA for AS4711, maxLength 23.671 of 673
Route object: RIR101.53.98.0/23Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none101.53.112.0/20No ROA covers it. Add a ROA for AS4711, maxLength 20.671 of 673
Route object: RIR101.53.112.0/20Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none101.53.112.0/22No ROA covers it. Add a ROA for AS4711, maxLength 22.671 of 673
Route object: RIR101.53.112.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none101.53.116.0/22No ROA covers it. Add a ROA for AS4711, maxLength 22.671 of 673
Route object: RIR101.53.116.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none101.53.120.0/22No ROA covers it. Add a ROA for AS4711, maxLength 22.671 of 673
Route object: RIR101.53.120.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none101.53.124.0/22No ROA covers it. Add a ROA for AS4711, maxLength 22.671 of 673
Route object: RIR101.53.124.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none150.48.0.0/17No ROA covers it. Add a ROA for AS4711, maxLength 17.671 of 673
Route object: RIR150.48.0.0/17Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none150.48.0.0/18No ROA covers it. Add a ROA for AS4711, maxLength 18.671 of 673
Route object: RIR150.48.0.0/18Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none150.48.64.0/18No ROA covers it. Add a ROA for AS4711, maxLength 18.671 of 673
Route object: RIR150.48.64.0/18Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none202.222.64.0/19No ROA covers it. Add a ROA for AS4711, maxLength 19.671 of 673
Route object: RIR202.222.64.0/19Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none202.222.64.0/20No ROA covers it. Add a ROA for AS4711, maxLength 20.671 of 673
Route object: RIR202.222.64.0/20Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none202.222.80.0/20No ROA covers it. Add a ROA for AS4711, maxLength 20.671 of 673
Route object: RIR202.222.80.0/20Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none202.222.96.0/20No ROA covers it. Add a ROA for AS4711, maxLength 20.671 of 673
Route object: RIR202.222.96.0/20Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none202.222.96.0/21No ROA covers it. Add a ROA for AS4711, maxLength 21.671 of 673
Route object: RIR202.222.96.0/21Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none202.222.104.0/21No ROA covers it. Add a ROA for AS4711, maxLength 21.671 of 673
Route object: RIR202.222.104.0/21Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none203.139.144.0/20No ROA covers it. Add a ROA for AS4711, maxLength 20.671 of 673
Route object: RIR203.139.144.0/20Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none101.53.96.0/22No ROA covers it. Add a ROA for AS4711, maxLength 22.669 of 673
Route object: RIR101.53.96.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.669 of 673
ROA: none2406:1000::/32No ROA covers it. Add a ROA for AS4711, maxLength 32.631 of 636
Route object: RIR2406:1000::/32Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.631 of 636

Route objects not announced

Route objects with origin AS4711 whose prefix no peer sees AS4711 announce. Many are kept on purpose (backup routes, space announced only in some places).

101.53.96.0/24JPIRR, RADBNo ROA
101.53.97.0/24JPIRR, RADBNo ROA
101.53.98.0/24JPIRR, RADBNo ROA
101.53.99.0/24JPIRR, RADBNo ROA
101.53.112.0/23NTTCOMNo ROA
101.53.112.0/24JPIRR, NTTCOM, RADBNo ROA
101.53.113.0/24JPIRR, NTTCOM, RADBNo ROA
202.222.74.0/23NTTCOMNo ROA
202.222.83.0/24NTTCOMNo ROA
202.222.86.0/23NTTCOMNo ROA
202.222.100.0/23NTTCOMNo ROA
202.222.102.0/23NTTCOMNo ROA
2406:1000::/34JPIRRNo ROA
2406:1000:4000::/34JPIRRNo ROA
2406:1000:8000::/34JPIRRNo ROA
2406:1000:c000::/34JPIRRNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.