SysEleven Status and Incidents

INCIDENT: Database as a Service connectivity issues, region dus2

Fri, 09 May 2025 12:12:14 +0000

Affected Components: DBaaS in dus2

Incident Start: 2025-05-09 12:00 UTC+02:00 (CEST)
Incident End: 2025-05-09 12:10 UTC+02:00 (CEST)

Description:

We are currently seeing connectivity issues with DBaaS in our dus2 region

Customer Impact:

Databases in dus2 are partly unreachable
New Databases in dus2 can not be created

Update: 2025-05-09 12:10 UTC+02:00 (CEST) - The issue has been identified and resolved

INCIDENT: SysEleven STACK Block Storage issues, region cbk

Tue, 20 May 2025 13:17:37 +0000

Affected Components: SysEleven Stack, Block Storage, region cbk

Incident Start: 2025-05-20 12:46 UTC+02:00 (CEST)

Incident End: 2025-05-20 13:30 UTC+02:00 (CEST)

Description:

We are facing issues with the distributed block storage system in region cbk.

Customer Impact:

Reduced performance of block storage

INCIDENT: PVC Failure of a hardware node, region bki

Wed, 28 May 2025 18:13:11 +0000

Affected Components: Hardware node failure, region bki

Incident Start: **2024-05-28 17:15 UTC+01:00 (CET)

Description:

Malfunction of a hardware node

Customer Impact:

During the period of restart, there will be a short interruption in the availability of the systems.
Affected customers were notified via E-Mail.
Please check the affected systems for their full functionality.

INCIDENT: SysEleven STACK API issues, region FES

Sat, 31 May 2025 16:27:46 +0000

Affected Components: SysEleven Stack API, region FES

Incident Start: 2025-05-31 16:00 Incident End: 2025-05-31 16:30

Description:

Accessibility of the SysEleven Stack API is not ensured.

Customer Impact:

Spawning new virtual machines (VMs) or changing existing resources is not possible.

INCIDENT: SysEleven STACK API issues, region HAM1

Sat, 31 May 2025 16:28:18 +0000

Affected Components: SysEleven Stack API, region HAM1

Incident Start: 2025-05-31 16:00 Incident End: 2025-05-31 16:30

Description:

Accessibility of the SysEleven Stack API is not ensured.

Customer Impact:

Spawning new virtual machines (VMs) or changing existing resources is not possible.

INCIDENT: SysEleven STACK API issues, region DUS2

Sat, 31 May 2025 16:29:09 +0000

Affected Components: SysEleven Stack API, region DUS2

Incident Start: 2025-05-31 16:00 Incident End: 2025-05-31 16:30

Description:

Accessibility of the SysEleven Stack API is not ensured.

Customer Impact:

Spawning new virtual machines (VMs) or changing existing resources is not possible.

INCIDENT: SysEleven STACK issues in region CBK

Fri, 04 Jul 2025 04:44:35 +0000

Affected Components: SysEleven Stack, region XXX

Incident Start: 2025-07-04 04:18 Incident End: 2025-07-04 04:45

Second Incident Start: 2025-07-04 05:15 Second Incident End: 2025-07-04 05:42

Description:

Occurring errors are currently being investigated.

Customer Impact:

Connectivity is restricted'

INCIDENT: PVC Failure of a hardware node, region BKI

Mon, 21 Jul 2025 20:02:45 +0000

Affected Components: Hardware node failure, region BKI1

Incident Start: 2025-07-21 19:30 UTC+02:00 (CET) Incident End: 2025-07-21 20:15 UTC+02:00 (CET)

Description:

Malfunction of a hardware node
Restart of the hardware node is necessary

Customer Impact:

During the period of restart, there will be a short interruption in the availability of the systems.
Affected customers were notified via E-Mail.
Please check the affected systems for their full functionality.

INCIDENT: PVC Failure of a hardware node, region BLU1

Wed, 23 Jul 2025 00:12:12 +0000

Affected Components: Hardware node failure, region BLU1

Incident Start: 2025-07-22 23:46 UTC+02:00 (CEST)

Incident End: 2025-07-23 01:26 UTC+02:00 (CEST)

We found a memory failure and we are going to evacuate the hardware node.

INCIDENT: SysEleven DBaaS issues in region DUS/HAM

Wed, 23 Jul 2025 14:49:29 +0000

Affected Components: SysEleven DBaaS, region DUS, HAM

Incident Start: 2025-23-07 14:23 UTC+02:00 (CEST)

Incident End: 2025-23-07 18:23 UTC+02:00 (CEST)

Description:

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.

Update:

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.

Update:

While all DBaaS instances continue to function as usual, we are still working on the ability of spawning new instances again.

Update:

We are pleased to announce that the creation of DBaaS instances is working properly again.

INCIDENT: SysEleven STACK issues in region CBK

Fri, 15 Aug 2025 14:06:25 +0000

Affected Components: SysEleven Stack, region CBK

Incident Start: 2025-08-15 13:45 Incident Start: 2025-08-15 14:12

Description:

Occurring errors are currently being investigated.

Customer Impact:

Connectivity is restricted

Update: 16:39

The network problems were caused by a DDoS attack which brought the network gateways in the CBK region into performance problems

INCIDENT: partial outage of MetaKube control planes in region CBK/DBL

Tue, 14 Oct 2025 04:04:54 +0000

Affected Components: MetaKube control planes, region CBK/DBL

Incident Start: 2025-10-14 02:40 UTC+02:00 (CEST)

Description:

Some clusters in the regions CBK/DBL have partial outages. The problem is identified and a solution is being worked on.

Update 2025-10-14 04:52 UTC+02:00 (CEST)

Performance is back to normal, watching status.

INCIDENT: SysEleven STACK issues in region FES

Wed, 15 Oct 2025 17:46:39 +0000

Affected Components: SysEleven Stack, region FES

Incident Start: 2025-10-15 17:35 Incident End: 2025-10-15 18:18

Description:

Occurring errors are currently being investigated.

Customer Impact:

New VMs with m2 flavors seem to have problems spawning correctly

Update: 2025-10-15 18:18

We could pin down the issues towards a recent update. The update was rolled back

INCIDENT: Major outage of DBaaS API and Databases

Mon, 20 Oct 2025 14:34:33 +0000

Affected Components: DBaaS API and DBaaS Databases

Incident Start: 2025-10-20 14:00 UTC+01:00 (CET)

Description:

No network functionality.

Customer Impact:

No access to the DBaaS API and Databases

INCIDENT: Performance Degradation of metakube platform on CBK region

Fri, 24 Oct 2025 09:37:02 +0000

Affected Components: Metakube Platform CBK region

Incident Start: 2025-10-24 07:00 UTC+01:00 (CET)

Issues with PostgreSQL as a Service

Wed, 26 Nov 2025 14:27:02 +0000

Affected Components: DBaaS API and DBaaS Databases

Incident Start: 2025-11-26 14:00 UTC+01:00 (CET)

Description:

We see issues that connecting to the PostgreSQL Databases may not work properly

Customer Impact:

Issues with Database Access

INCIDENT: SysEleven STACK DNSaaS API issues

Thu, 27 Nov 2025 11:56:14 +0000

Affected Components: SysEleven Stack DNSaaS API

Incident Start: 2025-11-27 11:06 UTC+01:00 (CET)

Incident End: 2025-11-27 12:07 UTC+01:00 (CET)

Description:

SysEleven OpenStack Cloud DNSaaS (Designate) API issues

Customer Impact:

Creating or updating DNS zones or records via the OpenStack DNSaaS (Designate) API fails
No impact on existing records

Update 12:07

DNSaaS API functionality is restored

INCIDENT: helpdesk portal

Fri, 05 Dec 2025 10:03:29 +0000

Incident Start: 2025-12-05 09:50 UTC+01:00 (CET)

Incident End: 2025-12-05 10:45 UTC+01:00 (CET)

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.

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.

Update 10:45: This incident has been resolved.

INCIDENT: IAM / Dashboard

Wed, 10 Dec 2025 09:09:08 +0000

Affected Components: IAM / Dashboard

Incident Start: 2025-12-10 07:30 UTC+01:00 (CET)

Incident End: 2025-12-10 09:30 UTC+01:00 (CET)

Update 9:05 Incident should be resolved, we are watching. Update 9:30 Incident is resolved.

Incident: E-Mail

Thu, 11 Dec 2025 16:36:28 +0000

Affected Components: E-Mail

Incident Start: 2025-12-11 16:15 UTC+01:00 (CET) Incident Start: 2025-12-11 17:20 UTC+01:00 (CET)

Update: Issue found. Broken config, got fixed.