bgpreport

Network · data from 2026-11-12

AS19919 VA SkyWire, LLC

Registry name: VSW - VA SkyWire, LLC, US · PeeringDB

3IPv4 routes 66.7% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS19919, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS19919, 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.
160.19.2.180/32 Invalid: maxLength Nonecovered by 160.19.0.0/20 0 0%low visibility 1
160.19.0.0/20 Valid RIR databaseARIN, RADB 671 100% 68
162.245.128.0/21 Valid RIR databaseARIN, RADB 671 100% 68
2601:1600::/28 Valid RIR databaseARIN, RADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS19919: AS-VSW-1. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS19919 isn't in the set, or no route object for AS19919 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS19919 in itNot covered
AS-VSW-1 ARIN 113 Yes 1

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: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength160.19.2.180/32ROA 160.19.0.0/20 AS19919 has maxLength 20; the route is a /32. Raise the maxLength, or add a ROA for 160.19.2.180/32.0 of 673
Route object: none160.19.2.180/32No route object for it. A route object for 160.19.0.0/20 with origin AS19919 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS19919 in the RIR database for the space.0 of 673

Route objects not announced

Every route object with origin AS19919 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.