bgpreport

Network · data from 2026-11-12

AS3810 VWMX-AS - Volkswagen Group of America, Inc.

Registry name: VWMX-AS - Volkswagen Group of America, Inc., US · not in PeeringDB

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

Announced routes

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

148.203.149.0/24 Valid Nonecovered by 148.203.148.0/23 673 100% 70
148.203.150.0/24 Valid Nonecovered by 148.203.0.0/16 673 100% 67
148.203.156.0/22 Valid Nonecovered by 148.203.0.0/16 673 100% 67
148.203.247.0/24 Valid Nonecovered by 148.203.0.0/16 672 100% 67
148.203.128.0/18 Valid Nonecovered by 148.203.0.0/16 670 100% 67
148.203.170.0/23 Valid Nonecovered by 148.203.160.0/19 670 100% 67
148.203.128.0/24 Valid Nonecovered by 148.203.128.0/20 2 0%low visibility 1
148.203.128.0/20 Valid Other IRR onlyRADB 2 0%low visibility 2
148.203.160.0/19 Valid Other IRR onlyRADB 2 0%low visibility 2
148.203.144.0/22 Valid Other IRR onlyRADB 1 0%low visibility 1
148.203.148.0/23 Valid Other IRR onlyRADB 1 0%low visibility 1
148.203.151.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
148.203.208.0/20 Valid RIR databaseLACNIC, RADB 2 0%low visibility 2
148.203.224.0/20 Valid RIR databaseLACNIC, RADB 2 0%low visibility 2
148.203.240.0/22 Valid RIR databaseLACNIC, RADB 2 0%low visibility 2
148.203.244.0/23 Valid RIR databaseLACNIC, RADB 2 0%low visibility 2
148.203.246.0/24 Valid RIR databaseLACNIC, RADB 2 0%low visibility 2
148.203.248.0/21 Valid RIR databaseLACNIC, RADB 2 0%low visibility 2
148.203.0.0/17 Valid RIR databaseLACNIC, RADB 1 0%low visibility 1
148.203.152.0/22 Valid RIR databaseLACNIC, RADB 1 0%low visibility 1

AS-SET

AS3810 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 12 are in fix.csv.

  • Route object: none7
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none148.203.149.0/24No route object for it. A route object for 148.203.148.0/23 with origin AS3810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3810 in the RIR database for the space.673 of 673
Route object: none148.203.150.0/24No route object for it. A route object for 148.203.0.0/16 with origin AS3810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3810 in the RIR database for the space.673 of 673
Route object: none148.203.156.0/22No route object for it. A route object for 148.203.0.0/16 with origin AS3810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3810 in the RIR database for the space.673 of 673
Route object: none148.203.247.0/24No route object for it. A route object for 148.203.0.0/16 with origin AS3810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3810 in the RIR database for the space.672 of 673
Route object: none148.203.128.0/18No route object for it. A route object for 148.203.0.0/16 with origin AS3810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3810 in the RIR database for the space.670 of 673
Route object: none148.203.170.0/23No route object for it. A route object for 148.203.160.0/19 with origin AS3810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3810 in the RIR database for the space.670 of 673
Route object: none148.203.128.0/24No route object for it. A route object for 148.203.128.0/20 with origin AS3810 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3810 in the RIR database for the space.2 of 673
Route object: RIR148.203.128.0/20Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR148.203.160.0/19Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR148.203.144.0/22Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR148.203.148.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

148.203.0.0/16LACNIC, RADBValid

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.