bgpreport

Network · data from 2026-11-12

AS152049 Iconmedia Nusantara Abadi

Registry name: IDNIC-ICONMEDIA-AS-ID - PT Iconmedia Nusantara Abadi, ID · PeeringDB

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

Announced routes

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

45.123.140.0/23 Invalid: origin None 6 1%low visibility 5
45.123.140.0/24 Valid Other IRR onlyRADB 668 99% 68
45.123.141.0/24 Valid Other IRR onlyRADB 668 99% 68

AS-SET

PeeringDB's irr_as_set for AS152049: AS152049:AS-ICONMEDIA. 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 (AS152049 isn't in the set, or no route object for AS152049 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 objectsAS152049 in itNot covered
AS152049:AS-ICONMEDIA APNIC 4129 No 3

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.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR2
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: origin45.123.140.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS152049 should announce it, add a ROA for AS152049.6 of 673
Route object: none45.123.140.0/23No route object for it. Add a route object with origin AS152049 in the RIR database for the space.6 of 673
Route object: RIR45.123.140.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.123.141.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
AS-SET: own ASNAS152049:AS-ICONMEDIAAS152049 isn't in AS152049:AS-ICONMEDIA (APNIC) once expanded. Add AS152049 to it.

Route objects not announced

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