Past Incidents

Affected Components: SysEleven Stack API, all regions

Incident Start: 2023-10-06 12:09

Incident End: 2023-10-06 12:25

Description:

• Accessibility of the SysEleven Stack API is not ensured.

Customer Impact:

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

Update: 12:25

The API is generally working again (with a concurring incident of smaller scope still persisting, see separate entry).

Affected Components: SysEleven Stack Networking in region DBL

Scheduled Start: 2 Oct 2023, 22:00 CEST

Scheduled End: 3 Oct 2023, 00:00 CEST

State: COMPLETED

Description:

We will perform maintenance on networking gateways.

Customer Impact during the Maintenance:

• Interruption of connectivity of virtual machines of up to 2 minutes
• VPN connections could be interrupted for up to 2 minutes

Customer Actions:

• no customer actions needed
• please inform us if you notice any irregularities

Affected Components: SysEleven Stack API, region DBL

Incident Start: 27th Sept. 2023/03:23 pm

Incident End: 27th Sept. 2023/03:58 pm

Description:

• Accessibility of the SysEleven Stack API is not ensured.

Customer Impact:

• Managing (creating/deleting/attaching/detaching) block storage (cinder) volumes may fail or is not possible at all. Volumes in continuous use are not affected.
• Creating new instances may also fail.

Update: 03:58 pm: Services have been restarted, we are checking functionality.

Update: 04:03 pm: Affected services are restored, we are cleaning up some side-effects that occured during the incident. All newly triggered actions should succeed again.

Update: 04:16 pm: All services are verified to be fully operational again.

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.