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

Monday 5th November 2018

No incidents reported

Sunday 4th November 2018

No incidents reported

Saturday 3rd November 2018

No incidents reported

Friday 2nd November 2018

No incidents reported

Thursday 1st November 2018

No incidents reported

Wednesday 31st October 2018

No incidents reported

Tuesday 30th October 2018

No incidents reported

Monday 29th October 2018

No incidents reported

Sunday 28th October 2018

No incidents reported

Saturday 27th October 2018

No incidents reported

Friday 26th October 2018

No incidents reported

Thursday 25th October 2018

Network SysEleven Stack issues in region DBL

At the moment we are facing connectivitiy issues in region DBL.

We will keep you informed and apologise for any inconveniences.

UPDATE 4:14: Any network connectivity issues are solved now. Reason for outage was a faulty line card.

Wednesday 24th October 2018

No incidents reported

Tuesday 23rd October 2018

No incidents reported

Monday 22nd October 2018

No incidents reported

Sunday 21st October 2018

No incidents reported

Saturday 20th October 2018

No incidents reported

Friday 19th October 2018

No incidents reported

Thursday 18th October 2018

No incidents reported

Wednesday 17th October 2018

No incidents reported

Tuesday 16th October 2018

No incidents reported

Monday 15th October 2018

Compute SysEleven Stack block storage issues in regions CBK and DBL

Today we were facing issues with the distributed file system, a core component of the SysEleven Stack.

Affected times for the region CBK

13:12 – 13:17 (MESZ)

14:32 – 14:37 (MESZ)

Affected times for the region DBL

12:05 – 12:15 (MESZ)

12:51 – 13:00 (MESZ)

13:50 – 14:00 (MESZ)

During these times it was possible that virtual machines did not respond due to IO wait. It might also have affected creating virtual machines and cinder volumes.

We will keep you informed and apologise for any inconveniences.

UPDATE 16:20

We identified that regular maintenance work on storage nodes (reboots) have indirectly caused this incident. The maintenance work is stopped until we find and resolve the root cause in close collaboration with the storage software vendor.

We will keep you informed on the results.

Sunday 14th October 2018

No incidents reported

Saturday 13th October 2018

No incidents reported

Friday 12th October 2018

No incidents reported

Thursday 11th October 2018

No incidents reported

Wednesday 10th October 2018

No incidents reported

Tuesday 9th October 2018

No incidents reported

Monday 8th October 2018

No incidents reported

Sunday 7th October 2018

No incidents reported