bgpreport

Network · data from 2026-11-12

AS73 University of Washington

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

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

Announced routes

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

69.91.192.0/18 No ROA Other IRR onlyRADB 672 100% 68
128.95.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
128.208.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
140.142.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
173.250.160.0/19 No ROA Other IRR onlyRADB 672 100% 68
198.48.64.0/19 No ROA Other IRR onlyRADB 672 100% 68
205.175.96.0/19 No ROA Other IRR onlyRADB 672 100% 68
108.179.140.0/22 No ROA Other IRR onlyRADB 670 100% 68
192.26.136.0/24 No ROA Other IRR onlyRADB 670 100% 68
192.42.144.0/24 No ROA Other IRR onlyRADB 670 100% 68
2607:4000::/32 No ROA Other IRR onlyRADB 636 100% 68

AS-SET

AS73's PeeringDB record names no 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 24 are in fix.csv.

  • ROA: none11
  • Route object: RIR11
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none69.91.192.0/18No ROA covers it. Add a ROA for AS73, maxLength 18.672 of 673
Route object: RIR69.91.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none128.95.0.0/16No ROA covers it. Add a ROA for AS73, maxLength 16.672 of 673
Route object: RIR128.95.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none128.208.0.0/16No ROA covers it. Add a ROA for AS73, maxLength 16.672 of 673
Route object: RIR128.208.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none140.142.0.0/16No ROA covers it. Add a ROA for AS73, maxLength 16.672 of 673
Route object: RIR140.142.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none173.250.160.0/19No ROA covers it. Add a ROA for AS73, maxLength 19.672 of 673
Route object: RIR173.250.160.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.48.64.0/19No ROA covers it. Add a ROA for AS73, maxLength 19.672 of 673
Route object: RIR198.48.64.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.175.96.0/19No ROA covers it. Add a ROA for AS73, maxLength 19.672 of 673
Route object: RIR205.175.96.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none108.179.140.0/22No ROA covers it. Add a ROA for AS73, maxLength 22.670 of 673
Route object: RIR108.179.140.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.26.136.0/24No ROA covers it. Add a ROA for AS73, maxLength 24.670 of 673
Route object: RIR192.26.136.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.42.144.0/24No ROA covers it. Add a ROA for AS73, maxLength 24.670 of 673
Route object: RIR192.42.144.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2607:4000::/32No ROA covers it. Add a ROA for AS73, maxLength 32.636 of 636
Route object: RIR2607:4000::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

204.69.8.0/21RADBValid
204.69.15.0/24RADBValid

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.