All systems are operational

About This Site

Timezone: Europe/Berlin (CET)

We provide current information about infrastructure and service availability below. If you experience service impacts or performance issues please contact support@syseleven.de, cloudsupport@syseleven.de or our emergency hotline.

Scheduled Maintenance
SysEleven Stack network maintenance announcement in region DBL

Between January 17th, 2019 07:00 AM and 08:00 AM (UTC +1) we will perform planned maintenance in Region DBL


During the maintenance window we will update the SDN software in our DBL region in order to fix a memory leak.

During the maintenance window the following services will not be accessible:

  • access to the SysEleven Stack Network API (Neutron) will be interrupted in region DBL

The following services will not be affected:

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

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

SysEleven Stack storage maintenance announcement

Between January 23rd, 2018 00:00 AM and 06:00 AM (UTC +1) we will perform planned storage maintenance in Region DBL


During the maintenance window we will update the distributed storage software in our DBL region in order to fix a memory leak.

It is possible that IO requests are slow during the maintenance window.

Affected services:

  • block storage
  • ephemeral storage
  • object storage

Not affected:

  • local SSD storage instances

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

Past Incidents

5th January 2019

No incidents reported

4th January 2019

No incidents reported

3rd January 2019

No incidents reported

2nd January 2019

API SysEleven Stack Neutron API issues in Region DBL

We were facing issues with the SysEleven Stack Neutron API between Dec 29th 2018 and Jan 2nd 2019. Some Neutron API requests were slow, and a few requests might have timed out and failed. The reason was an almost-out-of-memory situation in the software of one of the three SDN controllers. The problem was fixed at 11:26 CET on Jan 2nd 2019.

Network connectivity of VMs were not affected by this issue.

We apologise for any inconveniences.

1st January 2019

No incidents reported

31st December 2018

No incidents reported

30th December 2018

No incidents reported