Network · data from 2026-11-12
AS265753 AS265753 - CW HOLDINGS, S.A.
Registry name: AS265753 - CW HOLDINGS, S.A., HN · not in PeeringDB
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% |
| 2803:ebc0::/32 | Valid | Other IRR onlyRIPE-NONAUTH | 635 100% |
| 23.227.84.0/22 | Valid | RIR databaseARIN | 673 100% |
| 91.242.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.242.81.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.242.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.214.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 107.166.0.0/22 | Valid | RIR databaseARIN | 673 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 131.196.52.0/22 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 2803:ebc0::/32 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
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.