Network · data from 2026-11-12
AS59210 PHOENIXNAP-AS-SG1 - PhoenixNAP
Registry name: PHOENIXNAP-AS-SG1 - PhoenixNAP, SG · not in PeeringDB
24IPv4 routes
100.0% RPKI valid · 41.7% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
14 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS59210, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS59210, 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.
| 125.253.90.0/24 | Valid | None | 672 100% |
| 125.253.91.0/24 | Valid | None | 672 100% |
| 125.253.92.0/24 | Valid | None | 672 100% |
| 125.253.93.0/24 | Valid | None | 672 100% |
| 131.153.48.0/24 | Valid | Nonecovered by 131.153.48.0/22 | 672 100% |
| 131.153.49.0/24 | Valid | Nonecovered by 131.153.48.0/22 | 672 100% |
| 131.153.50.0/24 | Valid | Nonecovered by 131.153.48.0/22 | 672 100% |
| 131.153.78.0/24 | Valid | Nonecovered by 131.153.76.0/22 | 672 100% |
| 131.153.99.0/24 | Valid | None | 672 100% |
| 131.153.205.0/24 | Valid | None | 672 100% |
| 103.67.201.0/24 | Valid | None | 671 100% |
| 131.153.47.0/24 | Valid | Nonecovered by 131.153.46.0/23 | 671 100% |
| 131.153.85.0/24 | Valid | None | 671 100% |
| 131.153.206.0/24 | Valid | None | 671 100% |
| 131.153.46.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 131.153.46.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 131.153.48.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 131.153.76.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 131.153.159.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.243.172.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.243.173.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.243.174.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.243.175.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 223.26.18.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2401:bc40:a100::/40 | Valid | RIR databaseAPNIC | 634 100% |
| 2401:bc40:e301::/48 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
AS59210 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 21 are in fix.csv.
- Route object: none14
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 125.253.90.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 125.253.91.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 125.253.92.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 125.253.93.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.48.0/24 | No route object for it. A route object for 131.153.48.0/22 with origin AS59210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.49.0/24 | No route object for it. A route object for 131.153.48.0/22 with origin AS59210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.50.0/24 | No route object for it. A route object for 131.153.48.0/22 with origin AS59210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.78.0/24 | No route object for it. A route object for 131.153.76.0/22 with origin AS59210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.99.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.205.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 103.67.201.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.47.0/24 | No route object for it. A route object for 131.153.46.0/23 with origin AS59210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.85.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: none | 131.153.206.0/24 | No route object for it. Add a route object with origin AS59210 in the RIR database for the space. |
| Route object: RIR | 131.153.46.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.153.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.153.48.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.153.76.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.153.159.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59210 whose prefix no peer sees AS59210 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.185.56.0/24 | ARIN | Invalid: origin |
| 2401:bc40:6100::/40 | APNIC | 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.