bgpreport

Network · data from 2026-11-12

AS24536 Elektrindo Data Nusantara

Registry name: ELNUS-AS-ID - PT. Elektrindo Data Nusantara, ID · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.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
6Route objects not announced registered with origin AS24536, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24536, 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.
2404:4200::/48 Valid Nonecovered by 2404:4200::/32 635 100% 70
202.146.176.0/21 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.176.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.177.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.178.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.179.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.180.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.181.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.182.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.146.183.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
2404:4200::/32 Valid Other IRR onlyRADB 635 100% 70

AS-SET

AS24536's PeeringDB record names no 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 17 are in fix.csv.

  • Route object: none1
  • Route object: RIR10
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none2404:4200::/48No route object for it. A route object for 2404:4200::/32 with origin AS24536 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24536 in the RIR database for the space.635 of 636
Route object: RIR202.146.176.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.176.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.177.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.178.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.179.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.180.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.181.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.182.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.146.183.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2404:4200::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

202.146.176.0/22NTTCOM, RADBValid
202.146.176.0/23NTTCOMValid
202.146.178.0/23NTTCOMValid
202.146.180.0/22NTTCOMValid
202.146.180.0/23NTTCOM, RADBValid
202.146.182.0/23NTTCOMValid

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.