bgpreport

Network · data from 2026-11-12

AS45731 ARDH-AS-ID - ARDH GLOBAL INDONESIA, PT

Registry name: ARDH-AS-ID - ARDH GLOBAL INDONESIA, PT, ID · not in PeeringDB

11IPv4 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
18Route objects not announced registered with origin AS45731, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45731, 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.229.248.0/23 Valid Other IRR onlyRADB 673 100% 70
43.229.250.0/23 Valid Other IRR onlyRADB 673 100% 70
103.6.52.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
103.6.54.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
113.20.28.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
113.20.30.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
180.235.148.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
180.235.149.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
180.235.150.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
180.235.151.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.20.190.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
2001:df0:bc::/48 Valid Other IRR onlyNTTCOM, RADB 636 100% 70

AS-SET

AS45731 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 30 are in fix.csv.

  • Route object: RIR12
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
Route object: RIR43.229.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.229.250.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.6.52.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.6.54.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR113.20.28.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR113.20.30.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.235.148.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.235.149.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.235.150.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.235.151.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.20.190.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2001:df0:bc::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

43.229.248.0/22RADBValid
43.229.248.0/24APNICValid
43.229.249.0/24APNICValid
43.229.250.0/24APNICValid
43.229.251.0/24APNICValid
103.6.52.0/22NTTCOM, RADBValid
103.6.52.0/24NTTCOM, RADBValid
103.6.53.0/24NTTCOM, RADBValid
103.6.54.0/24NTTCOM, RADBValid
103.6.55.0/24NTTCOM, RADBValid
113.20.28.0/22NTTCOM, RADBValid
113.20.28.0/24NTTCOM, RADBValid
113.20.29.0/24NTTCOM, RADBValid
113.20.30.0/24NTTCOM, RADBValid
113.20.31.0/24NTTCOM, RADBValid
180.235.148.0/22NTTCOM, RADBValid
180.235.148.0/23NTTCOM, RADBValid
180.235.150.0/23NTTCOM, RADBValid

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.