Network · data from 2026-11-12
AS400326 vGRID
Registry name: NETFIRE-NFFIBER01 - NetFire, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400326, 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.
| 158.51.115.0/24 | Valid | Nonecovered by 158.51.114.0/23 | 2 0%low visibility |
| 2606:3f80:e001::/48 | Valid | None | 1 0%low visibility |
AS-SET
AS400326's PeeringDB record names no 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 3 are in fix.csv.
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 158.51.115.0/24 | No route object for it. A route object for 158.51.114.0/23 with origin AS400326 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400326 in the RIR database for the space. |
| Route object: none | 2606:3f80:e001::/48 | No route object for it. Add a route object with origin AS400326 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400326 whose prefix no peer sees AS400326 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 158.51.114.0/23 | ARIN | 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.