Past Incidents

For a number of customer clusters, the Kubernetes controller-manager and the scheduler were not functioning. Running workloads were not affected, but no scheduling decisions could be made.

Incident over: 22:30

At the moment we are facing network issues in region FES that also affect our control plane services.

We will keep you informed and apologize for any inconveniences.

Update 12:20 : We have identified and resolved an issue and are now verifying the solution. Update 13:05 : After a short watch time we have verified that the solution did fix the issue.

Reason for Outage (RfO) (de)

Between July 27rd, 2022 22:00 and 00:00 (CEST) we will perform planned maintenance in Region FES

During the maintenance we expect the following impact:

• series of interruptions of network connectivity of virtual machines for up to 5 minutes in total

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

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

We will keep you informed and apologise for any inconveniences.

update Since 15:20 the issues have been resolved

We are experiencing some issues on login via login.syseleven.de

Update: The issue was identified and fixed, login is working again

Between July 14th, 2022 10:00 PM and 01:00 AM (UTC +2) we will perform planned maintenance in Region FES

During the maintenance we expect the following impact:

• All OpenStack APIs in FES will be unavailable for up to 30 minutes
• VPN connections will be interrupted for up to 2 minutes

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

Our Monitoring identified a hardware node failure.

Affected customers were notified via E-Mail. If interaction is required customers will be notified individually.

Please contact us via e-mail or phone if you encountered problems but did not receive any mail.

Update: All guest systems, including the services running on them, are available and running again. Nevertheless, we kindly ask you to check the affected systems for their full functionality.

At the moment, some clients are experiencing timeout issues against their cluster's apiserver endpoint.

We haven't yet been able to reproduce the issue, but have found a possible hotfix that alleviates the issues and are testing it.

We will keep you informed and apologise for any inconveniences.

Update 13:37: We've deployed a fix and are watching the situation.