bgpreport

Network · data from 2026-11-12

AS22567 CWGS - CWGS ENTERPRISES, LLC

Registry name: CWGS - CWGS ENTERPRISES, LLC, US · not in PeeringDB

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

Announced routes

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

64.94.154.128/25 Invalid: maxLength Nonecovered by 64.94.154.0/24 1 0%low visibility 1
64.94.155.128/25 Invalid: maxLength Nonecovered by 64.94.155.0/24 1 0%low visibility 1
149.97.210.64/27 No ROA None 1 0%low visibility 1
198.1.26.0/24 No ROA Other IRR onlyRADB 672 100% 67
198.1.27.0/24 No ROA Other IRR onlyRADB 671 100% 67
64.94.155.0/24 Valid RIR databaseARIN 671 100% 67
64.94.154.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

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

  • ROA: maxLength2
  • ROA: none3
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength64.94.154.128/25ROA 64.94.154.0/24 AS22567 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 64.94.154.128/25.1 of 673
Route object: none64.94.154.128/25No route object for it. A route object for 64.94.154.0/24 with origin AS22567 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS22567 in the RIR database for the space.1 of 673
ROA: maxLength64.94.155.128/25ROA 64.94.155.0/24 AS22567 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 64.94.155.128/25.1 of 673
Route object: none64.94.155.128/25No route object for it. A route object for 64.94.155.0/24 with origin AS22567 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS22567 in the RIR database for the space.1 of 673
ROA: none149.97.210.64/27No ROA covers it. Add a ROA for AS22567, maxLength 27.1 of 673
Route object: none149.97.210.64/27No route object for it. Add a route object with origin AS22567 in the RIR database for the space.1 of 673
ROA: none198.1.26.0/24No ROA covers it. Add a ROA for AS22567, maxLength 24.672 of 673
Route object: RIR198.1.26.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.1.27.0/24No ROA covers it. Add a ROA for AS22567, maxLength 24.671 of 673
Route object: RIR198.1.27.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 AS22567 whose prefix no peer sees AS22567 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.94.154.0/23RADBNo ROA
198.1.26.0/23RADBNo 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.