Network · data from 2026-11-12
AS207631 CLOUD88 Cloud88 S.R.L.
Registry name: CLOUD88 Cloud88 S.R.L., IT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207631, 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.
| 2001:678:bd0::/48 | No ROA | Other IRR onlyRADB | 636 100% |
| 2a06:e881:7200::/40 | No ROA | Other IRR onlyRADB | 636 100% |
| 185.133.209.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 185.197.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS207631 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: none2
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:678:bd0::/48 | No ROA covers it. Add a ROA for AS207631, maxLength 48. |
| Route object: RIR | 2001:678:bd0::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2a06:e881:7200::/40 | No ROA covers it. Add a ROA for AS207631, maxLength 40. |
| Route object: RIR | 2a06:e881:7200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 185.133.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS207631 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.