bgpreport

Network · data from 2026-11-12

AS18153 MULTIDATA-ID-AP - PT Multidata Rancana Prima

Registry name: MULTIDATA-ID-AP - PT Multidata Rancana Prima, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18153, 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.72.200.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.72.192.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.72.193.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.72.195.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.72.196.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.72.201.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.72.202.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.72.206.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none202.72.200.0/24No ROA covers it. Add a ROA for AS18153, maxLength 24.673 of 673

Route objects not announced

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

202.72.192.0/20APNIC, NTTCOM, RADBNo ROA
202.72.192.0/21NTTCOM, RADBNo ROA
202.72.192.0/22NTTCOM, RADBNo ROA
202.72.192.0/23NTTCOM, RADBNo ROA
202.72.194.0/23NTTCOM, RADBNo ROA
202.72.196.0/22NTTCOM, RADBNo ROA
202.72.196.0/23NTTCOM, RADBNo ROA
202.72.197.0/24APNIC, NTTCOM, RADBNo ROA
202.72.198.0/23NTTCOM, RADBNo ROA
202.72.199.0/24APNICInvalid: origin
202.72.200.0/21NTTCOM, RADBNo ROA
202.72.200.0/22NTTCOM, RADBNo ROA
202.72.200.0/23NTTCOM, RADBNo ROA
202.72.202.0/23NTTCOM, RADBNo ROA
202.72.203.0/24APNICInvalid: origin
202.72.204.0/22NTTCOM, RADBNo ROA
202.72.206.0/23NTTCOM, RADBNo ROA
202.72.207.0/24APNICInvalid: origin

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.