bgpreport

Network · data from 2026-11-12

AS23950 GENID-AS-ID - Generasi Indonesia Digital PT.

Registry name: GENID-AS-ID - Generasi Indonesia Digital PT., ID · not in PeeringDB

2IPv4 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
2Low visibility seen by under 10% of full-table peers
26Route objects not announced registered with origin AS23950, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23950, 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.
202.51.16.0/24 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 28
202.51.19.0/24 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 28

AS-SET

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

  • Route object: RIR2
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
Route object: RIR202.51.16.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.51.19.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673

Route objects not announced

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

116.68.160.0/20RADBNo ROA
116.68.160.0/21RADBNo ROA
116.68.160.0/22RADBNo ROA
116.68.160.0/23RADBNo ROA
116.68.162.0/23RADBNo ROA
116.68.164.0/22RADBNo ROA
116.68.164.0/23RADBNo ROA
116.68.166.0/23RADBNo ROA
116.68.168.0/21RADBNo ROA
116.68.168.0/22RADBNo ROA
116.68.168.0/23RADBNo ROA
116.68.170.0/23RADBNo ROA
116.68.172.0/22RADBNo ROA
116.68.172.0/23RADBNo ROA
116.68.174.0/23RADBNo ROA
202.51.16.0/20NTTCOM, RADBNo ROA
202.51.16.0/21NTTCOMNo ROA
202.51.16.0/22NTTCOMNo ROA
202.51.16.0/23NTTCOM, RADBValid
202.51.17.0/24NTTCOM, RADBValid
202.51.18.0/23NTTCOMNo ROA
202.51.18.0/24NTTCOM, RADBNo ROA
202.51.20.0/22NTTCOMNo ROA
202.51.22.0/23NTTCOMNo ROA
202.51.22.0/24NTTCOM, RADBNo ROA
202.51.23.0/24NTTCOM, 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.