Network · data from 2026-11-12
AS55402 PNB1COM-PH - PNB Financial Center
Registry name: PNB1COM-PH - PNB Financial Center, PH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55402, 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.58.236.0/23 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 103.110.44.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.110.47.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.110.46.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
AS-SET
AS55402 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 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.58.236.0/23 | No ROA covers it. Add a ROA for AS55402, maxLength 23. |
Route objects not announced
Route objects with origin AS55402 whose prefix no peer sees AS55402 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.110.45.0/24 | APNIC | Valid |
| 202.58.236.0/24 | APNIC, RADB | No ROA |
| 202.58.237.0/24 | APNIC, RADB | No 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.