bgpreport

Network · data from 2026-11-12

AS149693 Jaringan Datamedia Nusantara

Registry name: IDNIC-DATAMEDIA-AS-ID - PT Jaringan Datamedia Nusantara, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149693, 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.186.96.0/23 No ROA Other IRR onlyRADB 1 0%low visibility 1
2400:aca0::/35 Valid Nonecovered by 2400:aca0::/32 635 100% 70
103.186.97.0/24 Valid Other IRR onlyRADB 673 100% 69
2400:aca0::/32 Valid Other IRR onlyRADB 635 100% 70
2400:aca0:2000::/35 Valid Other IRR onlyRADB 635 100% 70
2400:aca0:4000::/35 Valid Other IRR onlyRADB 635 100% 70
2400:aca0:6000::/35 Valid Other IRR onlyRADB 635 100% 70
2400:aca0:8000::/35 Valid Other IRR onlyRADB 635 100% 70
2400:aca0:a000::/35 Valid Other IRR onlyRADB 635 100% 70
2400:aca0:c000::/35 Valid Other IRR onlyRADB 635 100% 70
2400:aca0:e000::/35 Valid Other IRR onlyRADB 635 100% 70
103.186.96.0/24 Valid Other IRR onlyRADB 3 0%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS149693: AS149693:AS-ID. 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 (AS149693 isn't in the set, or no route object for AS149693 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 objectsAS149693 in itNot covered
AS149693:AS-ID 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 14 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR11
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none103.186.96.0/23No ROA covers it. Add a ROA for AS149693, maxLength 23.1 of 673
Route object: RIR103.186.96.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: none2400:aca0::/35No route object for it. A route object for 2400:aca0::/32 with origin AS149693 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149693 in the RIR database for the space.635 of 636
Route object: RIR103.186.97.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2400:aca0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:aca0:2000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:aca0:4000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:aca0:6000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:aca0:8000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:aca0:a000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:aca0:c000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2400:aca0:e000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR103.186.96.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
AS-SET: not foundAS149693:AS-IDPeeringDB names AS149693:AS-ID; no IRR database read has it.

Route objects not announced

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