bgpreport

Network · data from 2026-11-12

AS21217 Vaultica Data Centers AS21217

Registry name: SAFEHOSTNET Infrastructure Switzerland Colo Sarl, CH · PeeringDB

13IPv4 routes 100.0% RPKI valid · 92.3% with a route object
1IPv6 routes 100.0% RPKI valid · 100.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
22Route objects not announced registered with origin AS21217, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21217, 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.

185.247.9.0/24 Valid Nonecovered by 185.247.8.0/22 673 100% 66
80.80.224.0/21 Valid RIR databaseRIPE 673 100% 66
80.80.232.0/22 Valid RIR databaseRIPE 673 100% 66
80.80.236.0/23 Valid RIR databaseRIPE 673 100% 66
83.97.120.0/22 Valid RIR databaseRIPE 673 100% 66
185.169.95.0/24 Valid RIR databaseRIPE 673 100% 66
185.247.8.0/22 Valid RIR databaseRIPE 673 100% 66
194.88.9.0/24 Valid RIR databaseRIPE 673 100% 66
193.72.147.0/24 Valid RIR databaseRIPE 672 100% 66
91.199.255.0/24 Valid RIR databaseRIPE 671 100% 66
185.169.92.0/23 Valid RIR databaseRIPE 671 100% 66
185.254.152.0/24 Valid RIR databaseRIPE 671 100% 66
80.80.238.0/24 Valid RIR databaseRIPE 670 100% 66
2001:40c0::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS21217's PeeringDB record names no 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 23 are in fix.csv.

  • Route object: none1
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
Route object: none185.247.9.0/24No route object for it. A route object for 185.247.8.0/22 with origin AS21217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21217 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS21217 whose prefix no peer sees AS21217 announce. Many are kept on purpose (backup routes, space announced only in some places).

80.80.224.0/24RIPEInvalid: maxLength
80.80.225.0/24RIPEInvalid: maxLength
80.80.226.0/24RIPEInvalid: maxLength
80.80.227.0/24RIPEInvalid: maxLength
80.80.228.0/24RIPEInvalid: maxLength
80.80.229.0/24RIPEInvalid: maxLength
80.80.230.0/24RIPEInvalid: maxLength
80.80.231.0/24RIPEInvalid: maxLength
80.80.232.0/24RIPEInvalid: maxLength
80.80.233.0/24RIPEInvalid: maxLength
80.80.234.0/24RIPEInvalid: maxLength
80.80.235.0/24RIPEInvalid: maxLength
80.80.236.0/24RIPEInvalid: maxLength
80.80.237.0/24RIPEInvalid: maxLength
185.169.92.0/22RIPENo ROA
185.254.152.0/22RIPENo ROA
185.254.153.0/24RIPENo ROA
185.254.154.0/24RIPENo ROA
185.254.155.0/24RIPENo ROA
2001:40c0::/32RIPENo ROA
2001:40c0::/40RIPENo ROA
2a00:77c0::/48RIPENo 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.