Network · data from 2026-11-12
AS36027 CLOUDWYZE - CloudWyze, Inc.
Registry name: CLOUDWYZE - CloudWyze, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36027, 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.
| 158.120.76.0/23 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS36027 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 5 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 158.120.76.0/23 | No ROA covers it. Add a ROA for AS36027, maxLength 23. |
| Route object: RIR | 158.120.76.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36027 whose prefix no peer sees AS36027 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.155.80.0/24 | RADB | No ROA |
| 141.193.212.0/24 | ARIN, RADB | No ROA |
| 2605:b840::/32 | ARIN, RADB | No 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.