bgpreport

Network · data from 2026-11-12

AS399643 COOKSON HILLS CONNECT

Registry name: COOKSONHILLS-CONNECT-21 - COOKSON HILLS CONNECT, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399643, 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.
144.126.170.0/24 No ROA Nonecovered by 144.126.160.0/19 673 100% 67
144.126.180.0/24 No ROA Nonecovered by 144.126.160.0/19 673 100% 67
144.126.181.0/24 No ROA Nonecovered by 144.126.160.0/19 673 100% 67
144.126.182.0/24 No ROA Nonecovered by 144.126.160.0/19 673 100% 67
144.126.160.0/19 No ROA RIR databaseARIN 671 100% 68
212.178.224.0/19 No ROA RIR databaseARIN 671 100% 68

AS-SET

AS399643'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 11 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none144.126.170.0/24No ROA covers it. Add a ROA for AS399643, maxLength 24.673 of 673
Route object: none144.126.170.0/24No route object for it. A route object for 144.126.160.0/19 with origin AS399643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399643 in the RIR database for the space.673 of 673
ROA: none144.126.180.0/24No ROA covers it. Add a ROA for AS399643, maxLength 24.673 of 673
Route object: none144.126.180.0/24No route object for it. A route object for 144.126.160.0/19 with origin AS399643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399643 in the RIR database for the space.673 of 673
ROA: none144.126.181.0/24No ROA covers it. Add a ROA for AS399643, maxLength 24.673 of 673
Route object: none144.126.181.0/24No route object for it. A route object for 144.126.160.0/19 with origin AS399643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399643 in the RIR database for the space.673 of 673
ROA: none144.126.182.0/24No ROA covers it. Add a ROA for AS399643, maxLength 24.673 of 673
Route object: none144.126.182.0/24No route object for it. A route object for 144.126.160.0/19 with origin AS399643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399643 in the RIR database for the space.673 of 673
ROA: none144.126.160.0/19No ROA covers it. Add a ROA for AS399643, maxLength 19.671 of 673
ROA: none212.178.224.0/19No ROA covers it. Add a ROA for AS399643, maxLength 19.671 of 673

Route objects not announced

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

67.220.53.0/24ARINValid

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.