bgpreport

Network · data from 2026-11-12

AS23862 DILNET-AS-AP - University of the Philippines Diliman

Registry name: DILNET-AS-AP - University of the Philippines Diliman, PH · not in PeeringDB

12IPv4 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
23Route objects not announced registered with origin AS23862, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23862, 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.53.58.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
103.53.59.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
202.92.128.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
202.92.129.0/24 Valid RIR databaseAPNIC, RADB 671 100% 70
202.92.130.0/24 Valid RIR databaseAPNIC, RADB 671 100% 70
202.92.131.0/24 Valid RIR databaseAPNIC, RADB 671 100% 70
202.92.132.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
202.92.134.0/24 Valid RIR databaseAPNIC, RADB 671 100% 70
202.92.135.0/24 Valid RIR databaseAPNIC, RADB 671 100% 70
202.92.136.0/24 Valid RIR databaseAPNIC, RADB 671 100% 70
202.92.141.0/24 Valid RIR databaseAPNIC, RADB 671 100% 70
202.92.159.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 70
2400:b000:100::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS23862 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 23 are in fix.csv.

  • Route object: not announced23

Route objects not announced

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

103.53.56.0/22APNIC, NTTCOM, RADBNo ROA
103.53.56.0/23NTTCOM, RADBNo ROA
103.53.56.0/24NTTCOM, RADBNo ROA
103.53.57.0/24NTTCOM, RADBNo ROA
103.53.58.0/23NTTCOM, RADBNo ROA
202.92.128.0/20NTTCOM, RADBNo ROA
202.92.128.0/21NTTCOM, RADBNo ROA
202.92.128.0/22APNIC, NTTCOM, RADBNo ROA
202.92.128.0/23RADBNo ROA
202.92.130.0/23RADBNo ROA
202.92.132.0/22RADBNo ROA
202.92.132.0/23RADBNo ROA
202.92.134.0/23APNIC, NTTCOM, RADBNo ROA
202.92.136.0/21RADBNo ROA
202.92.136.0/22APNIC, NTTCOM, RADBValid
202.92.140.0/22RADBNo ROA
202.92.140.0/23NTTCOM, RADBNo ROA
202.92.140.0/24APNICInvalid: origin
202.92.142.0/23RADBNo ROA
202.92.143.0/24RADBNo ROA
2400:b000:c0e::/48APNICValid
2400:b000:eee::/48APNICValid
2400:b000:1100::/48APNICNo 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.