Network · data from 2026-11-12
AS400596 ELIXIOR.CLOUD
Registry name: ELIXIOR-CLOUD - Technologies Elixior, CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400596, 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.
| 23.132.28.0/24 | Valid | RIR databaseARIN | 671 100% |
| 2602:f758::/40 | Valid | RIR databaseARIN | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS400596: AS-ELIXIOR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS400596 isn't in the set, or no route object for AS400596 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS400596 in it | Not covered |
|---|---|---|---|---|---|
| AS-ELIXIOR | ARIN | 2 | 1 | Yes | 0 |
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS400596 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.