bgpreport

Network · data from 2026-11-12

AS45320 DEPKOMINFO-AS-ID - Departemen Komunikasi dan Informasi Republik Indonesia

Registry name: DEPKOMINFO-AS-ID - Departemen Komunikasi dan Informasi Republik Indonesia, ID · not in PeeringDB

6IPv4 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
7No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS45320, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45320, 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.
103.8.76.0/24 No ROA Other IRR onlyRADB 673 100% 69
103.8.77.0/24 No ROA Other IRR onlyRADB 673 100% 69
202.89.116.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
202.89.117.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
2001:df2:a600::/48 No ROA Other IRR onlyRADB 635 100% 67
202.89.116.0/23 No ROA RIR databaseAPNIC, NTTCOM 673 100% 69
103.8.76.0/23 No ROA RIR databaseAPNIC, RADB 672 100% 67

AS-SET

AS45320 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 12 are in fix.csv.

  • ROA: none7
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none103.8.76.0/24No ROA covers it. Add a ROA for AS45320, maxLength 24.673 of 673
Route object: RIR103.8.76.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.8.77.0/24No ROA covers it. Add a ROA for AS45320, maxLength 24.673 of 673
Route object: RIR103.8.77.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.89.116.0/24No ROA covers it. Add a ROA for AS45320, maxLength 24.672 of 673
Route object: RIR202.89.116.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.89.117.0/24No ROA covers it. Add a ROA for AS45320, maxLength 24.672 of 673
Route object: RIR202.89.117.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2001:df2:a600::/48No ROA covers it. Add a ROA for AS45320, maxLength 48.635 of 636
Route object: RIR2001:df2:a600::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none202.89.116.0/23No ROA covers it. Add a ROA for AS45320, maxLength 23.673 of 673
ROA: none103.8.76.0/23No ROA covers it. Add a ROA for AS45320, maxLength 23.672 of 673

Route objects not announced

Every route object with origin AS45320 is announced.

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.