Past Incidents

Between March 7th, 2019 0:00 AM and 01:00 AM (UTC +1) we will perform planned maintenance in Region CBK

During this period the Cinder (Volume) API in the CBK region is not available - leading to a loss of control.

During this period there will be:

• no access to Cinder API, causing loss of control over block volumes. Creation, deletion, modification, attachment, and detachment of volumes will not work.
• running virtual machines will not be affected, attached volumes will not be affected.
• data on the volumes will not be corrupted.
• SEOS (S3) will not be affected.
• network availability will not be affected.

After the maintenance is over, the storage availability zone name will be changed from "nova" to "cbk1". No Heat stack or Terraform state changes are required, if the availability zone was not explicitly specified.

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

Between February 27th 2019 00:00 AM and 05:00 AM (UTC +1) we will perform planned maintenance in Region CBK

During this period the API in the CBK region is not available - leading to a loss of control.

During this period there will be:

• no access to the API/Dashboard (loss of control)
• running virtual machines will not be affected
• SEOS (S3) will not be affected
• network availability will not be affected
• storage availability will not be affected

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

SysEleven Network Maintenance Announcement - Location: fix5 - Reason: Software Update

• Between February 20th, 2019 00:00 AM and 06:00 AM (local time) we will perform planned maintenance in our fix5 Location
• Reason: Software Updates

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

SysEleven Network Maintenance Announcement - Location: blu1 - Reason: Software Update

• Between February 19th, 2019 00:00 AM and 06:00 AM (local time) we will perform planned maintenance in our blu1 Location
• Reason: Software Updates

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

We observed an elevated rate of errors, creating local storage virtual machines (L1.* flavor).

Engineers are now looking into the problem and we will keep you informed here.

UPDATE 15:45: Creating L1.* virtual machines currently requires unusual amounts of disk space on the hypervisors. The elevated error rate was because not enough space was left, for short amounts of time. Our engineers have resolved this issue for now, and are still working on a permanent solution.

Please contact us at cloudsupport@syseleven.de if you are still encountering any issues.

SysEleven Network Maintenance Announcement - Location: bki1 - Reason: Software Update

• Between February 14th, 2019 00:00 AM and 06:00 AM (local time) we will perform planned maintenance in our bki1 Location
• Reason: Software Updates

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

In order to offer the same features in both regions we will roll out new versions of our networking components in the CBK region.

The maintenance window is planned for 2019-02-13 from 00:00-05:00 (CET)

During the maintenance window we will update the networking components in the CBK region.

There will be the following service degradations within the maintenance window:

• API endpoints of the CBK region are not available.
• Virtual machines of the CBK region will face several downtimes. They will be unavailable for approximately one minute in total.

The DBL region will not be affected.

UPDATE 01:55: The maintenance has been completed.

Currently it will take a long time to create servers with the Local SSD Storage (L1.*) flavors. The wait time increases linearly to Local SSD Storage capacity of the chosen flavor. Eventually, creating the server will succeed.

This is due to a mitigation we put in place that solves sporadic performance problems, when a virtual machine has been created or deleted. We are right now working on a better mitigation, that will not affect creating servers.

The issue only affects spawning new virtual machines with the L1.* flavor (Local SSD Storage).

We apologise for any inconveniences.

UPDATE 2019-02-13: The issues are fully resolved now. Creating and deleting Local SSD Storage instances will only take a few seconds now, and the time for creating and deleting VMs is constant, no matter what disk capacity.