bgpreport

Network · data from 2026-11-12

AS265753 AS265753 - CW HOLDINGS, S.A.

Registry name: AS265753 - CW HOLDINGS, S.A., HN · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.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 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS265753, seen from no peer

Announced routes

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

131.196.52.0/22 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
2803:ebc0::/32 Valid Other IRR onlyRIPE-NONAUTH 635 100% 68
23.227.84.0/22 Valid RIR databaseARIN 673 100% 67
91.242.71.0/24 Valid RIR databaseRIPE 673 100% 67
91.242.81.0/24 Valid RIR databaseRIPE 673 100% 67
91.242.107.0/24 Valid RIR databaseRIPE 673 100% 67
95.214.152.0/22 Valid RIR databaseRIPE 673 100% 67
107.166.0.0/22 Valid RIR databaseARIN 673 100% 67

AS-SET

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

  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: RIR131.196.52.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR2803:ebc0::/32Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS265753 is announced.

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.