bgpreport

Network · data from 2026-11-12

AS136121 Digital Media Telematika

Registry name: DIGITNET-AS-ID - PT Digital Media Telematika, ID · PeeringDB

7IPv4 routes 100.0% RPKI valid · 85.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS136121, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136121, 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.
202.154.18.0/23 Valid None 671 100% 68
103.154.230.0/23 Valid Other IRR onlyNTTCOM, RADB 671 100% 68
2406:5dc0::/32 Valid Other IRR onlyNTTCOM 635 100% 69
103.154.230.0/24 Valid Other IRR onlyNTTCOM, RADB 216 32% 58
103.154.231.0/24 Valid Other IRR onlyRADB 216 32% 58
202.154.18.0/24 Valid Other IRR onlyRADB 216 32% 58
202.154.19.0/24 Valid Other IRR onlyRADB 216 32% 58
103.158.210.0/24 Valid RIR databaseAPNIC 673 100% 70

AS-SET

PeeringDB's irr_as_set for AS136121: AS136121:AS-DIGITNET. 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 (AS136121 isn't in the set, or no route object for AS136121 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 objectsAS136121 in itNot covered
AS136121:AS-DIGITNET In no IRR database read today.

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

  • Route object: none1
  • Route object: RIR6
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none202.154.18.0/23No route object for it. Add a route object with origin AS136121 in the RIR database for the space.671 of 673
Route object: RIR103.154.230.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2406:5dc0::/32Route object only in NTTCOM. Add it in the RIR database for the space.635 of 636
Route object: RIR103.154.230.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.216 of 673
Route object: RIR103.154.231.0/24Route object only in RADB. Add it in the RIR database for the space.216 of 673
Route object: RIR202.154.18.0/24Route object only in RADB. Add it in the RIR database for the space.216 of 673
Route object: RIR202.154.19.0/24Route object only in RADB. Add it in the RIR database for the space.216 of 673
AS-SET: not foundAS136121:AS-DIGITNETPeeringDB names AS136121:AS-DIGITNET; no IRR database read has it.

Route objects not announced

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