Network · data from 2026-11-12
AS31198 Space-Norway-UK-Ltd SPACE NORWAY (UK) LIMITED
Registry name: Space-Norway-UK-Ltd SPACE NORWAY (UK) LIMITED, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31198, 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.
| 45.133.30.0/24 | No ROA | None | 2 0%low visibility |
| 45.133.28.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 171.33.174.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.18.152.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 62.228.242.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.228.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.173.48.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.173.63.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS31198 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 48 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: not announced44
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.133.30.0/24 | No ROA covers it. Add a ROA for AS31198, maxLength 24. |
| Route object: none | 45.133.30.0/24 | No route object for it. Add a route object with origin AS31198 in the RIR database for the space. |
| ROA: none | 45.133.28.0/23 | No ROA covers it. Add a ROA for AS31198, maxLength 23. |
| ROA: none | 171.33.174.0/24 | No ROA covers it. Add a ROA for AS31198, maxLength 24. |
Route objects not announced
Route objects with origin AS31198 whose prefix no peer sees AS31198 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.18.154.0/24 | RIPE | Valid |
| 46.18.158.0/24 | RIPE | Valid |
| 213.175.169.0/24 | RIPE | Invalid: origin |
| 217.173.48.0/20 | RIPE | No ROA |
| 217.173.49.0/28 | RIPE | No ROA |
| 217.173.49.16/28 | RIPE | No ROA |
| 217.173.49.32/28 | RIPE | No ROA |
| 217.173.49.48/28 | RIPE | No ROA |
| 217.173.49.64/29 | RIPE | No ROA |
| 217.173.49.88/29 | RIPE | No ROA |
| 217.173.49.128/28 | RIPE | No ROA |
| 217.173.49.144/28 | RIPE | No ROA |
| 217.173.49.160/28 | RIPE | No ROA |
| 217.173.49.176/29 | RIPE | No ROA |
| 217.173.49.192/28 | RIPE | No ROA |
| 217.173.49.208/29 | RIPE | No ROA |
| 217.173.49.224/28 | RIPE | No ROA |
| 217.173.50.0/29 | RIPE | No ROA |
| 217.173.50.8/29 | RIPE | No ROA |
| 217.173.50.16/28 | RIPE | No ROA |
| 217.173.50.32/29 | RIPE | No ROA |
| 217.173.50.40/29 | RIPE | No ROA |
| 217.173.50.48/28 | RIPE | No ROA |
| 217.173.50.64/26 | RIPE | No ROA |
| 217.173.50.136/29 | RIPE | No ROA |
| 217.173.50.144/29 | RIPE | No ROA |
| 217.173.50.152/29 | RIPE | No ROA |
| 217.173.50.240/29 | RIPE | No ROA |
| 217.173.51.32/28 | RIPE | No ROA |
| 217.173.51.64/26 | RIPE | No ROA |
| 217.173.52.0/25 | RIPE | No ROA |
| 217.173.53.0/29 | RIPE | No ROA |
| 217.173.53.8/29 | RIPE | No ROA |
| 217.173.53.24/29 | RIPE | No ROA |
| 217.173.53.32/29 | RIPE | No ROA |
| 217.173.53.40/29 | RIPE | No ROA |
| 217.173.53.48/29 | RIPE | No ROA |
| 217.173.53.64/29 | RIPE | No ROA |
| 217.173.53.192/28 | RIPE | No ROA |
| 217.173.53.208/28 | RIPE | No ROA |
| 217.173.54.0/24 | RIPE | No ROA |
| 217.173.58.0/24 | RIPE | No ROA |
| 217.173.59.0/24 | RIPE | No ROA |
| 217.173.60.0/24 | 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.