Network · data from 2026-11-12
AS23689 MAKATISHANGRILA-AS-AP - Makati Shangri-La
Registry name: MAKATISHANGRILA-AS-AP - Makati Shangri-La, PH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23689, 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.
| 124.105.146.0/23 | Invalid: origin | None | 121 18% |
| 120.28.28.0/24 | Valid | Nonecovered by 120.28.28.0/23 | 671 100% |
| 120.28.29.0/24 | Valid | Nonecovered by 120.28.28.0/23 | 671 100% |
| 136.158.164.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS23689 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 5 are in fix.csv.
- ROA: origin1
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 124.105.146.0/23 | ROAs covering it name AS9299, not AS23689. If AS23689 should announce it, add a ROA for AS23689. |
| Route object: none | 124.105.146.0/23 | No route object for it. Add a route object with origin AS23689 in the RIR database for the space. |
| Route object: none | 120.28.28.0/24 | No route object for it. A route object for 120.28.28.0/23 with origin AS23689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23689 in the RIR database for the space. |
| Route object: none | 120.28.29.0/24 | No route object for it. A route object for 120.28.28.0/23 with origin AS23689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23689 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23689 whose prefix no peer sees AS23689 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 120.28.28.0/23 | 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.