Past Incidents

Affected Components: SysEleven Stack, region CBK

Incident Start: 14th Sept. 2023/14:48

Incident End: 14th Sept. 2023/15:05

Description:

• Occurring errors are currently being investigated.

Customer Impact:

• Connectivity is restricted

Update:15:08

A SDN component on one of the network gateways of the CBK region crashed and did not restart correctly. This caused further network issues in the whole CBK cluster. Another restart of the SDN component was triggered manually to bring back normal service.

Update:15:09 We consider the incident as resolved. Please contact us if you still experience problems.

Affected Components: SysEleven Stack API, region DBL

Incident Start: 31th Aug. 2023/14:15

Incident End: 31th Aug. 2023/15:00

Description:

• We are seeing problems with the Cinder Volume services as well as Nova API services. The Accessibility of the SysEleven Stack API is not ensured.

Customer Impact:

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

Update:15:00

We brought back the failed services, control over resources is back, we are observing the situation and search for the root cause

Incident Start: 24th Aug. 2023/10:10 am

We saw a problem with the network gateway for our cloud region cbk. We are still monitoring and evaluating what caused the issues.

Update: 24th Aug. 2023/10:21 pm

We consider the incident as resolved. Please contact us if you still experience problems.

Incident Start: 20th Aug. 2023/05:58 pm

We saw a problem with the network gateway for our cloud region cbk. We are still monitoring and evaluating what caused the issues.

Update: 20th Aug. 2023/06:13 pm

We consider the incident as resolved. Please contact us if you still experience problems.

[We have edited the wording for clarity on August 22nd (Service Management)]

Incident Start: 19th Aug. 2023/01:20 pm

We saw a problem with the network gateway for our cloud region cbk. We are still monitoring and evaluating what caused the issues.

Update: 19th Aug. 2023/01:30 pm

We consider the incident as resolved. Please contact us if you still experience problems.

[We have edited the wording for clarity on August 22nd (Service Management)]