bgpreport

Network · data from 2026-11-12

AS17671 Jetcoms Netindo AS17671

Registry name: ASN-JETCOMS - JETCOMS-ID Autonomous system, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17671, 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.

114.199.81.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
114.199.84.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
114.199.86.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
114.199.88.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
114.199.90.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
114.199.91.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
114.199.94.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
114.199.95.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
202.47.68.0/24 Valid Other IRR onlyNTTCOM, REACH 673 100% 70
202.47.70.0/24 Valid Other IRR onlyNTTCOM, REACH 673 100% 70
202.47.72.0/24 Valid Other IRR onlyNTTCOM, REACH 673 100% 70
202.47.74.0/24 Valid Other IRR onlyNTTCOM, REACH 673 100% 70
202.47.77.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
202.47.78.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 70
202.52.8.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
202.58.220.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
202.58.222.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
114.199.89.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 35 5%low visibility 29
202.47.71.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 35 5%low visibility 29
202.58.217.0/24 Valid Other IRR onlyNTTCOM, RADB 2 0%low visibility 2

AS-SET

AS17671'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 95 are in fix.csv.

  • Route object: RIR20
  • Route object: not announced75
ChangePrefix or setDetailFull-table peers
Route object: RIR114.199.81.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.84.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.86.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.88.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.90.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.91.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.94.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.95.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.47.68.0/24Route object only in NTTCOM, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.47.70.0/24Route object only in NTTCOM, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.47.72.0/24Route object only in NTTCOM, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.47.74.0/24Route object only in NTTCOM, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.47.77.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.47.78.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.52.8.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.220.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.222.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.89.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.35 of 673
Route object: RIR202.47.71.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.35 of 673
Route object: RIR202.58.217.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

114.199.80.0/20NTTCOM, RADB, REACHValid
114.199.80.0/21NTTCOM, RADBValid
114.199.80.0/22NTTCOM, RADBValid
114.199.80.0/23NTTCOM, RADBValid
114.199.80.0/24NTTCOM, RADB, REACHValid
114.199.82.0/23NTTCOM, RADBValid
114.199.82.0/24NTTCOM, RADB, REACHValid
114.199.83.0/24NTTCOM, RADB, REACHValid
114.199.84.0/22NTTCOM, RADBValid
114.199.84.0/23NTTCOM, RADBValid
114.199.85.0/24NTTCOM, RADB, REACHValid
114.199.86.0/23NTTCOM, RADBValid
114.199.87.0/24NTTCOM, RADB, REACHValid
114.199.88.0/21NTTCOM, RADBValid
114.199.88.0/22NTTCOM, RADBValid
114.199.88.0/23NTTCOM, RADBValid
114.199.90.0/23NTTCOM, RADBValid
114.199.92.0/22NTTCOM, RADBValid
114.199.92.0/23NTTCOM, RADBValid
114.199.92.0/24NTTCOM, RADB, REACHValid
114.199.93.0/24NTTCOM, RADB, REACHValid
114.199.94.0/23NTTCOM, RADBValid
117.103.8.0/21NTTCOM, RADBNo ROA
202.47.64.0/20NTTCOM, RADB, REACHValid
202.47.64.0/21NTTCOM, RADBValid
202.47.64.0/22NTTCOM, RADBValid
202.47.64.0/23NTTCOM, RADBValid
202.47.64.0/24NTTCOM, REACHValid
202.47.65.0/24NTTCOM, REACHValid
202.47.66.0/23NTTCOM, RADBValid
202.47.66.0/24NTTCOM, RADB, REACHValid
202.47.67.0/24NTTCOM, REACHValid
202.47.68.0/22NTTCOM, RADBValid
202.47.68.0/23NTTCOM, RADBValid
202.47.69.0/24NTTCOM, REACHValid
202.47.70.0/23NTTCOM, RADBValid
202.47.72.0/21NTTCOM, RADBValid
202.47.72.0/22NTTCOM, RADBValid
202.47.72.0/23NTTCOM, RADBValid
202.47.73.0/24NTTCOM, REACHValid
202.47.74.0/23NTTCOM, RADBValid
202.47.75.0/24NTTCOM, REACHValid
202.47.76.0/22NTTCOM, RADBValid
202.47.76.0/23NTTCOM, RADBValid
202.47.76.0/24NTTCOM, RADB, REACHValid
202.47.78.0/23NTTCOM, RADBValid
202.47.79.0/24NTTCOM, REACHValid
202.52.8.0/23NTTCOMValid
202.52.8.0/24NTTCOMValid
202.52.9.0/24NTTCOMValid
202.52.10.0/23NTTCOMValid
202.52.10.0/24NTTCOMValid
202.52.11.0/24NTTCOMValid
202.58.216.0/21NTTCOM, RADBValid
202.58.216.0/22NTTCOM, RADBValid
202.58.216.0/23NTTCOM, RADBValid
202.58.216.0/24NTTCOM, RADBValid
202.58.218.0/23NTTCOM, RADBValid
202.58.218.0/24NTTCOM, RADBValid
202.58.219.0/24NTTCOM, RADBValid
202.58.220.0/22NTTCOM, RADBValid
202.58.220.0/23NTTCOM, RADBValid
202.58.221.0/24NTTCOM, RADBValid
202.58.222.0/23NTTCOM, RADBValid
202.58.223.0/24NTTCOM, RADBValid
202.67.32.0/20NTTCOM, RADBNo ROA
202.93.224.0/20NTTCOM, RADBNo ROA
202.93.240.0/21NTTCOM, RADBNo ROA
202.123.224.0/20NTTCOM, RADBNo ROA
202.148.0.0/19NTTCOM, RADBNo ROA
202.159.0.0/17NTTCOM, RADBNo ROA
202.160.254.0/24NTTCOM, RADBNo ROA
202.180.48.0/21RADBNo ROA
203.201.160.0/20NTTCOM, RADBNo ROA
2402:fc00::/32RADBNo 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.