https://syseleven-status.de 2026-05-12T11:10:12.829537+00:00 SysEleven support@syseleven.de python-feedgen https://www.syseleven.de/wp-content/uploads/2020/10/SysEleven_XL_Logo_quer_RGB.png Get all incidents by feed 584 2026-05-12T11:10:12.927349+00:00 <p>Affected Components: <strong>Metakube Platform CBK region</strong></p> <p>Incident Start: 2025-10-24 07:00 UTC+01:00 (CET)</p> 2025-10-24T09:37:02+00:00 585 2026-05-12T11:10:12.926568+00:00 <p>Affected Components: DBaaS API and DBaaS Databases</p> <p>Incident Start: <strong>2025-11-26 14:00 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <p>We see issues that connecting to the PostgreSQL Databases may not work properly</p> <hr /> <p>Customer Impact:</p> <p>Issues with Database Access</p> 2025-11-26T14:27:02+00:00 586 2026-05-12T11:10:12.925467+00:00 <p>Affected Components: <strong>SysEleven Stack DNSaaS API</strong></p> <p>Incident Start: <strong>2025-11-27 11:06 UTC+01:00 (CET)</strong></p> <p>Incident End: <strong>2025-11-27 12:07 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>SysEleven OpenStack Cloud DNSaaS (Designate) API issues</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Creating or updating DNS zones or records via the OpenStack DNSaaS (Designate) API fails</li> <li>No impact on existing records</li> </ul> <hr /> <p><strong>Update 12:07</strong></p> <p>DNSaaS API functionality is restored</p> 2025-11-27T11:56:14+00:00 587 2026-05-12T11:10:12.924754+00:00 <p>Incident Start: <strong>2025-12-05 09:50 UTC+01:00 (CET)</strong></p> <p>Incident End: <strong>2025-12-05 10:45 UTC+01:00 (CET)</strong></p> <p>We are currently experiencing an outage of our customer portal. We are already in contact with the manufacturer and are working on restoring it. In urgent cases, please use our hotlines.</p> <p>UPDATE 10.27: While our helpdesk portal is already fully operational again we continue observing the situation. In case of difficulties reaching our portal please do not hesitate in calling us.</p> <p>Update 10:45: This incident has been resolved.</p> 2025-12-05T10:03:29+00:00 588 2026-05-12T11:10:12.924105+00:00 <p>Affected Components: IAM / Dashboard</p> <p>Incident Start: <strong>2025-12-10 07:30 UTC+01:00 (CET)</strong></p> <p>Incident End: <strong>2025-12-10 09:30 UTC+01:00 (CET)</strong></p> <p>Update <strong>9:05</strong> Incident should be resolved, we are watching. Update <strong>9:30</strong> Incident is resolved.</p> 2025-12-10T09:09:08+00:00 589 2026-05-12T11:10:12.923405+00:00 <p>Affected Components: E-Mail</p> <p>Incident Start: <strong>2025-12-11 16:15 UTC+01:00 (CET)</strong> Incident Start: <strong>2025-12-11 17:20 UTC+01:00 (CET)</strong></p> <p>Update: Issue found. Broken config, got fixed.</p> 2025-12-11T16:36:28+00:00 590 2026-05-12T11:10:12.921975+00:00 <p>Affected Components: <strong>network in all regions</strong></p> <p>Incident Start: <strong>2026-01-08 16:50 UTC+01:00 (CET) </strong> Incident End: <strong>2026-01-08 17:50 UTC+01:00 (CET) </strong></p> <hr /> <p>Description:</p> <p>We are facing Network / DNS issues in CBK, DBL, FES, DUS and HAM. We are investigating.</p> <hr /> <p>Update: 17:26</p> <p>Services are running, network connectivity from outside have issues. Still investigating the network issues. Next update latest 18:00</p> <hr /> <p>Update: 17:48</p> <p>All systems are back to normal, still investigating</p> <hr /> <p>Update: 17:50</p> <p>incident is over</p> <hr /> <p><strong><a href="https://helpdesk.syseleven.de/hc/de/articles/32605555664274-2026-01-16-RFO-DNS-Outage-all-regions">Reason for Outage (RfO)</a> (de)</strong></p> 2026-01-08T16:59:54+00:00 591 2026-05-12T11:10:12.921034+00:00 <p>Affected Components: <strong>SysEleven Stack, region DUS2</strong></p> <p>Incident Start: <strong>2026-01-19 16:48 UTC+01:00 (CET)</strong></p> <p>Incident Stop: <strong>2026-01-19 17:43 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>Occurring errors are currently being investigated.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Connectivity is restricted</li> </ul> 2026-01-19T17:23:36+00:00 592 2026-05-12T11:10:12.920281+00:00 <p>Affected Components: <strong>SysEleven Stack, region DBL</strong></p> <p>Incident Start: <strong>2026-01-29 10:26 UTC+01:00 (CET)</strong> Incident End: <strong>2026-01-29 10:28 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>Occurring errors are currently being investigated.</li> </ul> 2026-01-29T10:51:33+00:00 593 2026-05-12T11:10:12.919572+00:00 <p>Affected Components: <strong>SysEleven Stack, region CBK</strong></p> <p>Incident Start: <strong>2026-01-29 10:26 UTC+01:00 (CET)</strong> Incident End: <strong>2026-01-29 10:28 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>Occurring errors are currently being investigated.</li> </ul> 2026-01-29T10:52:13+00:00 594 2026-05-12T11:10:12.918553+00:00 <p>Affected Components: <strong>SysEleven Stack, region FES</strong></p> <p>Incident Start: <strong>2026-01-29 10:26 UTC+01:00 (CET)</strong> Incident End: <strong>2026-01-29 10:28 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>Occurring errors are currently being investigated.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Connectivity is restricted</li> </ul> 2026-01-29T10:55:49+00:00 595 2026-05-12T11:10:12.918005+00:00 <p>Affected Components: Uplink ISP mitigating DDOS, side effects for reachability of any resources hosted by SysEleven.</p> <p>Incident Start: **2025-02-04 21:15 UTC+01:00 (CET)</p> <p>22:30 ISP deployed countermeasures. Problems aren't noticeable anymore. Incident End: **2025-02-04 22:35 UTC+01:00 (CE</p> 2026-02-14T22:12:49+00:00 596 2026-05-12T11:10:12.916563+00:00 <p>Affected Components: <strong>SysEleven Stack, region DUS2</strong></p> <p>Incident Start: <strong>2026-03-04 09:00 UTC+01:00 (CET)</strong> Incident End: <strong>2026-03-05 10:45 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>Occurring errors are currently being investigated.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Performance degradation of certain hardware nodes causing VMs to be slower</li> </ul> <hr /> <p>Update : <strong>2026-03-04 17:50 UTC+01:00 (CET)</strong></p> <p>Mitigation is taking effect, VMs are sequentially getting migrated towards new targets without the performance issues. This will take a bit longer to not make the current impact more severe</p> 2026-03-04T15:39:53+00:00 597 2026-05-12T11:10:12.915587+00:00 <p>Affected Components: <strong>SysEleven Stack, region HAM1</strong></p> <p>Incident Start: <strong>2026-03-05 12:00 UTC+01:00 (CET)</strong> Incident End: <strong>2026-03-05 19:30 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>Occurring errors are currently being investigated.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Some compute nodes showed performance issues. They are being drained sequentially to avoid impact on workloads. Feel free to reach out to us in case of questions!</li> </ul> 2026-03-05T12:12:23+00:00 598 2026-05-12T11:10:12.914676+00:00 <p>Affected Components: <strong>SysEleven Stack, region FES</strong></p> <p>Incident Start: <strong>2026-03-26 15:14 UTC+01:00 (CET) </strong> Incident End: <strong>2026-03-26 15:16 UTC+01:00 (CET) </strong></p> <hr /> <p>Description:</p> <ul> <li>A change in configuration caused an unexpected network outage for the region for ~2 minutes</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Connectivity is restricted</li> </ul> 2026-03-26T15:26:11+00:00 599 2026-05-12T11:10:12.913650+00:00 <p>Affected Components: <strong>SysEleven Stack API</strong></p> <p>Incident Start: <strong>2026-04-28 12:55</strong> Incident End: <strong>2026-04-28 13:15</strong></p> <hr /> <p>Description:</p> <ul> <li>Loss of control for DNSaaS API</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Creating new zones or adjusting DNS entries might currently not be possible</li> </ul> 2026-04-28T13:00:20+00:00 600 2026-05-12T11:10:12.912613+00:00 <p>Affected Components: <strong>MetaKube, region DBL/CBK</strong></p> <p>Incident Start: <strong>2026-05-05 15:00 UTC+02:00 (CEST)</strong></p> <hr /> <p>Description:</p> <p>Partial outage of etcd storage for a limited amount of clusters.</p> <hr /> <p>Customer Impact:</p> <ul> <li>Affected clusters do not have a working control plane</li> <li>Nodes and running workloads are not directly affected</li> </ul> <hr /> <p>Customer Actions:</p> <ul> <li>No customer actions needed</li> </ul> <hr /> 2026-05-05T15:10:26+00:00 601 2026-05-12T11:10:12.911308+00:00 <p>Affected Components: <strong>SysEleven Stack, region DBL</strong></p> <p>Incident Start: <strong>2026-05-05 15:00 UTC+02:00 (CEST)</strong></p> <p>Incident End: <strong>2026-05-05 16:05 UTC+02:00 (CEST)</strong></p> <hr /> <p>Description:</p> <ul> <li>Network connectivity issues in region DBL</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Connectivity is restricted</li> </ul> <hr /> <p>Update : <strong>2026-05-05 15:40 UTC+02:00 (CET)</strong></p> <p>Network connectivity is restored. We are monitoring the situation.</p> 2026-05-05T15:19:32+00:00 602 2026-05-12T11:10:12.909642+00:00 <p>Affected Components: <strong>SysEleven Stack, all regions</strong></p> <p>Incident Start: <strong>2026-05-05 21:39 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <p>We are currently experiencing partial issues with our DNS resolvers.</p> <p>The whole .de-zone is currently experiencing outages as reported by DENIC.</p> <p>We are investigating a workaround.</p> <hr /> <p>Customer Impact: This affects all services on our side and from customers.</p> <hr /> <p><strong>Update: 23:45 / 11:45 pm</strong></p> <p>We are monitoring the situation. We decided not to disable DNSSEC as a workaround to sustain integrity of DNS resolution, though this could ease the situation.</p> <hr /> <p><strong>Update: 00:31 / 12:31 am</strong></p> <p>DENIC is still working on the incident. The situation is improving. We are monitoring.</p> <hr /> <p><strong>Update: 07:31 / 07:31 am</strong></p> <p>DENIC status page says "All Systems Operational". Incident is resolved.</p> <hr /> 2026-05-05T23:04:56+00:00 603 2026-05-12T11:10:12.907542+00:00 <p>Affected Components: <strong>SysEleven Stack API, all regions</strong></p> <p>Incident Start: <strong>2026-05-05 21:39 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <ul> <li>cloud.syseleven.de and dashboard.syseleven.de are not reachable</li> <li>Cloud APIs are working as expected</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Spawning new virtual machines (VMs) or changing existing resources is not possible.</li> </ul> <hr /> <p><strong>Update: 23:45 / 11:45 pm</strong></p> <p>This is related to the DNS outage reported by DENIC from the 05.05 at 21:39 / 9:39 pm.</p> <hr /> 2026-05-05T23:31:40+00:00