bgpreport

Network · data from 2026-11-12

AS131778 Dian Nuswantoro Teknologi

Registry name: DINUSTECH-AS-ID - PT Dian Nuswantoro Teknologi, ID · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS131778, seen from no peer

Announced routes

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

2401:7aa0::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 70
103.30.0.0/23 Valid Other IRR onlyALTDB, RADB 673 100% 70
103.30.0.0/24 Valid Other IRR onlyALTDB, NTTCOM, RADB 673 100% 70
103.30.1.0/24 Valid Other IRR onlyALTDB, NTTCOM, RADB 673 100% 70
103.30.2.0/23 Valid Other IRR onlyALTDB 673 100% 70
103.30.2.0/24 Valid Other IRR onlyALTDB, NTTCOM, RADB 673 100% 70
103.30.3.0/24 Valid Other IRR onlyALTDB, NTTCOM, RADB 673 100% 70
2001:df0:229::/48 Valid Other IRR onlyALTDB 636 100% 67
103.30.0.0/22 Valid RIR databaseALTDB, APNIC, RADB 673 100% 70
103.246.107.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 70

AS-SET

AS131778'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 9 are in fix.csv.

  • ROA: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none2401:7aa0::/32No ROA covers it. Add a ROA for AS131778, maxLength 32.635 of 636
Route object: RIR2401:7aa0::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR103.30.0.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.30.0.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.30.1.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.30.2.0/23Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.30.2.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.30.3.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:df0:229::/48Route object only in ALTDB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS131778 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.