Network · data from 2026-11-12
AS17894 APMI-AS-AP - AyalaPort Makati, Inc. / Data Center Operator
Registry name: APMI-AS-AP - AyalaPort Makati, Inc. / Data Center Operator, PH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17894, 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.126.32.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.177.255.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 120.28.36.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.52.160.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 202.52.160.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.95.224.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.225.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.226.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.227.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.228.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.229.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.230.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.231.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.232.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.235.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.236.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.237.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.238.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.95.239.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.126.40.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 2401:b900::/32 | Valid | RIR databaseAPNIC, RADB | 636 100% |
AS-SET
AS17894 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 47 are in fix.csv.
- Route object: RIR2
- Route object: not announced45
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.126.32.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.177.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17894 whose prefix no peer sees AS17894 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.95.224.0/20 | NTTCOM, RADB | No ROA |
| 202.95.224.0/21 | NTTCOM, RADB | No ROA |
| 202.95.224.0/22 | NTTCOM, RADB | No ROA |
| 202.95.224.0/23 | NTTCOM, RADB | No ROA |
| 202.95.226.0/23 | NTTCOM, RADB | No ROA |
| 202.95.228.0/22 | NTTCOM, RADB | No ROA |
| 202.95.228.0/23 | NTTCOM, RADB | No ROA |
| 202.95.230.0/23 | NTTCOM, RADB | No ROA |
| 202.95.232.0/21 | NTTCOM, RADB | No ROA |
| 202.95.232.0/22 | NTTCOM, RADB | No ROA |
| 202.95.232.0/23 | NTTCOM, RADB | No ROA |
| 202.95.234.0/23 | NTTCOM, RADB | No ROA |
| 202.95.234.0/24 | NTTCOM, RADB | No ROA |
| 202.95.236.0/22 | NTTCOM, RADB | No ROA |
| 202.95.236.0/23 | NTTCOM, RADB | No ROA |
| 202.95.238.0/23 | NTTCOM, RADB | No ROA |
| 202.126.32.0/21 | APNIC, NTTCOM, RADB | Valid |
| 202.126.32.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.126.32.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.32.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.33.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.34.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.34.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.35.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.36.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.126.36.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.36.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.37.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.38.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.38.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.39.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.40.0/21 | APNIC, NTTCOM, RADB | Valid |
| 202.126.40.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.126.40.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.41.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.42.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.42.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.43.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.44.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.126.44.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.44.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.45.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.46.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.126.46.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.126.47.0/24 | APNIC, NTTCOM, RADB | Valid |
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.