Network · data from 2026-11-12
AS394643 AS-PHOENIXNAP-AUS1 - PhoenixNAP LLC
Registry name: AS-PHOENIXNAP-AUS1 - PhoenixNAP LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394643, 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.
| 131.153.228.0/23 | Valid | None | 672 100% |
| 131.153.244.0/24 | Valid | None | 672 100% |
| 2607:ff00:d00::/40 | Valid | None | 635 100% |
| 2607:6003:230f::/48 | Valid | None | 605 95% |
AS-SET
AS394643 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.
- Route object: none4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 131.153.228.0/23 | No route object for it. Add a route object with origin AS394643 in the RIR database for the space. |
| Route object: none | 131.153.244.0/24 | No route object for it. Add a route object with origin AS394643 in the RIR database for the space. |
| Route object: none | 2607:ff00:d00::/40 | No route object for it. Add a route object with origin AS394643 in the RIR database for the space. |
| Route object: none | 2607:6003:230f::/48 | No route object for it. Add a route object with origin AS394643 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS394643 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.