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.

Maintenance
MAINTENANCE: Core Routers in FES

Affected Components: Core Routers, region FES

Scheduled Start: 13. Jan. 2026/9:00 pm

Scheduled End: 14. Jan. 2026/02:00 am

State: SCHEDULED


Description:

In order to ensure the greatest possible stability and availability of our network, we will be carrying out maintenance work on our routers at the FES location during a maintenance window from 21:00 CET on Tuesday, 13 January 2026 until 02:00 CET on Wednesday, 14 January 2026. During the execution of the work, an increased latency time is to be expected over the period of the maintenance window.


Customer Impact during the Maintenance:

  • FES: reduced latency

Customer Actions:

  • No customer actions needed
  • Please inform us if you notice any irregularities
MAINTENANCE: SysEleven OpenStack Cloud announcement (DUS2)

Affected Components: SysEleven OpenStack Cloud Networking in region DUS2

Scheduled Start: 14 Jan 2026, 22:00 CET

Scheduled End: 14 Jan 2026, 23:00 CET

State: SCHEDULED


Description:

We will perform maintenance on networking gateways.


Customer Impact during the Maintenance:

  • Several short interruptions of external network connectivity up to 10 seconds each
  • VPN connections could be interrupted for up to 10 seconds

Customer Actions:

  • no customer actions needed
  • please inform us if you notice any irregularities

MAINTENANCE: SysEleven OpenStack Cloud announcement (DUS2)

Affected Components: SysEleven OpenStack Cloud in region DUS2

Scheduled Start: 20 Jan 2026, 22:00 CET

Scheduled End: 21 Jan 2026, 02:00 CET

State: SCHEDULED


Description:

We will perform an update of the OpenStack Compute service. During this update, all OpenStack API services in the region will be unavailable.


Customer Impact during the Maintenance:

  • OpenStack API services in region DUS2 will be unavailable (loss of control)
  • Running VMs will not be affected
  • Object storage will not be affected

Customer Actions:

  • No customer actions needed
  • Please inform us if you notice any irregularities

MAINTENANCE: SysEleven OpenStack Cloud announcement (HAM1)

Affected Components: SysEleven OpenStack Cloud in region HAM1

Scheduled Start: 27 Jan 2026, 22:00 CET

Scheduled End: 28 Jan 2026, 02:00 CET

State: SCHEDULED


Description:

We will perform an update of the OpenStack Compute service. During this update, all OpenStack API services in the region will be unavailable.


Customer Impact during the Maintenance:

  • OpenStack API services in region HAM1 will be unavailable (loss of control)
  • Running VMs will not be affected
  • Object storage will not be affected

Customer Actions:

  • No customer actions needed
  • Please inform us if you notice any irregularities

Past Incidents

Friday 22nd July 2022

No incidents reported

Thursday 21st July 2022

No incidents reported

Wednesday 20th July 2022

Network SysEleven Stack network issues in region FES

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

Tuesday 19th July 2022

SysEleven Login login.syseleven.de experiencing issues ("realm not found")

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

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

Monday 18th July 2022

No incidents reported

Sunday 17th July 2022

No incidents reported

Saturday 16th July 2022

No incidents reported

Friday 15th July 2022

No incidents reported

Thursday 14th July 2022

No incidents reported

Wednesday 13th July 2022

No incidents reported

Tuesday 12th July 2022

No incidents reported

Monday 11th July 2022

Virtual Machines Managed Platform (PVC) failure in a hardware node in DC BKI

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.

Sunday 10th July 2022

No incidents reported

Saturday 9th July 2022

No incidents reported

Friday 8th July 2022

No incidents reported

Thursday 7th July 2022

Control Plane Services (SysEleven - DBL) MetaKube connection issues to apiservers for clusters with nodes in CBK and DBL

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.

Wednesday 6th July 2022

No incidents reported

Tuesday 5th July 2022

No incidents reported

Monday 4th July 2022

No incidents reported

Sunday 3rd July 2022

No incidents reported

Saturday 2nd July 2022

No incidents reported

Friday 1st July 2022

No incidents reported

Thursday 30th June 2022

No incidents reported

Wednesday 29th June 2022

No incidents reported

Tuesday 28th June 2022

No incidents reported

Monday 27th June 2022

No incidents reported

Sunday 26th June 2022

No incidents reported

Saturday 25th June 2022

No incidents reported

Friday 24th June 2022

No incidents reported

Thursday 23rd June 2022

Network SysEleven Stack VPNaaS issues in region FES

At the moment we are facing API issues with VPNaaS in region FES. Already established VPNaaS connections should not be affected and should keep forwarding traffic. API problems make it impossible to create new VPNaaS connections, modify or delete existing.

We will keep you informed and apologize for any inconvenience.

Update 14:27: we believe to have fixed the problem but we are still observing and digging for the root cause.

Update 27th: our mitigation has proven stable. We stop watching while still investigating a more sustainable fix of the root cause.