Past Incidents

Between August 16th, 2022 22:00 and 24:00 (UTC +2) we will perform planned maintenance in Region DBL

During this period there will be:

• network availability of virtual machines will be interrupted for up to 5 min
• access to the API/Dashboard will not be affected
• SEOS (S3) will not be affected
• storage availability will not be affected

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

Fixed: Our external DNS resolution has been restored

Previous Message: Our DNS resolution is currently experiencing a major outage. We are investigating the issue. Due to this circumstance, further service outages may occur. Should you experience any outages or are in need of further assistance, please open a ticket or contact us via our emergency hotline. Our gitlab instance code.syseleven.de is also affected by the outage.

This incident has been resolved.

Past message: Our DNS provider is currently experiencing a major outage. We are investigating the issue. Due to this circumstance, further service outages may occur. Should you experience any outages or are in need of further assistance, please open a ticket or contact us via our emergency hotline.

Our Monitoring identified multiple hardware node failures.

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 16:30: All hardware nodes are running again. We are currently working on resolving all remaining alerts. Update 16:50: All websites are reachable and working again. We are still working on some remaining minor problems and follow up tasks.

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)