Active Incident

Updated a few seconds ago

Elevated error rates in object storage APIDegraded Performance

Incident Status

Degraded Performance

Components

OpenStack

Locations

STO1 - Stockholm South, STO2 - Stockholm West, STO3 - Stockholm North


February 12, 2026 14:41 CET
February 12, 2026 13:41 UTC
MONITORING

We received alerts of higher than normal error rates of the object storage API in OpenStack for a period of 10 minutes (14.22 to 14.32 CET) due to a hardware failure in the proxy layer. The issue healed automatically but we will continue to monitor the situation and check why the automatic fail over did not remove the faulty node sooner.
Issue with storage-service in STO1 on V2-volumesOperational

Incident Status

Operational

Components

DBaaS, Kubernetes, OpenStack

Locations

STO1 - Stockholm South


November 28, 2025 08:50 CET
November 28, 2025 07:50 UTC
INVESTIGATING

We have identified a ongoing disturbance with our V2-storage (all types) service in AZ STO1 since early this morning. We advice to not perform volume modifications, re-attachments or rebuilds at this moment related to V2 in STO1 as we are seeing issues with the stability of the service. We will keep this updated throughout the day.

November 28, 2025 10:11 CET
November 28, 2025 09:11 UTC
IDENTIFIED

We have made findings around the problem and will roll out a temporary workaround on V2 storage to reduce impact on customer operations. Next update in approx 2 hours, or less if possible.

November 28, 2025 11:37 CET
November 28, 2025 10:37 UTC
MONITORING

A workaround is implemented and solves the immidiate issue on impacted V2 storage volumes, however we are still working on a permanent resolution. Another update will be posted during the afternoon (CET).

November 28, 2025 14:12 CET
November 28, 2025 13:12 UTC
MONITORING

Afternoon update: Workaround is in place and after monitoring we are confident that it is effective and problems and impacts are resolved. For now we will continue to monitor this over the weekend and are awaiting the results and findings from our supplier.

December 9, 2025 13:26 CET
December 9, 2025 12:26 UTC
MONITORING

We have gotten updated binaries from our vendor which will add more debug information to help triaging the issue in the storage cluster. This patch will be applied during the day. This should not affect the storage system but does pose an elevated risk.

Scheduled Maintenance

DBaaS management upgradePlanned Maintenance

Schedule

February 17, 2026 09:00 - 12:00 CET
February 17, 2026 08:00 - 11:00 UTC

Components

DBaaS

Locations

STO1 - Stockholm South, STO2 - Stockholm West, STO3 - Stockholm North

Description

We will be upgrading our database management system. During the maintenance window, you might see intermittent unavailability and your datastores may appear as 'Unreachable' in the user interface. This is purely a visual issue, and connections to your databases will not be affected. There will be no impact on customer datastores.

2

Active Incidents

0

Active Maintenances

1

Upcoming Maintenances

Cloud Connect




Operational

Cloud VPN




Operational

DBaaS




Operational

Mail Relay




Operational

Kubernetes




Operational

OpenStack




Degraded Performance

Virtuozzo PaaS




Operational

Application Monitoring




Operational

The Vault




Operational

External Services

GitHub

Let's Encrypt

Slack

Zendesk

History (Last 7 days)

Intermittent issues against s3-APIsPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Kubernetes, OpenStack


Locations

STO1 - Stockholm South, STO2 - Stockholm West, STO3 - Stockholm North



February 10, 2026 13:44 CET
February 10, 2026 12:44 UTC
INVESTIGATING

We are currently investigating signs of intermittent issues with calls against our s3 API. We are seeing 403-errors occurring intermittently. Updates will continue as investigating moves forward.

February 10, 2026 15:12 CET
February 10, 2026 14:12 UTC
IDENTIFIED

We have found a issue and restarted proxy-services in all DCs. Initially no signs of issues in our logs however we are still monitoring and investigating to ensure there are no outstanding issues remaining.

February 11, 2026 12:17 CET
February 11, 2026 11:17 UTC
RESOLVED

Issue has been resolved without further noticed impact since late yesterday.
Kubernetes PCaaS orchestration maintenance - apply fixPlanned Maintenance

Description

We will deploy a fix for our PCaaS orchestration to avoid manual work in coming cluster upgrades. No expected impact for any functionality on customer workloads.


Components

Kubernetes


Locations

STO1 - Stockholm South, STO2 - Stockholm West, STO3 - Stockholm North


Schedule

February 11, 2026 10:00 - February 11, 2026 12:00 CET
February 11, 2026 09:00 - February 11, 2026 11:00 UTC


February 11, 2026 10:00 CET
February 11, 2026 09:00 UTC
UPDATE

Scheduled maintenance is starting.

February 11, 2026 12:00 CET
February 11, 2026 11:00 UTC
UPDATE

Scheduled maintenance is complete.
Upgrade Kubernetes PCaaS orchestration cont'dPlanned Maintenance

Description

We are upgrading our backend for PCaaS orchestration to support newer Kubernetes versions. No impact to customer workloads is expected.


Components

Kubernetes


Locations

STO1 - Stockholm South, STO2 - Stockholm West, STO3 - Stockholm North


Schedule

February 9, 2026 15:00 - February 9, 2026 17:00 CET
February 9, 2026 14:00 - February 9, 2026 16:00 UTC


February 9, 2026 15:40 CET
February 9, 2026 14:40 UTC
UPDATE

Scheduled Upgrade of Kubernetes PCaaS orchestration

February 10, 2026 14:15 CET
February 10, 2026 13:15 UTC
UPDATE

All work with yesterdays maintenance has been finalized, some outstanding issues with alerts on kube-controler-managers has been resolved (was not causing impact but triggered alerting).
Hypervisor crasch in sto1Operational

Incident Status

Operational


Components

DBaaS, Kubernetes, OpenStack


Locations

STO1 - Stockholm South



January 27, 2026 08:48 CET
January 27, 2026 07:48 UTC
IDENTIFIED

A single shared v1 hypervisor rebooted due to hardware issues at 07:36 CET causing some instances to stop. The hypervisor in question is disabled and all customer instances will be migrated to other hardware. All affected customer managed instances that is shut off needs to be manually started again.

February 9, 2026 15:39 CET
February 9, 2026 14:39 UTC
RESOLVED

The problematic hypervisor has been taken out of service and all remaining issues should be resolved.
DBaaS emergency management maintenance Planned Maintenance

Description

We will deploy a hotfix for our database management system. The fix addresses a problem with the control plane communication to the object storage. During the emergency maintenance, you might experience intermittent unavailability and your datastores may appear as 'Unreachable' in the user interface. This is purely a visual issue, and connections to your databases will not be affected. There will be no impact on customer datastores.


Components

DBaaS


Locations

STO1 - Stockholm South, STO2 - Stockholm West, STO3 - Stockholm North


Schedule

February 9, 2026 10:00 - February 9, 2026 12:00 CET
February 9, 2026 09:00 - February 9, 2026 11:00 UTC


February 9, 2026 10:00 CET
February 9, 2026 09:00 UTC
UPDATE

Scheduled maintenance is starting.

February 9, 2026 10:20 CET
February 9, 2026 09:20 UTC
UPDATE

The maintenance is completed.