bgpreport

Network · data from 2026-11-12

AS101 Pacific Northwest Gigapop

Registry name: WASH-NSF-AS - University of Washington, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS101, 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.
2001:1860:8000::/34 Valid Nonecovered by 2001:1860::/32 636 100% 68
2001:1860:c000::/34 Valid Nonecovered by 2001:1860::/32 17 3%low visibility 18
209.124.176.0/20 Valid Other IRR onlyRADB 672 100% 68
209.124.176.0/21 Valid Other IRR onlyRADB 672 100% 68
209.124.184.0/21 Valid Other IRR onlyRADB 672 100% 68
2001:1860::/32 Valid Other IRR onlyRADB 636 100% 68
2001:1860:4000::/34 Valid Other IRR onlyRADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS101: RADB::AS-PNW-GIGAPOP. 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 (AS101 isn't in the set, or no route object for AS101 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 objectsAS101 in itNot covered
RADB::AS-PNW-GIGAPOP RADB1 member set in no database: AS-3477-ALL 5021,264 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 12 are in fix.csv.

  • Route object: none2
  • Route object: RIR5
  • AS-SET: missing member1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2001:1860:8000::/34No route object for it. A route object for 2001:1860::/32 with origin AS101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS101 in the RIR database for the space.636 of 636
Route object: none2001:1860:c000::/34No route object for it. A route object for 2001:1860::/32 with origin AS101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS101 in the RIR database for the space.17 of 636
Route object: RIR209.124.176.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.124.176.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.124.184.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2001:1860::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:1860:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: missing memberRADB::AS-PNW-GIGAPOPAS-PNW-GIGAPOP (RADB) lists AS-3477-ALL; no IRR database read has it.

Route objects not announced

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

207.231.240.0/20RADBValid
209.124.177.0/24RADBValid
2001:504:b::/48RADBValid
2001:1860::/34RADBValid

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.