Network · data from 2026-11-12
AS216193 Hyperion Cloud SAS
Registry name: AS-HYPERION-CLOUD Hyperion Cloud SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216193, 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.
| 2a13:1c47:c0d1::/48 | Valid | Nonecovered by 2a13:1c47:c0d0::/44 | 630 99% |
| 154.16.229.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 154.16.254.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 2a13:1c47:c0d0::/44 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS216193's PeeringDB record names no 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 3 are in fix.csv.
- Route object: none1
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a13:1c47:c0d1::/48 | No route object for it. A route object for 2a13:1c47:c0d0::/44 with origin AS216193 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216193 in the RIR database for the space. |
| Route object: RIR | 154.16.229.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.16.254.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 AS216193 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.