bgpreport

Network · data from 2026-11-12

AS201917 VF-GROUP-DC1 Vodafone Group Services GmbH

Registry name: VF-GROUP-DC1 Vodafone Group Services GmbH, DE · not in PeeringDB

33IPv4 routes 100.0% RPKI valid · 93.9% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS201917, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201917, 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.
46.108.222.0/24 Valid None 673 100% 67
139.47.206.0/24 Valid None 673 100% 67
46.190.217.0/24 Valid RIR databaseRIPE 673 100% 67
46.190.223.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.25.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.31.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.81.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.85.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.86.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.114.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.141.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.146.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.212.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.214.0/24 Valid RIR databaseRIPE 673 100% 67
47.73.250.0/24 Valid RIR databaseRIPE 673 100% 67
139.47.179.0/24 Valid RIR databaseRIPE 673 100% 67
139.47.196.0/22 Valid RIR databaseRIPE 673 100% 67
139.47.200.0/22 Valid RIR databaseRIPE 673 100% 67
139.47.212.0/22 Valid RIR databaseRIPE 673 100% 67
194.20.64.0/20 Valid RIR databaseRIPE 673 100% 67
194.20.64.0/21 Valid RIR databaseRIPE 673 100% 67
194.20.70.0/24 Valid RIR databaseRIPE 673 100% 67
194.20.72.0/22 Valid RIR databaseRIPE 673 100% 67
194.20.76.0/22 Valid RIR databaseRIPE 673 100% 67
195.232.146.0/24 Valid RIR databaseRIPE 673 100% 67
195.232.147.0/24 Valid RIR databaseRIPE 673 100% 67
195.233.149.0/24 Valid RIR databaseRIPE 673 100% 67
195.233.155.0/24 Valid RIR databaseRIPE 673 100% 67
37.25.147.0/24 Valid RIR databaseRIPE 672 100% 67
37.25.148.0/24 Valid RIR databaseRIPE 672 100% 67
37.25.168.0/24 Valid RIR databaseRIPE 672 100% 67
37.25.171.0/24 Valid RIR databaseRIPE 672 100% 67
37.25.244.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS201917 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 14 are in fix.csv.

  • Route object: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none46.108.222.0/24No route object for it. Add a route object with origin AS201917 in the RIR database for the space.673 of 673
Route object: none139.47.206.0/24No route object for it. Add a route object with origin AS201917 in the RIR database for the space.673 of 673

Route objects not announced

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

37.25.169.0/24RIPEValid
37.25.228.0/26RIPEInvalid: maxLength
45.144.96.0/22RIPEValid
46.190.245.192/26RIPEInvalid: maxLength
47.73.24.0/24RIPEValid
47.73.118.0/23RIPEValid
47.73.142.0/24RIPEValid
85.205.253.192/27RIPEInvalid: origin
139.47.183.64/28RIPEInvalid: maxLength
176.125.20.128/26RIPEInvalid: origin
176.125.29.0/26RIPEInvalid: origin
176.125.29.224/27RIPEInvalid: 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.