bgpreport

Network · data from 2026-11-12

AS38764 POLRI-AS-ID - MARKAS BESAR KEPOLISIAN REPUBLIK INDONESIA

Registry name: POLRI-AS-ID - MARKAS BESAR KEPOLISIAN REPUBLIK INDONESIA, ID · not in PeeringDB

8IPv4 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
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS38764, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38764, 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.
120.29.225.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
120.29.228.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
120.29.229.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
120.29.230.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
120.29.224.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
120.29.226.0/24 Valid Other IRR onlyNTTCOM, RADB 658 98% 69
120.29.227.0/24 Valid Other IRR onlyNTTCOM, RADB 658 98% 69
120.29.231.0/24 Valid Other IRR onlyNTTCOM, RADB 657 98% 69

AS-SET

AS38764 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 15 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: RIR120.29.225.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.29.228.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.29.229.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.29.230.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.29.224.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR120.29.226.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.658 of 673
Route object: RIR120.29.227.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.658 of 673
Route object: RIR120.29.231.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.657 of 673

Route objects not announced

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

120.29.224.0/21APNIC, NTTCOM, RADBValid
120.29.224.0/22NTTCOM, RADBValid
120.29.224.0/23NTTCOM, RADBValid
120.29.226.0/23NTTCOM, RADBValid
120.29.228.0/22NTTCOM, RADBValid
120.29.228.0/23NTTCOM, RADBValid
120.29.230.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.