Network · data from 2026-11-12
AS41001 SafespringSE Safespring AB
Registry name: SafespringSE Safespring AB, SE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41001, 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.
| 2a09:d400::/48 | No ROA | Nonecovered by 2a09:d400::/32 | 635 100% |
| 2a09:d400:1::/48 | No ROA | Nonecovered by 2a09:d400::/32 | 635 100% |
| 2a09:d400:400::/48 | No ROA | Nonecovered by 2a09:d400::/32 | 635 100% |
| 212.162.144.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.189.28.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 192.121.132.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 192.121.208.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 194.14.20.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 2a0a:bcc0::/29 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS41001 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 17 are in fix.csv.
- ROA: none9
- Route object: none3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a09:d400::/48 | No ROA covers it. Add a ROA for AS41001, maxLength 48. |
| Route object: none | 2a09:d400::/48 | No route object for it. A route object for 2a09:d400::/32 with origin AS41001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41001 in the RIR database for the space. |
| ROA: none | 2a09:d400:1::/48 | No ROA covers it. Add a ROA for AS41001, maxLength 48. |
| Route object: none | 2a09:d400:1::/48 | No route object for it. A route object for 2a09:d400::/32 with origin AS41001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41001 in the RIR database for the space. |
| ROA: none | 2a09:d400:400::/48 | No ROA covers it. Add a ROA for AS41001, maxLength 48. |
| Route object: none | 2a09:d400:400::/48 | No route object for it. A route object for 2a09:d400::/32 with origin AS41001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41001 in the RIR database for the space. |
| ROA: none | 212.162.144.0/22 | No ROA covers it. Add a ROA for AS41001, maxLength 22. |
| ROA: none | 185.189.28.0/22 | No ROA covers it. Add a ROA for AS41001, maxLength 22. |
| ROA: none | 192.121.132.0/23 | No ROA covers it. Add a ROA for AS41001, maxLength 23. |
| ROA: none | 192.121.208.0/23 | No ROA covers it. Add a ROA for AS41001, maxLength 23. |
| ROA: none | 194.14.20.0/23 | No ROA covers it. Add a ROA for AS41001, maxLength 23. |
| ROA: none | 2a0a:bcc0::/29 | No ROA covers it. Add a ROA for AS41001, maxLength 29. |
Route objects not announced
Route objects with origin AS41001 whose prefix no peer sees AS41001 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.47.188.0/22 | RIPE | Valid |
| 193.11.90.0/23 | RIPE | Invalid: origin |
| 2001:6b0:5a::/48 | RIPE | Valid |
| 2001:6b0:7d::/48 | RIPE | Valid |
| 2a09:d400::/32 | 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.