Network · data from 2026-11-12
AS215682 nscale-stav-public Nscale Glomfjord AS
Registry name: nscale-stav-public Nscale Glomfjord AS, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215682, 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.
| 46.148.114.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 46.148.115.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 46.148.116.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a0b:92c0::/44 | Valid | Nonecovered by 2a0b:92c0::/40 | 635 100% |
| 46.148.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.143.78.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS215682 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 6 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.148.114.0/24 | No ROA covers it. Add a ROA for AS215682, maxLength 24. |
| ROA: none | 46.148.115.0/24 | No ROA covers it. Add a ROA for AS215682, maxLength 24. |
| ROA: none | 46.148.116.0/24 | No ROA covers it. Add a ROA for AS215682, maxLength 24. |
| Route object: none | 2a0b:92c0::/44 | No route object for it. A route object for 2a0b:92c0::/40 with origin AS215682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215682 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS215682 whose prefix no peer sees AS215682 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0b:92c0::/29 | RIPE | Valid |
| 2a0b:92c0::/40 | RIPE | 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.