bgpreport

Network · data from 2026-11-12

AS399896 VWNA-AS3 - Volkswagen Group of America, Inc.

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

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

Announced routes

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

199.5.54.0/24 Invalid: maxLength Nonecovered by 199.5.32.0/19 1 0%low visibility 1
199.5.32.0/19 Valid RIR databaseARIN 672 100% 67

AS-SET

AS399896 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 4 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength199.5.54.0/24ROA 199.5.32.0/19 AS399896 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 199.5.54.0/24.1 of 673
Route object: none199.5.54.0/24No route object for it. A route object for 199.5.32.0/19 with origin AS399896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399896 in the RIR database for the space.1 of 673

Route objects not announced

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

167.253.44.0/23ARINNo ROA
167.253.44.0/24ARINNo 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.