bgpreport

Network · data from 2026-11-12

AS24298 apolloglobal-ph - Apollo Global Net AS, Application Service Provider, Manila

Registry name: apolloglobal-ph - Apollo Global Net AS, Application Service Provider, Manila, PH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24298, 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.123.144.0/22 Valid RIR databaseAPNIC 673 100% 68
103.123.144.0/24 Valid RIR databaseAPNIC 673 100% 68
103.123.145.0/24 Valid RIR databaseAPNIC 673 100% 68
103.123.147.0/24 Valid RIR databaseAPNIC 673 100% 68
202.60.8.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.60.9.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.60.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.60.12.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.60.15.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.123.146.0/24 Valid RIR databaseAPNIC 667 99% 66
202.60.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 666 99% 66
202.60.11.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 666 99% 66
202.60.13.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 666 99% 66

AS-SET

AS24298 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 16 are in fix.csv.

  • Route object: not announced16

Route objects not announced

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

103.123.144.0/23APNICValid
103.123.146.0/23APNICValid
165.220.0.0/16NTTCOM, RADBNo ROA
165.220.0.0/17RADBNo ROA
165.220.0.0/18RADBNo ROA
165.220.0.0/19RADBNo ROA
165.220.0.0/20RADBNo ROA
165.220.16.0/20NTTCOM, RADBNo ROA
202.60.8.0/22APNIC, NTTCOM, RADBValid
202.60.8.0/23APNIC, NTTCOM, RADBValid
202.60.10.0/23APNIC, NTTCOM, RADBValid
202.60.12.0/22APNIC, NTTCOM, RADBValid
202.60.12.0/23APNIC, NTTCOM, RADBValid
202.60.14.0/23APNIC, NTTCOM, RADBValid
202.60.14.0/24APNIC, NTTCOM, RADBValid
202.60.16.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.