Network · data from 2026-11-12
AS11572 SS-ATL - PhoenixNAP LLC
Registry name: SS-ATL - PhoenixNAP LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11572, 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.
| 204.217.128.0/22 | No ROA | None | 672 100% |
| 206.232.0.0/22 | No ROA | None | 672 100% |
| 64.38.249.0/24 | Valid | None | 672 100% |
| 64.38.250.0/24 | Valid | None | 672 100% |
| 104.244.52.0/24 | Valid | None | 672 100% |
| 131.153.24.0/21 | Valid | None | 672 100% |
| 131.153.65.0/24 | Valid | None | 672 100% |
| 131.153.66.0/23 | Valid | None | 672 100% |
| 131.153.82.0/24 | Valid | None | 672 100% |
| 131.153.132.0/22 | Valid | None | 672 100% |
| 131.153.152.0/23 | Valid | None | 672 100% |
| 63.214.166.0/23 | Valid | None | 662 98% |
| 2607:6003:2305::/48 | Valid | None | 636 100% |
| 2607:ff00:500::/40 | Valid | None | 636 100% |
| 142.228.4.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 142.228.40.0/22 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS11572 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.
- ROA: none2
- Route object: none14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.217.128.0/22 | No ROA covers it. Add a ROA for AS11572, maxLength 22. |
| Route object: none | 204.217.128.0/22 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| ROA: none | 206.232.0.0/22 | No ROA covers it. Add a ROA for AS11572, maxLength 22. |
| Route object: none | 206.232.0.0/22 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 64.38.249.0/24 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 64.38.250.0/24 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 104.244.52.0/24 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 131.153.24.0/21 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 131.153.65.0/24 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 131.153.66.0/23 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 131.153.82.0/24 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 131.153.132.0/22 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 131.153.152.0/23 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 63.214.166.0/23 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 2607:6003:2305::/48 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
| Route object: none | 2607:ff00:500::/40 | No route object for it. Add a route object with origin AS11572 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS11572 is announced.
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.