bgpreport

Network · data from 2026-11-12

AS9821 PREGINET

Registry name: DOST-PH-AP - Department of Science and Technology, PH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9821, 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.80.140.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
202.90.128.0/19 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
202.90.155.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
2001:d18::/32 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS9821'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 33 are in fix.csv.

  • Route object: not announced33

Route objects not announced

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

103.192.184.0/22NTTCOM, RADBNo ROA
103.192.184.0/23NTTCOM, RADBNo ROA
103.192.184.0/24NTTCOM, RADBNo ROA
103.192.185.0/24NTTCOM, RADBNo ROA
103.192.186.0/23NTTCOM, RADBNo ROA
103.192.186.0/24NTTCOM, RADBNo ROA
103.192.187.0/24NTTCOM, RADBNo ROA
202.90.135.0/24APNIC, NTTCOM, RADBValid
202.92.128.0/19NTTCOM, RADBNo ROA
202.92.128.0/20NTTCOM, RADBNo ROA
202.92.128.0/21NTTCOM, RADBNo ROA
202.92.128.0/22NTTCOM, RADBNo ROA
202.92.128.0/23NTTCOM, RADBNo ROA
202.92.130.0/23NTTCOM, RADBNo ROA
202.92.132.0/22NTTCOM, RADBNo ROA
202.92.132.0/23NTTCOM, RADBNo ROA
202.92.134.0/23NTTCOM, RADBNo ROA
202.92.136.0/21NTTCOM, RADBNo ROA
202.92.140.0/22NTTCOM, RADBNo ROA
202.92.140.0/23NTTCOM, RADBNo ROA
202.92.142.0/23NTTCOM, RADBNo ROA
202.92.143.0/24NTTCOM, RADBNo ROA
202.92.144.0/20NTTCOM, RADBNo ROA
202.92.144.0/21NTTCOM, RADBNo ROA
202.92.152.0/21NTTCOM, RADBNo ROA
202.92.152.0/22NTTCOM, RADBNo ROA
202.92.152.0/23NTTCOM, RADBNo ROA
202.92.154.0/23NTTCOM, RADBNo ROA
202.92.156.0/22NTTCOM, RADBNo ROA
202.92.156.0/23NTTCOM, RADBNo ROA
202.92.158.0/23NTTCOM, RADBNo ROA
202.92.158.0/24NTTCOM, RADBNo ROA
203.211.56.0/22APNICValid

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.