bgpreport

Network · data from 2026-11-12

AS40284 GSCBN

Registry name: GSCBN - Glenwood Springs Community Broadband Network, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40284, 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.72.67.0/24 Valid Nonecovered by 208.72.64.0/21 671 100% 67
64.184.232.0/24 Valid Other IRR onlyRADB 671 100% 67
64.184.233.0/24 Valid Other IRR onlyRADB 671 100% 67
64.184.242.0/24 Valid Other IRR onlyRADB 671 100% 67
64.184.243.0/24 Valid Other IRR onlyRADB 671 100% 67
208.72.64.0/24 Valid Other IRR onlyRADB 671 100% 67
208.72.65.0/24 Valid Other IRR onlyRADB 671 100% 67
208.72.66.0/24 Valid Other IRR onlyRADB 671 100% 67
208.72.68.0/24 Valid Other IRR onlyRADB 671 100% 67
208.72.69.0/24 Valid Other IRR onlyRADB 671 100% 67
208.72.70.0/24 Valid Other IRR onlyRADB 671 100% 67
208.72.71.0/24 Valid Other IRR onlyRADB 671 100% 67
64.184.232.0/23 Valid Other IRR onlyRADB 670 100% 68
64.184.242.0/23 Valid Other IRR onlyRADB 670 100% 68
74.114.4.0/24 Valid Other IRR onlyRADB 670 100% 67
74.114.5.0/24 Valid Other IRR onlyRADB 670 100% 67
74.114.6.0/24 Valid Other IRR onlyRADB 670 100% 67
74.114.7.0/24 Valid Other IRR onlyRADB 670 100% 67
74.114.4.0/22 Valid RIR databaseARIN, RADB 670 100% 68
208.72.64.0/21 Valid RIR databaseARIN, RADB 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS40284: ARIN::AS-CBN. 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 (AS40284 isn't in the set, or no route object for AS40284 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 objectsAS40284 in itNot covered
ARIN::AS-CBN ARIN 3123 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 20 are in fix.csv.

  • Route object: none1
  • Route object: RIR17
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none208.72.67.0/24No route object for it. A route object for 208.72.64.0/21 with origin AS40284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40284 in the RIR database for the space.671 of 673
Route object: RIR64.184.232.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.184.233.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.184.242.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.184.243.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.72.64.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.72.65.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.72.66.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.72.68.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.72.69.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.72.70.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.72.71.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.184.232.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR64.184.242.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.114.4.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.114.5.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.114.6.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.114.7.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

38.19.184.0/24RADBNo ROA
162.246.199.0/24RADBNo 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.