bgpreport

Network · data from 2026-11-12

AS134654 Datautama Dinamika NAP

Registry name: DATAUTAMA-NAP-IX - PT Datautama Dinamika - NAP, ID · PeeringDB

5IPv4 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
1Route objects not announced registered with origin AS134654, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134654, 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.147.254.0/24 Valid Other IRR onlyRADB 670 100% 66
103.147.255.0/24 Valid Other IRR onlyRADB 670 100% 67
175.184.238.0/23 Valid Other IRR onlyRADB 670 100% 67
2405:c5c0:ff00::/40 Valid Other IRR onlyRADB 636 100% 69
175.184.238.0/24 Valid Other IRR onlyRADB 141 21% 49
175.184.239.0/24 Valid Other IRR onlyRADB 141 21% 49

AS-SET

PeeringDB's irr_as_set for AS134654: RADB::AS-DATAUTAMA-GLOBAL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS134654 isn't in the set, or no route object for AS134654 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS134654 in itNot covered
RADB::AS-DATAUTAMA-GLOBAL RADB10 member sets in no database: AS-JDP, AS13335:AS-CLOUDFLARE, AS149707:AS-AKSESDATA, AS23671:AS-SET-LM-ID, AS23949:AS-COMNET … 202109,187 Yes 0

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

  • Route object: RIR6
  • AS-SET: missing member10
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR103.147.254.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.147.255.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR175.184.238.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2405:c5c0:ff00::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR175.184.238.0/24Route object only in RADB. Add it in the RIR database for the space.141 of 673
Route object: RIR175.184.239.0/24Route object only in RADB. Add it in the RIR database for the space.141 of 673
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS-JDP; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS13335:AS-CLOUDFLARE; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS149707:AS-AKSESDATA; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS23671:AS-SET-LM-ID; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS23949:AS-COMNET; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS38496:AS-CNI; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS45146:AS-RAJASA; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS45325:AS-PC24; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS46055:AS-ROKA; no IRR database read has it.
AS-SET: missing memberRADB::AS-DATAUTAMA-GLOBALAS-DATAUTAMA-GLOBAL (RADB) lists AS9340:AS-INDONET; no IRR database read has it.

Route objects not announced

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

175.184.237.0/24RADBValid

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.