kyberio Status Status

Secure Public Cloud - API Currently Unreachable

Monitoring - A fix has been implemented and we are monitoring the results.
Mar 02, 2026 - 12:39 CET

Investigating - The OpenStack API endpoints are currently unreachable. As a result, API-based operations (e.g., instance management, network operations, volume management) are not possible at this time.

Our team is currently investigating the incident.
Mar 02, 2026 - 12:00 CET

General Operational

Operations Center Operational

Monitoring Operational

Core Network & Routing Operational

Customer Control Center Operational

Datacenters Operational

DE01 AZ1 (Hannover) Operational

DE01 AZ2 (Hannover) Operational

DE02 AZ1 (Wolfsburg) Operational

DE03 (Frankfurt PoP) Operational

Core Services Operational

VMware Cloud Operational

Siteaccelerator CDN Operational

Enterprise DNS Operational

Sitebalancer GSLB Operational

E-Mail Services Operational

DDoS Protection Service Operational

Domain Registration Operational

Backup-System (Onsite) Operational

Backup-System (Offsite) Operational

Secure Public Cloud Operational

Compute Operational

Volumes (Block-Storage) Operational

Object-Storage (S3) Operational

Network-Services Operational

Dashboard Operational

API Operational

KMS Operational

LBaaS Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Mar 2, 2026

Unresolved incident: Secure Public Cloud - API Currently Unreachable.

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

No incidents reported.

Feb 26, 2026

No incidents reported.

Feb 25, 2026

No incidents reported.

Feb 24, 2026

No incidents reported.

Feb 23, 2026

No incidents reported.

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Feb 20, 2026

No incidents reported.

Feb 19, 2026

Incident - Secure Public Cloud (OpenStack)

Resolved - The root cause of the incident has been identified and successfully resolved.

All components are now operating normally.

We will continue to monitor the environment to ensure ongoing stability.

Thank you for your patience and understanding.
Feb 19, 15:33 CET

Identified - Unfortunately, extended monitoring has shown that the previously applied patch did not result in an improvement.

The issue is currently still under investigation. Our teams are continuing to analyze the root cause in order to identify the problem and implement appropriate corrective actions.

We will provide further updates as soon as new information becomes available.
Feb 18, 19:16 CET

Monitoring - The root cause of the incident affecting the RabbitMQ service in our Secure Public Cloud has been identified, and a patch has been successfully applied.

The service is now operating normally. We have moved the incident status to Monitoring to ensure continued stability.

Running workloads were not affected during the incident.

Our team will continue to closely monitor the environment.
We will provide further updates if necessary.
Feb 18, 01:01 CET

Investigating - We are currently experiencing an incident affecting the RabbitMQ service in our Secure Public Cloud.
As a result, it is currently not possible to perform changes to existing resources.

Running workloads are not affected by this incident and continue to operate normally.

Our team is already working on analysis and resolution.
We will provide updates as soon as more information becomes available.
Feb 17, 20:05 CET

Feb 18, 2026

Feb 17, 2026

Feb 16, 2026

No incidents reported.