Network · data from 2026-11-12
AS60819 SAFENAMES-AS Safenames Ltd.
Registry name: SAFENAMES-AS Safenames Ltd., GB · not in PeeringDB
63IPv4 routes
100.0% RPKI valid · 100.0% with a route object
2IPv6 routes
100.0% RPKI valid · 50.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
1 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
15Route objects not announced
registered with origin AS60819, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS60819, 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.
| 2a00:a900:7afe::/48 | Valid | Nonecovered by 2a00:a900::/32 | 634 100% |
| 31.3.64.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 31.3.64.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 31.3.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.14.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.102.117.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 84.247.17.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 84.247.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.104.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.104.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.105.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.106.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.106.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.106.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.33.82.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.33.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.34.109.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.34.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.34.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.42.58.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.244.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.46.63.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.47.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.114.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.113.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.113.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.114.48.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.247.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.176.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.96.161.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.191.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.191.160.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.191.161.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.191.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.191.163.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.208.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.208.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.212.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.58.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.214.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.240.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.240.197.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.241.8.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.241.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.241.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.241.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.240.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.242.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.243.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.250.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.251.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.254.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.19.255.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.114.49.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.19.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.241.145.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a00:a900::/32 | Valid | RIR databaseRADB, RIPE | 636 100% |
AS-SET
AS60819 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 16 are in fix.csv.
- Route object: none1
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a00:a900:7afe::/48 | No route object for it. A route object for 2a00:a900::/32 with origin AS60819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60819 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60819 whose prefix no peer sees AS60819 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.3.64.0/24 | RIPE | Valid |
| 31.3.65.0/24 | RIPE | Valid |
| 31.3.67.0/24 | RIPE | Valid |
| 31.3.68.0/24 | RIPE | Valid |
| 31.3.69.0/24 | RIPE | Valid |
| 31.3.70.0/24 | RIPE | Valid |
| 31.3.71.0/24 | RIPE | Valid |
| 31.14.216.0/23 | RIPE | No ROA |
| 217.19.240.0/20 | RIPE | No ROA |
| 217.19.240.0/21 | RIPE | No ROA |
| 217.19.244.0/24 | RIPE | Valid |
| 217.19.245.0/24 | RIPE | Invalid: maxLength |
| 217.19.246.0/24 | RIPE | Invalid: maxLength |
| 217.19.247.0/24 | RIPE | Invalid: maxLength |
| 217.19.248.0/21 | 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.