Past Incidents

Between November 05, 2020 23:00 and 00:00 (UTC +1) we will perform planned maintenance in Region CBK

We expect short network interruptions of up to 1 minute.

• network availability will be affected
• state of virtual machines will not be affected
• storage availability will not be affected
• SEOS (S3) will not be affected
• the API will not be affected

Should you have any trouble following the maintenance work please contact us.

Between November 02, 2020 23:00 and 00:00 (UTC +1) we will perform planned maintenance in Region DBL

UPDATE: The appointment for the maintenance has been moved to Nov. 2nd

We expect short network interruptions of up to 1 minute.

• network availability will be affected
• state of virtual machines will not be affected
• storage availability will not be affected
• SEOS (S3) will not be affected
• the API will not be affected

Should you have any trouble following the maintenance work please contact us.

Currently we are facing issues with the SysEleven Stack API. We are working on a solution and keep you informed. The outage only affects spawning new virtual machines or changing existing resources.

We apologise for any inconveniences.

UPDATE 11:57: The issues are now resolved. If you are still experiencing issues, please contact us at cloudsupport@syseleven.de

Cluster creation takes very long, fails occasionally after rolling out updated etcd launcher architecture

There are issues when calling SysEleven via telephone. We are investigating the issue. Please contact us via email or ticket (support@syseleven.de, https://helpdesk.syseleven.de).

Update 09:55: Service has been recovered.

One of our local storage nodes has failed, and won't restart. All VMs on this node are currenly unavailable.

We will keep you informed and apologise for any inconveniences.

Update 12:05: The node could not be recovered, all affected VMs are gone and will be removed from your list.

We were facing issues with the distributed file system, a core component of the SysEleven Stack. During the issues it was possible that virtual machines can't be spawned or have no write access to their volumes(disks).

We will keep you informed and apologize for any inconveniences.

Update: 18:48 The issues were identified and fixed