Past Incidents

Between March 4, 2021 22:00 and 00:00 (UTC +1) we will perform planned maintenance in Region DBL

During this period there will be:

• interruptions of network connectivity of virtual machines for up to 5 minutes
• 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.

Between 03 March 2021, 22:00 and 04 March 2021, 07:00 (UTC +1) we will perform planned maintenance in Region CBK

During the maintenance we expect the following impact:

• interruptions of network connectivity of virtual machines for up to 5 minutes (before midnight)
• possible degradation in storage performance (S3 and VMs)

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

We are investigating an intermittent internet connectivity issue in CBK that affected some amount of network connections.

We will keep you informed and apologise for any inconveniences.

UPDATE 10:19: This affected resolving for a part of the SysEleven Stack Designate DNS resolvers.

UPDATE 10:23: This is a correction. We assumed an intermittent internet connectivity issue. In fact we still see ongoing issues for a fraction of internet connections. We are working on resolving these.

UPDATE 10:44: The issues are now resolved. There should be no ongoing issues anymore. Please contact cloudsupport@syseleven.de immediately, if you are experiencing ongoing issues. We are still watching the infrastructure closely.

UPDATE 11:05: The issues are now resolved. We are working on measures to prevent this kind of problem in the future.

Between February 24th, 2021 22:00 and midnight (UTC +1) we will perform planned maintenance in Region DBL

Our plan is to update networking components.

During this period there will be:

• API/Dashboard will not be affected
• running virtual machines may be affected by network interruptions
• SEOS (S3) will not be affected
• network availability will be affected: there may be network interruptions of up to 5 min
• storage availability will not be affected

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

english Version below:

------ deutsche Version -----

Derzeit besteht eine Störung in der Netzwerkinfrastruktur der Cloud Umgebungen in CBK und DBL.

Die Störung hat zur Auswirkung, dass es bei der Netzwerkkommunikation über das TCP-Protokoll zu Geschwindigkeitsverlust führen kann.

Unsere Engineers untersuchen die Ursache mit Hochdruck und werden umgehend Gegenmaßnahmen ergreifen. Einen aktuellen Status finden Sie auf unserer Status Page, die Sie unter https://www.syseleven-status.net/ erreichen können.

Sobald das Problem behoben ist und die Systeme wieder stabil laufen, werden wir auch noch einmal per Mail informieren.

Sollten Sie Fragen haben oder Unterstützung benötigen stehen wir ihnen per support@syseleven.de bzw. per Telefon zur Verfügung.

------ english version -----

There is currently an incident in the cloud environments' network infrastructure in CBK and DBL.

The disruption is that network communication via the TCP protocol can lead to a loss of speed.

Our engineers are investigating the cause at full speed and will take countermeasures immediately. You find more informations and an up-to-date status on https://www.syseleven-status.net/.

As soon as the problem is solved and the systems are stable again, we will inform you by mail.

If you have any questions or need support, please contact us via support@syseleven.de or phone.

Update 12:40 CET

Our Cloud Development Team and our Network Team are still investigating the network issue.

Update 15:40 CET

To improve the network’s stability, we have to schedule today's emergency maintenance at 16:00 CET. The maintenance may impact the network’s availability for a short period of time and your systems may not be available by the network.

Update 18:00 CET

We've rolled out a very promising change in the more affected region CBK. We're observing it over the week-end before we will follow-up in region DBL.

Update Tue 09:30 CET

We've rolled out the change in DBL and consider the incident solved now. Please contact us if you still observe problems.

At the moment we are facing issues with the network in both regions of the SysEleven Stack. There might be the chance for lost packets on outgoing TCP connections to external destinations.

We will keep you informed and apologize for any inconveniences.

Update Fri 02:00: The emergency maintenance was carried out but did not improve the situation as expected. We are continuing our investigations.

Update Fri 18:00: We've rolled out a very promising change in the more affected region CBK. We're observing it over the week-end before we will follow-up in region DBL.

Update Tue 09:30: We've rolled out the change in DBL and consider the incident solved now. Please contact us if you still observe problems.

SysEleven Container Registry is currently unavailable. We are investigating the issue and will update you as soon as possible. We apologize for the inconvenience.

At the moment we are facing issues with DNSaaS in region DBL and CBK.

Currently only one nameserver can be used.

UPDATE 12:15: The issue is now resolved. If you are still experiencing issues, please contact us at cloudsupport@syseleven.de

We will keep you informed and apologise for any inconveniences.

Between 1:10 and 1:13 p.m. we were facing issues with the Object Storage in Region CBK.

The problem is resolved now.

We apologise for any inconveniences.

At the moment we are facing issues with Metakube Syseleven login.

New sessions cannot be created at the time.

We are investigating the issue ro provide a solution to the issue as soon as possible.

We will keep you informed and apologise for any inconveniences.

We are experiencing DNS errors in Mekatube clusters that may lead to malfunctions. We are investigating the issue and come back with updates.

Update 14:20: Problem has been identified and fix is being prepared.

Update 15:09: Fix has been rolled out on most clusters. The rest is in progress.

Update 15:39: Fix has been rolled out on all affected clusters. Incident has been solved.