bgpreport

Network · data from 2026-11-12

AS19116 Washington Broadband

Registry name: WASHINGTON-BROADBAND - Washington Broadband, Inc., US · PeeringDB

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

Announced routes

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

2606:4680::/42 No ROA Nonecovered by 2606:4680::/32 635 100% 68
38.119.167.0/24 No ROA Other IRR onlyALTDB 670 100% 67
2606:4680::/32 No ROA RIR databaseARIN 635 100% 68
104.245.131.0/24 Valid Other origin onlycovered by 104.245.128.0/21 673 100% 67
104.245.133.0/24 Valid Other origin onlycovered by 104.245.132.0/22 671 100% 67
71.93.26.0/24 Valid None 200 30% 56
71.93.27.0/24 Valid None 200 30% 56
71.94.210.0/24 Valid None 200 30% 56
104.245.128.0/21 Valid RIR databaseARIN 673 100% 67
104.245.128.0/23 Valid RIR databaseARIN 671 100% 67
104.245.130.0/24 Valid RIR databaseARIN 671 100% 67
104.245.132.0/22 Valid RIR databaseARIN 671 100% 67
104.245.135.0/24 Valid RIR databaseARIN 671 100% 67
71.93.22.0/24 Valid RIR databaseARIN 200 30% 56
71.93.23.0/24 Valid RIR databaseARIN 200 30% 56
71.93.24.0/24 Valid RIR databaseARIN 200 30% 56
71.93.25.0/24 Valid RIR databaseARIN 200 30% 56
71.94.208.0/24 Valid RIR databaseARIN 200 30% 56
71.94.209.0/24 Valid RIR databaseARIN 200 30% 56

AS-SET

PeeringDB's irr_as_set for AS19116: AS-19116. 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 (AS19116 isn't in the set, or no route object for AS19116 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 objectsAS19116 in itNot covered
AS-19116 ARIN 010 No 19

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

  • ROA: none3
  • Route object: none6
  • Route object: RIR1
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2606:4680::/42No ROA covers it. Add a ROA for AS19116, maxLength 42.635 of 636
Route object: none2606:4680::/42No route object for it. A route object for 2606:4680::/32 with origin AS19116 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19116 in the RIR database for the space.635 of 636
ROA: none38.119.167.0/24No ROA covers it. Add a ROA for AS19116, maxLength 24.670 of 673
Route object: RIR38.119.167.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none2606:4680::/32No ROA covers it. Add a ROA for AS19116, maxLength 32.635 of 636
Route object: none104.245.131.0/24Route objects for it name AS19166. A route object for 104.245.128.0/21 with origin AS19116 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19116 in the RIR database for the space.673 of 673
Route object: none104.245.133.0/24Route objects for it name AS19166. A route object for 104.245.132.0/22 with origin AS19116 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19116 in the RIR database for the space.671 of 673
Route object: none71.93.26.0/24No route object for it. Add a route object with origin AS19116 in the RIR database for the space.200 of 673
Route object: none71.93.27.0/24No route object for it. Add a route object with origin AS19116 in the RIR database for the space.200 of 673
Route object: none71.94.210.0/24No route object for it. Add a route object with origin AS19116 in the RIR database for the space.200 of 673
AS-SET: own ASNAS-19116AS19116 isn't in AS-19116 (ARIN) once expanded. Add AS19116 to it.

Route objects not announced

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

71.93.22.0/23ARINValid
71.93.24.0/23ARINValid
71.94.208.0/23ARINValid

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.