Network · data from 2026-11-12
AS200599 EINSENERGIE-AS eins energie in sachsen GmbH & Co. KG
Registry name: EINSENERGIE-AS eins energie in sachsen GmbH & Co. KG, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200599, 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.
| 185.205.156.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.205.157.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.205.158.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.205.159.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.78.112.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 81.27.232.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 81.27.233.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 81.27.234.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 81.27.235.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 81.27.236.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 81.27.237.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 81.27.238.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a0b:740::/29 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS200599 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 14 are in fix.csv.
- ROA: none13
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.205.156.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 185.205.157.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 185.205.158.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 185.205.159.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 212.78.112.0/20 | No ROA covers it. Add a ROA for AS200599, maxLength 20. |
| ROA: none | 81.27.232.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 81.27.233.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 81.27.234.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 81.27.235.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 81.27.236.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 81.27.237.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 81.27.238.0/24 | No ROA covers it. Add a ROA for AS200599, maxLength 24. |
| ROA: none | 2a0b:740::/29 | No ROA covers it. Add a ROA for AS200599, maxLength 29. |
Route objects not announced
Route objects with origin AS200599 whose prefix no peer sees AS200599 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.205.156.0/22 | 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.