bgpreport

Network · data from 2026-11-12

AS397606 Crowsnest Broadband, LLC

Registry name: CROWSNEST-BROADBAND-LLC - Crowsnest Broadband, US · PeeringDB

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

Announced routes

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

208.86.196.0/24 Valid Nonecovered by 208.86.196.0/22 671 100% 67
208.94.224.0/24 Valid Nonecovered by 208.94.224.0/21 671 100% 67
208.94.225.0/24 Valid Nonecovered by 208.94.224.0/21 671 100% 67
208.94.226.0/24 Valid Nonecovered by 208.94.224.0/21 671 100% 67
208.94.228.0/24 Valid Nonecovered by 208.94.224.0/21 671 100% 67
170.39.208.0/24 Valid Other IRR onlyRADB 671 100% 67
170.39.209.0/24 Valid Other IRR onlyRADB 671 100% 67
170.39.210.0/24 Valid Other IRR onlyRADB 671 100% 67
170.39.211.0/24 Valid Other IRR onlyRADB 671 100% 67
207.174.68.0/24 Valid Other IRR onlyRADB 671 100% 67
207.174.69.0/24 Valid Other IRR onlyRADB 671 100% 67
207.174.70.0/24 Valid Other IRR onlyRADB 671 100% 67
207.174.71.0/24 Valid Other IRR onlyRADB 671 100% 67
216.152.68.0/24 Valid Other IRR onlyRADB 671 100% 67
216.152.69.0/24 Valid Other IRR onlyRADB 671 100% 67
64.52.102.0/23 Valid RIR databaseARIN, RADB 671 100% 67
66.118.49.0/24 Valid RIR databaseARIN 671 100% 67
130.51.152.0/22 Valid RIR databaseARIN 671 100% 67
147.160.51.0/24 Valid RIR databaseALTDB, ARIN 671 100% 67
208.93.4.0/22 Valid RIR databaseARIN, RADB 671 100% 67
2605:4940::/32 Valid RIR databaseARIN, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS397606: RS-CROWSNEST. 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 (AS397606 isn't in the set, or no route object for AS397606 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 objectsAS397606 in itNot covered
RS-CROWSNEST A route-set, not an AS-SET; route-sets aren't expanded.

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

  • Route object: none5
  • Route object: RIR10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none208.86.196.0/24No route object for it. A route object for 208.86.196.0/22 with origin AS397606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397606 in the RIR database for the space.671 of 673
Route object: none208.94.224.0/24No route object for it. A route object for 208.94.224.0/21 with origin AS397606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397606 in the RIR database for the space.671 of 673
Route object: none208.94.225.0/24No route object for it. A route object for 208.94.224.0/21 with origin AS397606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397606 in the RIR database for the space.671 of 673
Route object: none208.94.226.0/24No route object for it. A route object for 208.94.224.0/21 with origin AS397606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397606 in the RIR database for the space.671 of 673
Route object: none208.94.228.0/24No route object for it. A route object for 208.94.224.0/21 with origin AS397606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397606 in the RIR database for the space.671 of 673
Route object: RIR170.39.208.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.39.209.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.39.210.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.39.211.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.174.68.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.174.69.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.174.70.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.174.71.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.152.68.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.152.69.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

170.39.208.0/22ARINValid
207.174.68.0/22ARINValid
208.86.196.0/22ARIN, RADBValid
208.94.224.0/21ARIN, RADBValid
216.152.68.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.