bgpreport

Network · data from 2026-11-12

AS205505 Volkswagen Financial Services

Registry name: DE-VWFS-AS01 Volkswagen Financial Services AG, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205505, 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.
91.198.139.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
185.60.96.0/24 No ROA RIR databaseRIPE 673 100% 66
185.60.97.0/24 No ROA RIR databaseRIPE 673 100% 66
185.60.98.0/24 No ROA RIR databaseRIPE 673 100% 66
185.60.99.0/24 No ROA RIR databaseRIPE 673 100% 66
193.25.182.0/24 No ROA RIR databaseRIPE 673 100% 66
193.25.183.0/24 No ROA RIR databaseRIPE 673 100% 66
2a04:8f40:1000::/48 No ROA RIR databaseRIPE 635 100% 67
2a04:8f40:2000::/48 No ROA RIR databaseRIPE 635 100% 67
2a04:8f40:ffff::/48 No ROA RIR databaseRIPE 635 100% 67

AS-SET

AS205505'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 15 are in fix.csv.

  • ROA: none10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none91.198.139.0/24No ROA covers it. Add a ROA for AS205505, maxLength 24.673 of 673
ROA: none185.60.96.0/24No ROA covers it. Add a ROA for AS205505, maxLength 24.673 of 673
ROA: none185.60.97.0/24No ROA covers it. Add a ROA for AS205505, maxLength 24.673 of 673
ROA: none185.60.98.0/24No ROA covers it. Add a ROA for AS205505, maxLength 24.673 of 673
ROA: none185.60.99.0/24No ROA covers it. Add a ROA for AS205505, maxLength 24.673 of 673
ROA: none193.25.182.0/24No ROA covers it. Add a ROA for AS205505, maxLength 24.673 of 673
ROA: none193.25.183.0/24No ROA covers it. Add a ROA for AS205505, maxLength 24.673 of 673
ROA: none2a04:8f40:1000::/48No ROA covers it. Add a ROA for AS205505, maxLength 48.635 of 636
ROA: none2a04:8f40:2000::/48No ROA covers it. Add a ROA for AS205505, maxLength 48.635 of 636
ROA: none2a04:8f40:ffff::/48No ROA covers it. Add a ROA for AS205505, maxLength 48.635 of 636

Route objects not announced

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

185.60.96.0/22RADBNo ROA
193.25.182.0/23RADB, RIPENo ROA
2a04:8f40::/32RADBNo ROA
2a04:8f40:2::/48RIPENo ROA
2a04:8f40:3000::/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.