Network · data from 2026-11-12
AS40253 Elysia Root L.C.
Registry name: ELYSIA-ROOT-LC - Elysia Root L.C., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40253, 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.
| 69.36.44.0/24 | Valid | Nonecovered by 69.36.44.0/22 | 672 100% |
| 69.36.45.0/24 | Valid | Nonecovered by 69.36.44.0/22 | 672 100% |
| 69.36.46.0/24 | Valid | Nonecovered by 69.36.44.0/22 | 672 100% |
| 2.27.104.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 2602:f494::/36 | Valid | RIR databaseARIN | 634 100% |
| 2602:f494::/48 | Valid | RIR databaseARIN | 634 100% |
| 2602:f494:3::/48 | Valid | RIR databaseARIN | 634 100% |
| 2602:f494:10::/44 | Valid | RIR databaseARIN | 634 100% |
| 2602:fed2:7080::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS40253: ARIN::AS-ELYSIA. 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 (AS40253 isn't in the set, or no route object for AS40253 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 | AS40253 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-ELYSIA | ARIN | 1 | 1 | Yes | 0 |
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.
- Route object: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 69.36.44.0/24 | No route object for it. A route object for 69.36.44.0/22 with origin AS40253 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40253 in the RIR database for the space. |
| Route object: none | 69.36.45.0/24 | No route object for it. A route object for 69.36.44.0/22 with origin AS40253 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40253 in the RIR database for the space. |
| Route object: none | 69.36.46.0/24 | No route object for it. A route object for 69.36.44.0/22 with origin AS40253 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40253 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40253 whose prefix no peer sees AS40253 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.36.44.0/22 | ARIN | Valid |
| 2602:f494:1::/48 | ARIN | Invalid: maxLength |
| 2602:f494:2::/48 | ARIN | 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.