Network · data from 2026-11-12
AS40178 OCEANBLUE-CLOUD-US - OCEANBLUE CLOUD, INC.
Registry name: OCEANBLUE-CLOUD-US - OCEANBLUE CLOUD, INC., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40178, 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.
| 38.22.127.0/24 | No ROA | None | 0 0%low visibility |
| 23.145.156.0/24 | Valid | RIR databaseARIN | 673 100% |
| 163.8.215.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
AS40178 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 6 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.22.127.0/24 | No ROA covers it. Add a ROA for AS40178, maxLength 24. |
| Route object: none | 38.22.127.0/24 | No route object for it. Add a route object with origin AS40178 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40178 whose prefix no peer sees AS40178 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.109.98.0/24 | RADB | No ROA |
| 156.236.85.0/24 | AFRINIC | Invalid: origin |
| 188.92.121.0/24 | RIPE | Valid |
| 2001:df7:3703::/48 | APNIC | Valid |
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.