bgpreport

Network · data from 2026-11-12

AS58397 INFINYS-AS-ID - PT Infinys System Indonesia

Registry name: INFINYS-AS-ID - PT Infinys System Indonesia, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58397, 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.
43.245.180.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
43.245.181.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
43.245.182.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
43.245.183.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.23.20.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.23.21.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.23.22.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.23.23.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.188.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.189.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.190.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.191.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.192.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.193.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.194.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.195.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.204.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.205.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.206.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
103.41.207.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.44.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.45.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.46.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.144.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.145.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.146.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.147.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.148.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.149.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.150.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.151.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 69
117.53.47.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 670 100% 69
2001:df0:f800::/48 Valid Other IRR onlyRADB 635 100% 70
43.224.16.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
43.224.18.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
43.224.19.0/24 Valid RIR databaseAPNIC, RADB, REACH 673 100% 69
103.43.44.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 69
103.43.45.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 69
103.43.46.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 69
103.43.47.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 69

AS-SET

AS58397 isn't in PeeringDB, where networks name their 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 66 are in fix.csv.

  • Route object: RIR33
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
Route object: RIR43.245.180.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR43.245.181.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR43.245.182.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR43.245.183.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.23.20.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.23.21.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.23.22.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.23.23.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.188.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.189.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.190.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.191.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.192.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.193.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.194.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.195.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.204.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.205.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.206.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR103.41.207.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.44.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.45.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.46.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.144.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.145.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.146.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.147.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.148.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.149.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.150.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.151.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR117.53.47.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.670 of 673
Route object: RIR2001:df0:f800::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

43.224.16.0/22APNICValid
43.224.17.0/24APNIC, RADBValid
43.245.180.0/22NTTCOM, RADBValid
43.245.180.0/23NTTCOM, RADBValid
43.245.182.0/23NTTCOM, RADBValid
103.23.20.0/22APNIC, NTTCOMValid
103.23.20.0/23NTTCOM, RADBValid
103.23.22.0/23NTTCOM, RADBValid
103.41.188.0/22APNIC, NTTCOM, RADBValid
103.41.188.0/23NTTCOM, RADBValid
103.41.190.0/23NTTCOM, RADBValid
103.41.192.0/22APNIC, NTTCOM, RADBValid
103.41.192.0/23NTTCOM, RADBValid
103.41.194.0/23NTTCOM, RADBValid
103.41.204.0/22APNIC, NTTCOM, RADBNo ROA
103.41.204.0/23NTTCOM, RADBNo ROA
103.41.206.0/23NTTCOM, RADBNo ROA
103.43.44.0/22APNIC, NTTCOM, RADBValid
117.53.44.0/22NTTCOM, RADBValid
117.53.44.0/23NTTCOM, RADBValid
117.53.46.0/23NTTCOM, RADBValid
117.53.144.0/22NTTCOM, RADBValid
117.53.144.0/23NTTCOM, RADBValid
117.53.146.0/23NTTCOM, RADBValid
117.53.148.0/22NTTCOM, RADBNo ROA
117.53.148.0/23NTTCOM, RADBNo ROA
117.53.150.0/23NTTCOM, RADBNo ROA
117.102.155.0/24NTTCOMNo ROA
117.102.246.0/24REACHInvalid: origin
117.102.247.0/24REACHInvalid: origin
117.102.248.0/22REACHInvalid: origin
117.102.255.0/24REACHInvalid: origin
2407:180::/32APNICValid

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.