All systems are operational

About This Site

Timezone: Europe/Berlin (CET - UTC +1/CEST - UTC +2)

We provide current information about infrastructure and service availability below. If you experience service impacts or performance issues please contact our helpdesk or our Service Desk.

Past Incidents

Wednesday 4th July 2018

API SysEleven Stack API issues in Region DBL

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 apologize for any inconveniences.

Update 14:44
The API is available again. The reason for the short unavailability was due to a software bug.

Tuesday 3rd July 2018

Datacenter Berlin 2 (BKI1) SysEleven Stack Object Storage issues in region CBK

At the moment we are facing issues with the Object Storage in Region CBK. At the moment it is possible that objects can't be read or written.

We will keep you informed and apologise for any inconveniences.

UPDATE 19:54: We fixed the issues. Every service is up and running again.

Compute SysEleven Stack Compute issues in Region CBK

Currently we are facing issues with the SysEleven Stack Compute service in Region CBK.

Thus it is not possible to create new instances at the moment. Also it is not possible to create new Volumes in this region.

Running VMs are not affected.

We apologise for any inconviniences.

UPDATE 16:00:
We fixed the issues and are now investigating the root cause.

Block Storage (Cinder Volumes / M1 Flavors) Cinder API issues in the DBL region

We are currently facing issues with the cinder volume API.

Only creating, updating or attaching cinder volumes in the DBL region is affected.

Running VMs with cinder volumes are NOT affacted.

UPDATE 12:15:
We solved the issues and are watching the systems closely.

UPDATE 13:00:
The issues are solved and we are working on a root cause analysis.

Monday 2nd July 2018

No incidents reported

Sunday 1st July 2018

No incidents reported

Saturday 30th June 2018

No incidents reported

Friday 29th June 2018

No incidents reported

Thursday 28th June 2018

No incidents reported

Wednesday 27th June 2018

No incidents reported

Tuesday 26th June 2018

No incidents reported

Monday 25th June 2018

No incidents reported

Sunday 24th June 2018

No incidents reported

Saturday 23rd June 2018

No incidents reported

Friday 22nd June 2018

No incidents reported

Thursday 21st June 2018

No incidents reported

Wednesday 20th June 2018

No incidents reported

Tuesday 19th June 2018

No incidents reported

Monday 18th June 2018

No incidents reported

Sunday 17th June 2018

No incidents reported

Saturday 16th June 2018

No incidents reported

Friday 15th June 2018

No incidents reported

Thursday 14th June 2018

No incidents reported

Wednesday 13th June 2018

No incidents reported

Tuesday 12th June 2018

No incidents reported

Monday 11th June 2018

No incidents reported

Sunday 10th June 2018

No incidents reported

Saturday 9th June 2018

No incidents reported

Friday 8th June 2018

No incidents reported

Thursday 7th June 2018

No incidents reported

Wednesday 6th June 2018

API SysEleven Stack API issues in region DBL

Currently we are facing issues with the SysEleven Stack API. We are working on a solution.

  • The outage only affects spawning new virtual machines or changing existing ressources.

Update: 16:59
The issue is solved, the API is up and responding properly again.
The problem was also caused by a network fabric failure.

We apologise for any inconveniences.

Block Storage (Cinder Volumes / M1 Flavors) SysEleven Stack Block and Object Storage issues in region DBL

At the moment we are facing issues with the distributed file system, a core component of the SysEleven Stack.

  • Virtul machines might have trouble spawning or have no access to their volumes (disks)
  • SEOS/S3 access might be slow or interrupted

Update: 14:34
We identified the cause and are working on a fix.

Update: 14:46
The issue is solved, everything is up and running properly again.
The problem was caused by a network fabric failure.


We will keep you informed and apologise for any inconveniences.

Tuesday 5th June 2018

No incidents reported