bgpreport

Network · data from 2026-11-12

AS402056 WIDEWIRED

Registry name: WIDEWIRED - WideWired, US · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 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 AS402056, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS402056, 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.
2602:f3c3::/48 Valid Nonecovered by 2602:f3c3::/40 3 0%low visibility 3
66.92.163.0/24 Valid RIR databaseARIN, RADB 672 100% 67
198.252.150.0/24 Valid RIR databaseARIN 672 100% 67
2602:f3c3::/40 Valid RIR databaseARIN 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS402056: ARIN::AS402056:AS-WIDEWIRED. 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 (AS402056 isn't in the set, or no route object for AS402056 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 objectsAS402056 in itNot covered
ARIN::AS402056:AS-WIDEWIRED ARIN 113 Yes 0

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

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2602:f3c3::/48No route object for it. A route object for 2602:f3c3::/40 with origin AS402056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402056 in the RIR database for the space.3 of 636

Route objects not announced

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