bgpreport

Network · data from 2026-11-12

AS38502 MDPNET-AS-ID - PT. MULTI DATA PALEMBANG

Registry name: MDPNET-AS-ID - PT. MULTI DATA PALEMBANG, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38502, 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.
116.90.208.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
116.90.209.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
116.90.210.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
116.90.211.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
116.90.212.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
116.90.215.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69

AS-SET

AS38502 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.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none116.90.208.0/24No ROA covers it. Add a ROA for AS38502, maxLength 24.673 of 673
Route object: RIR116.90.208.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.90.209.0/24No ROA covers it. Add a ROA for AS38502, maxLength 24.673 of 673
Route object: RIR116.90.209.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.90.210.0/24No ROA covers it. Add a ROA for AS38502, maxLength 24.673 of 673
Route object: RIR116.90.210.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.90.211.0/24No ROA covers it. Add a ROA for AS38502, maxLength 24.673 of 673
Route object: RIR116.90.211.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.90.212.0/24No ROA covers it. Add a ROA for AS38502, maxLength 24.673 of 673
Route object: RIR116.90.212.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.90.215.0/24No ROA covers it. Add a ROA for AS38502, maxLength 24.673 of 673
Route object: RIR116.90.215.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

116.90.208.0/21APNIC, NTTCOM, RADBNo ROA
116.90.208.0/22NTTCOMNo ROA
116.90.208.0/23NTTCOMNo ROA
116.90.210.0/23NTTCOMNo ROA
116.90.212.0/22NTTCOMNo ROA
116.90.212.0/23NTTCOMNo ROA
116.90.213.0/24NTTCOMNo ROA
116.90.214.0/23NTTCOMNo ROA
116.90.214.0/24NTTCOMNo 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.