Network · data from 2026-11-12
AS402976 BLUE-CLOUD - Robeing
Registry name: BLUE-CLOUD - Robeing, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402976, 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.
| 217.217.4.0/24 | Valid | None | 673 100% |
AS-SET
AS402976 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 20 are in fix.csv.
- Route object: none1
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.217.4.0/24 | No route object for it. Add a route object with origin AS402976 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402976 whose prefix no peer sees AS402976 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 13.141.122.0/24 | RADB, RIPE | Valid |
| 64.50.165.0/24 | ARIN, RADB | Valid |
| 64.226.204.0/24 | RADB, RIPE | Valid |
| 66.132.211.0/24 | RADB, RIPE | Valid |
| 69.90.32.0/24 | RADB, RIPE | Valid |
| 69.90.227.0/24 | RADB, RIPE | Valid |
| 86.38.255.0/24 | RADB, RIPE | Valid |
| 91.124.216.0/24 | RADB, RIPE | Valid |
| 91.124.221.0/24 | RADB, RIPE | Valid |
| 91.239.148.0/24 | ARIN, RADB | Valid |
| 92.112.22.0/24 | RADB, RIPE | Valid |
| 92.112.215.0/24 | RADB, RIPE | Valid |
| 92.113.184.0/24 | RADB, RIPE | Valid |
| 94.118.20.0/24 | RADB, RIPE | Valid |
| 95.134.23.0/24 | RADB, RIPE | Valid |
| 95.134.125.0/24 | RADB, RIPE | Valid |
| 95.135.193.0/24 | RADB, RIPE | Valid |
| 178.18.151.0/24 | RIPE | Valid |
| 188.220.215.0/24 | RADB, RIPE | 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.