Network · data from 2026-11-12
AS216258 eox-faster EOX IT Services GmbH
Registry name: eox-faster EOX IT Services GmbH, AT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216258, 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:2140:900::/48 | Valid | Nonecovered by 2a13:2140::/32 | 634 100% |
| 2a13:2144:1::/48 | Valid | Nonecovered by 2a13:2144::/32 | 634 100% |
| 2a13:2144:2::/48 | Valid | Nonecovered by 2a13:2144::/32 | 634 100% |
| 2a13:2144:3::/48 | Valid | Nonecovered by 2a13:2144::/32 | 634 100% |
| 2a13:2144:4::/48 | Valid | Nonecovered by 2a13:2144::/32 | 634 100% |
| 2a13:2144:5::/48 | Valid | Nonecovered by 2a13:2144::/32 | 634 100% |
| 2a13:2144:6::/48 | Valid | Nonecovered by 2a13:2144::/32 | 634 100% |
| 92.42.98.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a13:2140:25::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:2140:53::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:2140:80::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:2140:389::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:2141:1::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:2142:1::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:2147:1::/48 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS216258 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 13 are in fix.csv.
- Route object: none7
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a13:2140:900::/48 | No route object for it. A route object for 2a13:2140::/32 with origin AS216258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216258 in the RIR database for the space. |
| Route object: none | 2a13:2144:1::/48 | No route object for it. A route object for 2a13:2144::/32 with origin AS216258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216258 in the RIR database for the space. |
| Route object: none | 2a13:2144:2::/48 | No route object for it. A route object for 2a13:2144::/32 with origin AS216258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216258 in the RIR database for the space. |
| Route object: none | 2a13:2144:3::/48 | No route object for it. A route object for 2a13:2144::/32 with origin AS216258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216258 in the RIR database for the space. |
| Route object: none | 2a13:2144:4::/48 | No route object for it. A route object for 2a13:2144::/32 with origin AS216258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216258 in the RIR database for the space. |
| Route object: none | 2a13:2144:5::/48 | No route object for it. A route object for 2a13:2144::/32 with origin AS216258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216258 in the RIR database for the space. |
| Route object: none | 2a13:2144:6::/48 | No route object for it. A route object for 2a13:2144::/32 with origin AS216258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216258 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS216258 whose prefix no peer sees AS216258 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:2140::/32 | RIPE | Valid |
| 2a13:2140:5222::/48 | RIPE | Valid |
| 2a13:2141:2::/48 | RIPE | Valid |
| 2a13:2142:2::/48 | RIPE | Valid |
| 2a13:2143:1::/48 | RIPE | Valid |
| 2a13:2144::/32 | 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.