bgpreport

Network · data from 2026-11-12

AS11994 Gatespeed Broadband

Registry name: CZIO-ASN - Cruzio, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11994, 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.
161.129.228.0/24 No ROA None 670 100% 69
161.129.224.0/24 No ROA Other origin only 579 86% 69
44.31.128.0/22 No ROA Other IRR onlyRADB 670 100% 68
69.27.176.0/20 No ROA Other IRR onlyRADB 670 100% 68
192.135.76.0/24 No ROA Other IRR onlyRADB 670 100% 68
192.135.198.0/24 No ROA Other IRR onlyRADB 670 100% 68
198.202.199.0/24 No ROA Other IRR onlyRADB 670 100% 68
198.232.247.0/24 No ROA Other IRR onlyRADB 670 100% 68
199.73.112.0/22 No ROA Other IRR onlyRADB 670 100% 68
207.89.57.0/24 No ROA Other IRR onlyRADB 228 34% 59
216.173.128.0/21 Valid Nonecovered by 216.173.128.0/20 669 99% 68
216.173.136.0/21 Valid Nonecovered by 216.173.128.0/20 669 99% 68
68.170.176.0/21 Valid Other IRR onlyRADB 670 100% 68
216.173.128.0/20 Valid RIR databaseARIN, RADB 672 100% 67
63.249.64.0/18 Valid RIR databaseARIN, RADB 670 100% 68

AS-SET

AS11994'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 38 are in fix.csv.

  • ROA: none10
  • Route object: none4
  • Route object: RIR9
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none161.129.228.0/24No ROA covers it. Add a ROA for AS11994, maxLength 24.670 of 673
Route object: none161.129.228.0/24No route object for it. Add a route object with origin AS11994 in the RIR database for the space.670 of 673
ROA: none161.129.224.0/24No ROA covers it. Add a ROA for AS11994, maxLength 24.579 of 673
Route object: none161.129.224.0/24Route objects for it name AS27348. Add a route object with origin AS11994 in the RIR database for the space.579 of 673
ROA: none44.31.128.0/22No ROA covers it. Add a ROA for AS11994, maxLength 22.670 of 673
Route object: RIR44.31.128.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none69.27.176.0/20No ROA covers it. Add a ROA for AS11994, maxLength 20.670 of 673
Route object: RIR69.27.176.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.135.76.0/24No ROA covers it. Add a ROA for AS11994, maxLength 24.670 of 673
Route object: RIR192.135.76.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.135.198.0/24No ROA covers it. Add a ROA for AS11994, maxLength 24.670 of 673
Route object: RIR192.135.198.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.202.199.0/24No ROA covers it. Add a ROA for AS11994, maxLength 24.670 of 673
Route object: RIR198.202.199.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.232.247.0/24No ROA covers it. Add a ROA for AS11994, maxLength 24.670 of 673
Route object: RIR198.232.247.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none199.73.112.0/22No ROA covers it. Add a ROA for AS11994, maxLength 22.670 of 673
Route object: RIR199.73.112.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none207.89.57.0/24No ROA covers it. Add a ROA for AS11994, maxLength 24.228 of 673
Route object: RIR207.89.57.0/24Route object only in RADB. Add it in the RIR database for the space.228 of 673
Route object: none216.173.128.0/21No route object for it. A route object for 216.173.128.0/20 with origin AS11994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11994 in the RIR database for the space.669 of 673
Route object: none216.173.136.0/21No route object for it. A route object for 216.173.128.0/20 with origin AS11994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11994 in the RIR database for the space.669 of 673
Route object: RIR68.170.176.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

63.249.64.0/20RADBValid
63.249.80.0/22RADBValid
63.249.92.0/22RADBValid
63.249.96.0/21RADBValid
63.249.108.0/24RADBValid
63.249.120.0/21RADBValid
68.170.176.0/20ARINValid
69.27.176.0/22RADBNo ROA
69.27.176.0/24RADBNo ROA
69.27.177.0/24RADBNo ROA
69.27.180.0/22RADBNo ROA
69.27.184.0/22RADBNo ROA
69.27.188.0/22RADBNo ROA
216.168.143.0/24RADBNo ROA
2001:470:e2::/48ARINValid

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.