https://syseleven-status.de 2025-12-12T12:05:56.231310+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 570 2025-12-12T12:05:56.356944+00:00 <p>Affected Components: <strong>DBaaS in dus2</strong></p> <p>Incident Start: <strong>2025-05-09 12:00 UTC+02:00 (CEST)</strong><br /> Incident End: <strong>2025-05-09 12:10 UTC+02:00 (CEST)</strong></p> <hr /> <p>Description:</p> <ul> <li>We are currently seeing connectivity issues with DBaaS in our dus2 region</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Databases in dus2 are partly unreachable</li> <li>New Databases in dus2 can not be created</li> </ul> <hr /> <p>Update: <strong>2025-05-09 12:10 UTC+02:00 (CEST)</strong> - The issue has been identified and resolved</p> 2025-05-09T12:12:14+00:00 571 2025-12-12T12:05:56.355854+00:00 <p>Affected Components: <strong>SysEleven Stack, Block Storage, region cbk</strong></p> <p>Incident Start: <strong>2025-05-20 12:46 UTC+02:00 (CEST)</strong></p> <p>Incident End: <strong>2025-05-20 13:30 UTC+02:00 (CEST)</strong></p> <hr /> <p>Description:</p> <p>We are facing issues with the distributed block storage system in region cbk.</p> <hr /> <p>Customer Impact:</p> <ul> <li>Reduced performance of block storage</li> </ul> 2025-05-20T13:17:37+00:00 572 2025-12-12T12:05:56.354931+00:00 <p>Affected Components: <strong>Hardware node failure, region bki</strong></p> <p>Incident Start: **2024-05-28 17:15 UTC+01:00 (CET)</p> <hr /> <p>Description:</p> <ul> <li>Malfunction of a hardware node</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>During the period of restart, there will be a short interruption in the availability of the systems.</li> <li>Affected customers were notified via E-Mail.</li> <li>Please check the affected systems for their full functionality.</li> </ul> 2025-05-28T18:13:11+00:00 573 2025-12-12T12:05:56.353207+00:00 <p>Affected Components: <strong>SysEleven Stack API, region FES</strong></p> <p>Incident Start: <strong>2025-05-31 16:00</strong> Incident End: <strong>2025-05-31 16:30</strong></p> <hr /> <p>Description:</p> <ul> <li>Accessibility of the SysEleven Stack API is not ensured.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Spawning new virtual machines (VMs) or changing existing resources is not possible.</li> </ul> 2025-05-31T16:27:46+00:00 574 2025-12-12T12:05:56.350658+00:00 <p>Affected Components: <strong>SysEleven Stack API, region HAM1</strong></p> <p>Incident Start: <strong>2025-05-31 16:00</strong> Incident End: <strong>2025-05-31 16:30</strong></p> <hr /> <p>Description:</p> <ul> <li>Accessibility of the SysEleven Stack API is not ensured.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Spawning new virtual machines (VMs) or changing existing resources is not possible.</li> </ul> 2025-05-31T16:28:18+00:00 575 2025-12-12T12:05:56.348638+00:00 <p>Affected Components: <strong>SysEleven Stack API, region DUS2</strong></p> <p>Incident Start: <strong>2025-05-31 16:00</strong> Incident End: <strong>2025-05-31 16:30</strong></p> <hr /> <p>Description:</p> <ul> <li>Accessibility of the SysEleven Stack API is not ensured.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>Spawning new virtual machines (VMs) or changing existing resources is not possible.</li> </ul> 2025-05-31T16:29:09+00:00 576 2025-12-12T12:05:56.347651+00:00 <p>Affected Components: <strong>SysEleven Stack, region XXX</strong></p> <p>Incident Start: <strong>2025-07-04 04:18</strong> Incident End: <strong>2025-07-04 04:45</strong></p> <p>Second Incident Start: <strong>2025-07-04 05:15</strong> Second Incident End: <strong>2025-07-04 05:42</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> 2025-07-04T04:44:35+00:00 577 2025-12-12T12:05:56.346641+00:00 <p>Affected Components: Hardware node failure, region BKI1</p> <p>Incident Start: 2025-07-21 19:30 UTC+02:00 (CET) Incident End: 2025-07-21 20:15 UTC+02:00 (CET)</p> <hr /> <p>Description:</p> <ul> <li>Malfunction of a hardware node</li> <li>Restart of the hardware node is necessary </li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>During the period of restart, there will be a short interruption in the availability of the systems.</li> <li>Affected customers were notified via E-Mail.</li> <li>Please check the affected systems for their full functionality.</li> </ul> 2025-07-21T20:02:45+00:00 578 2025-12-12T12:05:56.346049+00:00 <p>Affected Components: <strong>Hardware node failure, region BLU1</strong></p> <p>Incident Start: 2025-07-22 23:46 UTC+02:00 (CEST)</p> <p>Incident End: 2025-07-23 01:26 UTC+02:00 (CEST)</p> <p>We found a memory failure and we are going to evacuate the hardware node.</p> 2025-07-23T00:12:12+00:00 579 2025-12-12T12:05:56.344611+00:00 <p>Affected Components: <strong>SysEleven DBaaS, region DUS, HAM</strong></p> <p>Incident Start: <strong>2025-23-07 14:23 UTC+02:00 (CEST)</strong></p> <p>Incident End: <strong>2025-23-07 18:23 UTC+02:00 (CEST)</strong></p> <hr /> <p>Description:</p> <p>We are currently investigating the situation that no new DBaaS instances can be created in the DUS and HAM regions at present. The operation of existing instances is not affected. We will report on further developments here.</p> <hr /> <p>Update:</p> <p>The creation of DBaaS instances in the HAM region is functional again. We are still working on a solution for the DUS region and will keep you informed.</p> <hr /> <p>Update:</p> <p>While all DBaaS instances continue to function as usual, we are still working on the ability of spawning new instances again.</p> <hr /> <p>Update:</p> <p>We are pleased to announce that the creation of DBaaS instances is working properly again.</p> <hr /> 2025-07-23T14:49:29+00:00 580 2025-12-12T12:05:56.343306+00:00 <p>Affected Components: <strong>SysEleven Stack, region CBK</strong></p> <p>Incident Start: <strong>2025-08-15 13:45</strong> Incident Start: <strong>2025-08-15 14:12</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> <hr /> <p><strong>Update: 16:39</strong></p> <p>The network problems were caused by a DDoS attack which brought the network gateways in the CBK region into performance problems</p> 2025-08-15T14:06:25+00:00 581 2025-12-12T12:05:56.342020+00:00 <p>Affected Components: <strong>MetaKube control planes, region CBK/DBL</strong></p> <p>Incident Start: <strong>2025-10-14 02:40 UTC+02:00 (CEST)</strong></p> <hr /> <p>Description:</p> <p>Some clusters in the regions CBK/DBL have partial outages. The problem is identified and a solution is being worked on.</p> <hr /> <p>Update <strong>2025-10-14 04:52 UTC+02:00 (CEST)</strong></p> <p>Performance is back to normal, watching status.</p> 2025-10-14T04:04:54+00:00 582 2025-12-12T12:05:56.340230+00:00 <p>Affected Components: <strong>SysEleven Stack, region FES</strong></p> <p>Incident Start: <strong>2025-10-15 17:35</strong> Incident End: <strong>2025-10-15 18:18</strong></p> <hr /> <p>Description:</p> <ul> <li>Occurring errors are currently being investigated.</li> </ul> <hr /> <p>Customer Impact:</p> <ul> <li>New VMs with m2 flavors seem to have problems spawning correctly</li> </ul> <hr /> <p>Update: <strong>2025-10-15 18:18</strong></p> <p>We could pin down the issues towards a recent update. The update was rolled back</p> 2025-10-15T17:46:39+00:00 583 2025-12-12T12:05:56.339584+00:00 <p>Affected Components: DBaaS API and DBaaS Databases</p> <p>Incident Start: <strong>2025-10-20 14:00 UTC+01:00 (CET)</strong></p> <hr /> <p>Description:</p> <p>No network functionality.</p> <hr /> <p>Customer Impact:</p> <p>No access to the DBaaS API and Databases</p> 2025-10-20T14:34:33+00:00 584 2025-12-12T12:05:56.339141+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 2025-12-12T12:05:56.337683+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 2025-12-12T12:05:56.336300+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 2025-12-12T12:05:56.334103+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 2025-12-12T12:05:56.332166+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 2025-12-12T12:05:56.330582+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