Network · data from 2026-11-12
AS35706 Net at Once
Registry name: NAO Net at Once Sweden AB, SE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35706, 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.
| 217.10.103.135/32 | Invalid: maxLength | Nonecovered by 217.10.96.0/19 | 0 0%low visibility |
| 31.210.248.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 77.105.192.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 82.197.224.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 85.195.0.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 151.252.128.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 178.249.144.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 185.51.224.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 217.10.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 2001:4db8::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS35706: AS-NAO. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS35706 isn't in the set, or no route object for AS35706 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS35706 in it | Not covered |
|---|---|---|---|---|---|
| AS-NAO | RIPE | 19 | 5 | Yes | 1 |
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 13 are in fix.csv.
- ROA: maxLength1
- ROA: none7
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 217.10.103.135/32 | ROA 217.10.96.0/19 AS35706 has maxLength 19; the route is a /32. Raise the maxLength, or add a ROA for 217.10.103.135/32. |
| Route object: none | 217.10.103.135/32 | No route object for it. A route object for 217.10.96.0/19 with origin AS35706 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS35706 in the RIR database for the space. |
| ROA: none | 31.210.248.0/21 | No ROA covers it. Add a ROA for AS35706, maxLength 21. |
| ROA: none | 77.105.192.0/18 | No ROA covers it. Add a ROA for AS35706, maxLength 18. |
| ROA: none | 82.197.224.0/19 | No ROA covers it. Add a ROA for AS35706, maxLength 19. |
| ROA: none | 85.195.0.0/18 | No ROA covers it. Add a ROA for AS35706, maxLength 18. |
| ROA: none | 151.252.128.0/18 | No ROA covers it. Add a ROA for AS35706, maxLength 18. |
| ROA: none | 178.249.144.0/21 | No ROA covers it. Add a ROA for AS35706, maxLength 21. |
| ROA: none | 185.51.224.0/22 | No ROA covers it. Add a ROA for AS35706, maxLength 22. |
Route objects not announced
Route objects with origin AS35706 whose prefix no peer sees AS35706 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.212.209.0/24 | RIPE | Invalid: origin |
| 185.186.56.0/22 | RIPE | Invalid: origin |
| 185.186.56.0/23 | RIPE | Invalid: origin |
| 185.186.58.0/23 | RIPE | Invalid: origin |
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.