bgpreport

Network · data from 2026-11-12

AS19409 VWCREDIT-COM - VW CREDIT, INC

Registry name: VWCREDIT-COM - VW CREDIT, INC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19409, 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.
63.174.218.0/24 No ROA Other origin only 561 83% 63
199.5.59.0/24 Valid RIR databaseARIN, RADB 651 97% 67
199.5.60.0/24 Valid RIR databaseARIN, RADB 651 97% 67
199.5.61.0/24 Valid RIR databaseARIN, RADB 651 97% 67
199.5.63.0/24 Valid RIR databaseARIN, RADB 650 97% 67

AS-SET

AS19409 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none63.174.218.0/24No ROA covers it. Add a ROA for AS19409, maxLength 24.561 of 673
Route object: none63.174.218.0/24Route objects for it name AS7922. Add a route object with origin AS19409 in the RIR database for the space.561 of 673

Route objects not announced

Every route object with origin AS19409 is announced.

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.