Network · data from 2026-11-12
AS399798 NOVANTAS-01 - Novantas, Inc.
Registry name: NOVANTAS-01 - Novantas, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399798, 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.
| 2602:80a:7000::/48 | No ROA | Nonecovered by 2602:80a:7000::/44 | 635 100% |
| 192.206.42.0/24 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS399798 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.
- ROA: none2
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:80a:7000::/48 | No ROA covers it. Add a ROA for AS399798, maxLength 48. |
| Route object: none | 2602:80a:7000::/48 | No route object for it. A route object for 2602:80a:7000::/44 with origin AS399798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399798 in the RIR database for the space. |
| ROA: none | 192.206.42.0/24 | No ROA covers it. Add a ROA for AS399798, maxLength 24. |
Route objects not announced
Route objects with origin AS399798 whose prefix no peer sees AS399798 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:80a:7000::/44 | ARIN | No ROA |
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.