Network · data from 2026-11-12
AS39945 NUSPIRE - Nuspire Communications
Registry name: NUSPIRE - Nuspire Communications, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39945, 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.
| 208.67.230.0/24 | Valid | Other origin onlycovered by 208.67.228.0/22 | 672 100% |
| 45.54.20.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 208.67.228.0/23 | Valid | RIR databaseARIN | 673 100% |
| 208.67.231.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS39945 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: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 208.67.230.0/24 | Route objects for it name AS36236. A route object for 208.67.228.0/22 with origin AS39945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39945 in the RIR database for the space. |
| Route object: RIR | 45.54.20.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39945 whose prefix no peer sees AS39945 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 208.67.228.0/22 | RADB | Valid |
| 2607:f740:e620::/48 | RADB | 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.