Network · data from 2026-11-12
AS205737 naveum Naveum AG
Registry name: naveum Naveum AG, CH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205737, 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.
| 2a0b:9640::/30 | No ROA | Nonecovered by 2a0b:9640::/29 | 634 100% |
| 185.207.76.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 195.200.94.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS205737 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 | 2a0b:9640::/30 | No ROA covers it. Add a ROA for AS205737, maxLength 30. |
| Route object: none | 2a0b:9640::/30 | No route object for it. A route object for 2a0b:9640::/29 with origin AS205737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205737 in the RIR database for the space. |
| ROA: none | 185.207.76.0/22 | No ROA covers it. Add a ROA for AS205737, maxLength 22. |
Route objects not announced
Route objects with origin AS205737 whose prefix no peer sees AS205737 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0b:9640::/29 | RIPE | 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.