bgpreport

Network · data from 2026-11-12

AS152373 Anugerah Media Data Nusantara, PT

Registry name: IDNIC-AMAN-AS-ID - PT Anugerah Media Data Nusantara, 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
0Route objects not announced registered with origin AS152373, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS152373, 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.176.201.0/24 Valid Other IRR onlyRADB 671 100% 69
103.176.200.0/24 Valid Other IRR onlyRADB 669 99% 68
157.15.62.0/23 Valid Other IRR onlyRADB 669 99% 68
2001:df3:72c0::/48 Valid Other IRR onlyRADB 636 100% 70
157.15.63.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
157.15.62.0/24 Valid RIR databaseAPNIC, RADB 669 99% 68

AS-SET

PeeringDB's irr_as_set for AS152373: APNIC::AS152373:AS-AMAN. 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 (AS152373 isn't in the set, or no route object for AS152373 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 objectsAS152373 in itNot covered
APNIC::AS152373:AS-AMAN APNIC 216 No 6

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

  • Route object: RIR4
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: RIR103.176.201.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.176.200.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR157.15.62.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2001:df3:72c0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
AS-SET: own ASNAPNIC::AS152373:AS-AMANAS152373 isn't in AS152373:AS-AMAN (APNIC) once expanded. Add AS152373 to it.

Route objects not announced

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