Network · data from 2026-11-12
AS16084 EON-IS E.ON Digital Technology GmbH
Registry name: EON-IS E.ON Digital Technology GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16084, 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.
| 153.100.8.0/24 | Valid | None | 673 100% |
| 193.26.56.0/22 | Valid | Nonecovered by 193.26.56.0/21 | 673 100% |
| 193.26.59.0/24 | Valid | Nonecovered by 193.26.56.0/21 | 673 100% |
| 193.26.60.0/22 | Valid | Nonecovered by 193.26.56.0/21 | 672 100% |
| 193.26.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS16084 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 18 are in fix.csv.
- Route object: none4
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 153.100.8.0/24 | No route object for it. Add a route object with origin AS16084 in the RIR database for the space. |
| Route object: none | 193.26.56.0/22 | No route object for it. A route object for 193.26.56.0/21 with origin AS16084 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16084 in the RIR database for the space. |
| Route object: none | 193.26.59.0/24 | No route object for it. A route object for 193.26.56.0/21 with origin AS16084 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16084 in the RIR database for the space. |
| Route object: none | 193.26.60.0/22 | No route object for it. A route object for 193.26.56.0/21 with origin AS16084 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16084 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16084 whose prefix no peer sees AS16084 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.217.0.0/16 | RIPE | No ROA |
| 192.71.129.0/24 | RIPE | No ROA |
| 192.71.130.0/24 | RIPE | No ROA |
| 192.71.217.0/24 | RIPE | No ROA |
| 193.26.32.0/19 | RIPE | No ROA |
| 193.26.36.0/24 | RIPE | No ROA |
| 193.26.52.0/23 | RIPE | No ROA |
| 193.235.204.0/24 | RIPE | No ROA |
| 194.68.8.0/22 | RIPE | No ROA |
| 194.103.152.0/24 | RIPE | No ROA |
| 194.132.140.0/24 | RIPE | No ROA |
| 194.132.141.0/24 | RIPE | No ROA |
| 217.67.32.0/20 | RIPE | No ROA |
| 217.67.33.0/24 | RIPE | No ROA |
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.