bgpreport

Network · data from 2026-11-12

AS23694 IDNIC-ICONMEDIANETWORK-AS-ID - PT Iconmedia Lintas Nusantara

Registry name: IDNIC-ICONMEDIANETWORK-AS-ID - PT Iconmedia Lintas Nusantara, ID · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
14Route objects not announced registered with origin AS23694, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23694, 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.66.44.0/22 Valid Other IRR onlyRADB 673 100% 69
103.66.44.0/23 Valid Other IRR onlyRADB 673 100% 70
103.66.44.0/24 Valid Other IRR onlyRADB 673 100% 70
103.66.46.0/24 Valid Other IRR onlyRADB 673 100% 70
103.66.47.0/24 Valid Other IRR onlyRADB 673 100% 70
103.66.45.0/24 Valid Other IRR onlyRADB 218 32% 58
103.66.46.0/23 Valid Other IRR onlyRADB 218 32% 58

AS-SET

AS23694 isn't in PeeringDB, where networks name their AS-SET.

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

  • Route object: RIR7
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: RIR103.66.44.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.66.44.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.66.44.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.66.46.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.66.47.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.66.45.0/24Route object only in RADB. Add it in the RIR database for the space.218 of 673
Route object: RIR103.66.46.0/23Route object only in RADB. Add it in the RIR database for the space.218 of 673

Route objects not announced

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

202.87.176.0/21NTTCOM, RADBNo ROA
202.87.176.0/22NTTCOM, RADBNo ROA
202.87.176.0/23NTTCOM, RADBNo ROA
202.87.178.0/23NTTCOM, RADBNo ROA
202.87.180.0/22NTTCOM, RADBNo ROA
202.87.180.0/23NTTCOM, RADBNo ROA
202.87.182.0/23NTTCOM, RADBNo ROA
202.87.184.0/21NTTCOM, RADBNo ROA
202.87.184.0/22NTTCOM, RADBNo ROA
202.87.184.0/23NTTCOM, RADBNo ROA
202.87.186.0/23NTTCOM, RADBNo ROA
202.87.188.0/22NTTCOM, RADBNo ROA
202.87.188.0/23NTTCOM, RADBNo ROA
202.87.190.0/23NTTCOM, RADBNo ROA

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.