bgpreport

Network · data from 2026-11-12

AS11693 NULINK - WideOpenWest Finance LLC

Registry name: NULINK - WideOpenWest Finance LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11693, 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.
66.216.192.0/24 Valid None 2 0%low visibility 2
66.216.193.0/24 Valid None 2 0%low visibility 2
66.216.194.0/24 Valid None 2 0%low visibility 2
66.216.196.0/24 Valid None 2 0%low visibility 2
66.216.198.0/23 Valid None 2 0%low visibility 2
66.216.200.0/24 Valid None 2 0%low visibility 2
66.216.212.0/23 Valid None 2 0%low visibility 2
66.216.220.0/24 Valid None 2 0%low visibility 2
66.216.223.0/24 Valid None 2 0%low visibility 2
216.130.128.0/20 Valid None 2 0%low visibility 2
216.130.144.0/24 Valid None 2 0%low visibility 2
216.130.156.0/23 Valid Nonecovered by 216.130.152.0/21 2 0%low visibility 2
216.130.146.0/23 Valid Other IRR onlyBBOI 2 0%low visibility 2
216.130.148.0/22 Valid Other IRR onlyBBOI 2 0%low visibility 2
216.130.152.0/21 Valid Other IRR onlyBBOI 2 0%low visibility 2

AS-SET

AS11693 isn't in PeeringDB, where networks name their 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 33 are in fix.csv.

  • Route object: none12
  • Route object: RIR3
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
Route object: none66.216.192.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.193.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.194.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.196.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.198.0/23No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.200.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.212.0/23No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.220.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none66.216.223.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none216.130.128.0/20No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none216.130.144.0/24No route object for it. Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: none216.130.156.0/23No route object for it. A route object for 216.130.152.0/21 with origin AS11693 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11693 in the RIR database for the space.2 of 673
Route object: RIR216.130.146.0/23Route object only in BBOI. Add it in the RIR database for the space.2 of 673
Route object: RIR216.130.148.0/22Route object only in BBOI. Add it in the RIR database for the space.2 of 673
Route object: RIR216.130.152.0/21Route object only in BBOI. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

205.167.158.0/23RADBNo ROA
209.22.192.0/21BBOINo ROA
209.22.192.0/24RADBNo ROA
209.22.193.0/24BBOI, RADBNo ROA
209.22.194.0/24BBOI, RADBNo ROA
209.22.195.0/24BBOI, RADBNo ROA
209.22.196.0/24BBOI, RADBNo ROA
209.22.197.0/24BBOI, RADBNo ROA
209.22.198.0/24BBOI, RADBNo ROA
209.22.199.0/24BBOI, RADBNo ROA
209.22.200.0/24RADBNo ROA
209.22.201.0/24BBOI, RADBNo ROA
209.22.202.0/24BBOI, RADBNo ROA
209.22.203.0/24BBOI, RADBNo ROA
209.22.204.0/23BBOINo ROA
209.22.204.0/24RADBNo ROA
209.22.205.0/24BBOI, RADBNo ROA
209.22.207.0/24BBOI, RADBNo ROA

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.