UpCloud

Affected: APAC-1: Managed Object Storage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-06 06:58 UTC

   We have identified a service degradation issue affecting Managed Object Storage in our Singapore (SG-SIN1) data center. The issue causes periodic latency spikes and HTTP 503 errors that last 10 to 15 minutes. We have identified the root cause and are actively working to resolve...

2. monitoring 2026-10-06 18:13 UTC

   We have identified the root cause of the service degradation affecting Managed Object Storage in our Singapore (SG-SIN1) data center and have deployed a fix. We currently monitoring the system to ensure long-term stability. Thank you for your patience, and we apologize for any...

3. resolved 2026-10-13 14:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: FI-HEL2: File Storage

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-28 14:01 UTC

   We are investigating a File Storage service backend issue that is affecting some File Storage services in our FI-HEL2 data center. We noticed some unwanted failovers for some File Storage NFS services and as a safety measure we are performing some more failovers to resolve and...

2. monitoring 2026-09-28 15:34 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-28 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: DE-FRA1: Storage Backends

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-25 23:45 UTC

   We are investigating a storage backend issue that is affecting some resources including cloud servers in our DE-FRA1 data center. We are actively working to resolve this issue as swiftly as possible. We regret any inconvenience this might be causing and thank you for your...

2. monitoring 2026-08-26 03:47 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-26 06:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: AU-SYD1: Cloud Servers, DE-FRA1: Cloud Servers, ES-MAD1: Cloud Servers, FI-HEL1: Cloud Servers, FI-HEL2: Cloud Servers, NL-AMS1: Cloud Servers, PL-WAW1: Cloud Servers, SG-SIN1: Cloud Servers, UK-LON1: Cloud Servers, US:CHI1: Cloud Servers, US-NYC1: Cloud Servers, US-SJO1: Cloud Servers, SE-STO1: Cloud Servers, DK-CPH1: Cloud Servers, NO-SVG1: Cloud Servers

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-11 09:12 UTC

   The issue has been identified, and we are working on fixing it. It affects all new deployments in all zones.

2. identified 2026-08-11 09:23 UTC

   We have identified the cause of the issue affecting Cloud Server Deployments and are actively working on a fix. The issue may impact new Cloud Server Deployments. Please refrain from attempting management operations, including Start, Restart, Shut down, and Force Shutdown, to...

3. identified 2026-08-11 09:48 UTC

   A fix has been implemented, and new Cloud Server deployments are now proceeding without errors. We are currently cleaning up Cloud Servers that were left in an error state during the incident.

4. monitoring 2026-08-11 10:05 UTC

   We thank you for your continued patience throughout this process and apologize for any impact. The incident is now resolved, and all affected services should be operational. For any further issues, please contact our Support team via live chat or email at support@upcloud.com. We...

5. resolved 2026-08-11 11:09 UTC

   Our team has confirmed the full resolution of the issue. All affected services should now be functioning normally. If you continue to experience any further issues, please contact our Support team via Live Chat or email support@upcloud.com Thank you for your patience, and we...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-03 15:29 UTC

   We are currently experiencing technical issues with our Live Chat system. You can still reach our support team by emailing support@upcloud.com. We apologise for the inconvenience and we will provide an update as soon as live chat is restored.

2. resolved 2026-08-03 20:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: EUROPE-2: Managed Object Storage

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-07 12:02 UTC

   We have identified an issue with our Europe 2 Object Storage in our DE-FRA1 data centre. The problem may cause affected services to not be able to read or write to the object storage. We are working to bring all affected services back online and resolve the situation as soon as...

2. monitoring 2026-07-07 12:18 UTC

   A fix have been implemented and we are monitoring this.

3. resolved 2026-07-07 13:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: General, FI-HEL1: Other, FI-HEL2: Other

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-16 10:18 UTC

   We have resolved the DNS resolution issue that was causing increased response times. Impacting our control panel https://hub.upcloud.com/ and certain cloud services in the FI-HEL1 and FI-HEL2 data centres. All systems are now stable, and there should be no further visible...

2. resolved 2026-06-16 13:30 UTC

   We have resolved the DNS resolution issue that was causing increased response times. Impacting our control panel https://hub.upcloud.com/ and certain cloud services in the FI-HEL1 and FI-HEL2 data centres. After monitoring our systems for a some time, we can confirm now the...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-15 13:12 UTC

   We are investigating an issue affecting American Express card payments, for which we are seeing increased failure rates. All other payment methods remain fully operational. We would recommend those using American Express for Automated payments to check that these have been...

2. identified 2026-06-18 12:43 UTC

   The problem has been identified and we are working on a resolution. It specifically affects payments made in Euro, with American Express cards. As a workaround, customers can use an alternative payment method while we work with our payment provider to resolve the issue....

3. monitoring 2026-07-08 13:44 UTC

   A fix has been implemented, and Euro (EUR) payments utilizing American Express cards are once again processing normally. We are continuing to monitor the situation closely to ensure ongoing stability. If you have any questions or need further assistance, please reach out to us...

4. resolved 2026-07-09 09:18 UTC

   This is now resolved. If you have any questions or need further assistance, please reach out to us via email at support@upcloud.com or via Live Chat in our control panel: https://hub.upcloud.com

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: SG-SIN1: Network Connections, SG-SIN1: Managed Kubernetes, AU-SYD1: Managed Kubernetes, APAC-1: Managed Object Storage

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-05 14:50 UTC

   We have identified an issue with network connectivity in our SG-SIN1 data centre. The affected cloud servers may experience slow connections or become unreachable. We are working to restore connectivity and resolve the situation as soon as possible.

2. investigating 2026-06-05 14:58 UTC

   We are currently investigating this issue.

3. identified 2026-06-05 15:32 UTC

   We have identified an issue with network connectivity in our SG-SIN1 data centre and AU-SYD1 🟢 Managed Kubernetes Cluster Workloads: Not Affected (100% Uptime) 🟢 Kubernetes API / kubectl: Not Affected 🔴 UpCloud Managed Kubernetes API & Control Panel Section: Temporarily...

4. monitoring 2026-06-05 16:10 UTC

   We have restored all affected Managed Kubernetes and Managed Object Storage to normal operating status and will continue to monitor the situation. 🟢 Managed Kubernetes Cluster Workloads: Not Affected (100% Uptime) 🟢 Kubernetes API / kubectl: Not Affected 🟢 UpCloud Managed...

5. resolved 2026-06-05 19:11 UTC

   We have resolved the root cause of the networking issue affecting our Managed Object Storage and our Managed Kubernetes service in our SG-SIN1 data center. All affected services should now be functioning normally. If you continue to experience any further issues, please contact...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: General

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-26 14:42 UTC

   We are currently investigating an issue affecting new cloud service deployments. We apologise for the inconvenience and will provide an update in 30 minutes with more information.

2. monitoring 2026-05-26 15:15 UTC

   We have implemented the fix and isolated the issue. And we will keep monitoring the situation. We sincerely apologise for any inconvenience. And if you have any issues or questions, please don't hesitate to contact us via email: support@upcloud.com or via live chat from our...

3. resolved 2026-05-26 17:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: SG-SIN1: Managed Kubernetes

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 03:26 UTC

   We are currently investigating an issue affecting the Managed Kubernetes Service in our SG-SIN1 region. Users may find that their clusters are stuck in a Pending state. Our team is currently investigating the issue to identify the root cause. We will provide additional updates...

2. identified 2026-05-13 06:11 UTC

   We have identified the root cause of the issues affecting the Managed Kubernetes service in the SG-SIN1 region. Our team is currently working on a resolution to address the issue. We will provide further updates once the fix is applied.

3. monitoring 2026-05-13 08:20 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-13 12:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel, API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-04 11:15 UTC

   We have identified an issue causing slowness with new logins to our control panel at https://hub.upcloud.com/ And we are currently working on fully stabilising the situation. This may also delay calls to our API, and dependent systems such as Terraform. Please note that this...

2. identified 2026-05-04 12:28 UTC

   We are continuing to work on a fix for this issue.

3. identified 2026-05-04 12:28 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2026-05-04 12:35 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-05-04 13:21 UTC

   This incident has been fully resolved. Please contact our support team via live chat or support@upcloud.com if you have any further questions regarding the incident.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: EUROPE-1: Managed Object Storage

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-29 18:28 UTC

   We have identified an issue causing latency and timeouts when accessing or managing Managed Object Storage in the Europe-1 region. Users may experience temporary timeouts or failure which management operations or to load bucket details. All other Managed Object Storage regions...

2. identified 2026-04-29 19:30 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-04-29 20:43 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-29 21:51 UTC

   Our team has confirmed the full resolution of the issue affecting our EUROPE-1 Managed Object Storage in our FI-HEL2 data center. All affected services should now be functioning normally. If you continue to experience any further issues, please contact our Support team via Live...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: SG-SIN1: Cloud Servers

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-22 03:47 UTC

   We have identified an issue with one of the compute nodes in our SG-SIN1 data centre. The problem may cause affected cloud servers to become slow or unresponsive. We are working to bring all affected servers back online and resolve the situation as soon as possible.

2. monitoring 2026-04-22 04:53 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-04-22 05:07 UTC

   Our team continues to be fully engaged and focused on finding a mitigation. To avoid unexpected complications during the recovery process, please refrain from attempting server management operations, including Start, Restart, Shut down, and Force Shutdown. We apologize for the...

4. resolved 2026-04-22 06:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: US-SJO1: Cloud Servers

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-15 07:44 UTC

   We are currently investigating reports of issues affecting the deployment of new Cloud Servers in our US-SJO1 data center. We sincerely apologize for the inconvenience and will share more information as soon as it becomes available.

2. identified 2026-04-15 08:09 UTC

   We have identified the cause of the issue and applied a fix. While we are seeing signs of new Cloud Server deployment operations recovering, we are continuing to work on a permanent resolution to prevent a recurrence. If you have any questions or concerns regarding your...

3. monitoring 2026-04-15 09:00 UTC

   We have been monitoring the fix implemented earlier and all internal systems are performing as expected. All affected services have been fully restored. We will continue to monitor the situation until we can confirm the full resolution of the issue. If you continue to experience...

4. resolved 2026-04-15 11:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: US-NYC1: Storage Backends

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-31 01:48 UTC

   We are investigating a storage backend issue that is affecting some cloud servers in our US-NYC1 data centre.

2. monitoring 2026-03-31 06:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-31 06:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: FI-HEL1: Cloud Servers, FI-HEL1: Managed Load Balancer, FI-HEL1: Managed Kubernetes

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-16 19:28 UTC

   We have identified a compute node issue affecting some Cloud Servers, Managed Load Balancers and Managed Kubernetes services in our FI-HEL1 data center. You may experience unresponsive servers, delays or failures in provisioning new resources, or errors when managing existing...

2. identified 2026-03-16 20:33 UTC

   Our team is working to ensure all services are fully restored and operating normally. We have deployed a fix for the issue affecting the managed resources. It may take a short time for these changes to take effect across all resources. If you have any questions or concerns...

3. identified 2026-03-16 21:34 UTC

   We are continuing to work on this issue to ensure all services are fully restored to normal operation. The earlier fix is still finishing propagating to all managed resources.

4. identified 2026-03-16 22:36 UTC

   We are continuing to work on this issue to ensure all services are fully restored to normal operation.

5. identified 2026-03-16 23:37 UTC

   We are continuing to work on this issue to ensure all services are fully restored to normal operation.

6. identified 2026-03-17 00:36 UTC

   We are continuing to work on this issue to ensure all services are fully restored to normal operation. Normal operational status has been restored across the majority of our cloud infrastructure and managed services.

7. monitoring 2026-03-17 01:38 UTC

   We have restored all affected cloud servers to normal operating status and continue to monitor the situation. If your server is still not fully functional, please contact our support at support@upcloud.com or reach out to us via live chat at hub.upcloud.com We apologise for the...

8. resolved 2026-03-17 13:01 UTC

   We have been monitoring the situation closely over the 12 hours and can confirm that all affected services have now been fully restored. The Issue impacted some of our Managed Load Balancer instances within the FI-HEL1 Data Centre, which subsequently impacted some Managed...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: APAC-1: Managed Object Storage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-16 12:02 UTC

   We are currently investigating an issue affecting Managed Object Storage in our APAC-1 location, specifically returning 503 errors during operations sporadically. We apologise for the inconvenience and will provide further updates as more information becomes available.

2. monitoring 2026-03-16 14:32 UTC

   We thank you for your continued patience throughout this process and apologize for any impact. The incident is now resolved, and all affected services should be operational. For any further issues, please contact our Support team via live chat or email at support@upcloud.com We...

3. resolved 2026-03-16 15:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: EUROPE-1: Managed Object Storage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 13:24 UTC

   We are currently witnessing degraded performance with our Object Storage instances in our Europe-1 zone. We are actively working to resolve this issue as swiftly as possible. We regret any inconvenience this might be causing and thank you for your patience as we work to address...

2. monitoring 2026-03-12 16:36 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-12 18:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: FI-HEL1: Cloud Servers, FI-HEL1: Storage Backends

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-06 04:22 UTC

   We have identified an issue with one of the compute nodes in our Finland data centre. The problem may cause affected cloud servers to become slow or unresponsive. We are working to bring all affected servers back online and resolve the situation as soon as possible.

2. resolved 2026-02-06 04:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: SG-SIN1: Cloud Servers

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-03 13:23 UTC

   We have identified an issue with one of the compute nodes in our SG-SIN1 data centre. The problem may cause affected cloud servers to become slow or unresponsive. We are working to bring all affected servers back online and resolve the situation as soon as possible.

2. resolved 2026-02-03 13:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: SG-SIN1: Cloud Servers, SG-SIN1: Storage Backends

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-03 06:09 UTC

   We have identified an issue with one of the compute nodes in our Singapore data centre. The problem may cause affected cloud servers to become slow or unresponsive. We are working to bring all affected servers back online and resolve the situation as soon as possible.

2. identified 2026-02-03 06:30 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-02-03 06:45 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-02-03 07:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UK-LON1: Storage Backends

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-01 16:34 UTC

   We are currently investigating a storage backend issue affecting the UK-LON1 datacentre. This may impact Cloud Servers, Managed Kubernetes, Managed Databases and Object Storage. We recommend avoiding stopping/starting your server(s) at this time. We are actively working to...

2. resolved 2026-02-01 18:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: ES-MAD1: Network Connections

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-23 08:39 UTC

   We have identified an issue with network connectivity in our data centre. The affected cloud servers may experience slow connections or become unreachable. We are working to restore connectivity and resolve the situation as soon as possible.

2. monitoring 2026-01-23 09:39 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-23 10:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: ES-MAD1: Network Connections

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-22 21:24 UTC

   We are currently investigating an issue affecting network connections in our ES-MAD1 data center. We apologize for the inconvenience and will provide an update in 30 minutes with more information.

2. identified 2026-01-22 21:55 UTC

   We have identified the cause of the network connection issue affecting ES-MAD1 data center and are actively working on a fix.

3. monitoring 2026-01-22 22:55 UTC

   A fix was implemented and the network connections are working normally now. We will continue to monitor the status. For assistance with issues in ES-MAD1 please contact our Support team via live chat or email (support@upcloud.com).

4. resolved 2026-01-23 00:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: NO-SVG1: Managed Load Balancer, AU-SYD1: Managed Load Balancer, ES-MAD1: Managed Load Balancer, PL-WAW1: Managed Load Balancer, SG-SIN1: Managed Load Balancer, UK-LON1: Managed Load Balancer, US-CHI1: Managed Load Balancer, US-SJO1: Managed Load Balancer, NO-SVG1: Managed Kubernetes, DE-FRA1: Managed Load Balancer, FI-HEL1: Managed Load Balancer, NL-AMS1: Managed Load Balancer, US-NYC1: Managed Load Balancer, UK-LON1: Managed Kubernetes, SG-SIN1: Managed Kubernetes, US-CHI1: Managed Kubernetes, SE-STO1: Managed Load Balancer, AU-SYD1: Managed Kubernetes, ES-MAD1: Managed Kubernetes, PL-WAW1: Managed Kubernetes, US-SJO1: Managed Kubernetes, DK-CPH1: Managed Load Balancer, FI-HEL2: Managed Load Balancer, DE-FRA1: Managed Kubernetes, NL-AMS1: Managed Kubernetes, SE-STO1: Managed Kubernetes, FI-HEL1: Managed Kubernetes, US-NYC1: Managed Kubernetes, APAC-1: Managed Object Storage, US-1: Managed Object Storage, DK-CPH1: Managed Kubernetes, FI-HEL2: Managed Kubernetes, EUROPE-3: Managed Object Storage, EUROPE-1: Managed Object Storage

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-20 12:40 UTC

   We have identified an issue on newly created Managed Object Storage, Managed Kubernetes and Managed Load Balancer instances. This affects the creation and renewal of TLS/SSL certifications and is causing newly created instances to enter a pending state. We apologize for any...

2. identified 2026-01-20 12:40 UTC

   We are continuing to work on a fix for this issue.

3. identified 2026-01-20 16:22 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2026-01-21 03:03 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-01-21 05:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-09 19:56 UTC

   We are currently experiencing issues with our Live chat and emails. We are investigating the issue further and will report back as soon as possible. We thank you for your patience. All UpCloud Services remains fully functional.

2. monitoring 2026-01-09 21:12 UTC

   The issue has been resolved and Live chat / emails are now available as normal. We will continue to monitor the situation for stability.

3. resolved 2026-01-09 22:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-05 14:18 UTC

   We are currently experiencing issues with our Live chat and emails. We are investigating the issue further and will report back as soon as possible. We thank you for your patience. All UpCloud Services remains fully functional.

2. monitoring 2026-01-05 14:27 UTC

   The issue has been resolved and Live chat / emails are now available as normal. We will continue to monitor the situation for stability.

3. resolved 2026-01-05 16:03 UTC

   The incident regarding our Support Live chat and emails has been fully resolved, thanks for your patience.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: SE-STO1: Network Connections

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-22 04:25 UTC

   We are investigating a networking issue that is affecting some cloud servers in our SE-STO1 data centre.

2. identified 2025-12-22 05:03 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-12-22 05:21 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-12-22 07:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: NL-AMS1: Network Connections

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-22 04:23 UTC

   We are investigating a networking issue that is affecting some cloud servers in our NL-AMS1 data centre.

2. identified 2025-12-22 05:03 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-12-22 05:20 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-12-22 07:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UK-LON1: Network Connections

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-22 04:22 UTC

   We are investigating a networking issue that is affecting some cloud servers in our UK-LON1 data centre.

2. identified 2025-12-22 05:03 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-12-22 05:20 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-12-22 07:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: ES-MAD1: Managed Kubernetes, ES-MAD1: Other

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-16 00:43 UTC

   We have identified a network-related issue affecting services in the ES-MAD1 region. New clusters for the Managed Kubernetes service in ES-MAD1 are unable to be deployed and will receive an error message when attempting to do so. Existing clusters are currently operational and...

2. monitoring 2025-12-16 07:32 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-12-16 09:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: FI-HEL2: Cloud Servers, FI-HEL2: Network Connections, FI-HEL2: NAT Gateways, FI-HEL2: Managed Kubernetes

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-27 07:49 UTC

   We have identified the cause of the issue affecting some of our manged services in FI-HEL2 data center and are actively working on a fix. The issue impact is on networking level. Please refrain from attempting management operations including Start, Restart, Shut down and Force...

2. identified 2025-11-27 08:51 UTC

   Our team continues to be fully engaged and focused on finding a mitigation. To avoid unexpected complications during the recovery process, we continue to request that users refrain from attempting management operations, including Start, Restart, Shut down, and Force Shutdown.

3. identified 2025-11-27 09:32 UTC

   We have now isolated the issue and limited the impact. You can now safely do any stop and start operations. But we still continue work to fully restore services. If you still see any issues affecting your services in FI-HEL2 or have questions, please do not hesitate to contact...

4. monitoring 2025-11-27 09:49 UTC

   We thank you for your patience throughout this incident and apologize for any impact. The incident is now resolved, and all affected services should be operational. We will keep monitoring the situation. If you have any questions, please do not hesitate to contact our support,...

5. resolved 2025-11-27 10:51 UTC

   The incident affecting our FI-HEL2 data centre has been resolved. Our monitoring confirms that all systems are operating normally, and we have not observed any further issues. We sincerely apologise for the inconvenience caused, and will be conducting an internal investigation...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-22 09:51 UTC

   We are currently investigating reports of issues affecting the UpCloud API. Users may experience increased latency or intermittent failures when performing management actions, such as deploying, modifying, or deleting cloud resources. We sincerely apologise for the inconvenience...

2. monitoring 2025-11-22 11:34 UTC

   We are happy to report that the primary issue affecting the UpCloud API has been resolved and all management services are now functioning normally. We will continue to monitor the situation closely and will post an update as soon as the issue is fully resolved. We sincerely...

3. resolved 2025-11-22 13:14 UTC

   We can confirm that the issues affecting the UpCloud API are fully resolved and all management services are operating as expected. If you continue to experience issues, please reach out to our Support team via our 24/7 Live Chat or email support@upcloud.com. We sincerely...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-21 06:55 UTC

   We are currently investigating reports of issues affecting the UpCloud API. Users may experience increased latency or intermittent failures when performing management actions, such as deploying, modifying, or deleting cloud resources. We sincerely apologise for the inconvenience...

2. monitoring 2025-11-21 07:06 UTC

   We are happy to report that the primary issue affecting the UpCloud API has been resolved and all management services are now functioning normally. We will continue to monitor the situation closely and will post an update as soon as the issue is fully resolved. We sincerely...

3. resolved 2025-11-21 07:36 UTC

   We can confirm that the issues affecting the UpCloud API are fully resolved and all management services are operating as expected. If you continue to experience issues, please reach out to our Support team via our 24/7 Live Chat or email support@upcloud.com. We sincerely...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel, UpCloud Website

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 12:00 UTC

   We have identified an issue affecting our public website and control panel. During this time, users may experience difficulties when attempting to access certain pages at https://upcloud.com/ and https://hub.upcloud.com/ All services deployed remain accessible and are...

2. monitoring 2025-11-18 15:13 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-11-18 18:10 UTC

   Access to the UpCloud Control Panel and public website has been fully restored. The disruption was traced to a service incident with our upstream provider, Cloudflare. You can review their incident report here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 While the...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel, API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-03 19:17 UTC

   We are currently experiencing issues with our API and this is affecting server related actions globally and UpCloud Control panel. We are investigating the issue further and will report back as soon as possible.

2. identified 2025-11-03 19:38 UTC

   The issue with our API has been identified and we are currently working on deploying a fix.

3. monitoring 2025-11-03 20:06 UTC

   We have fixed the issue with the API affecting server configurations and deployments, and continue to monitor the situation. If you are still encountering some issues with your server, please contact our support at support@upcloud.com. We apologise for the incident.

4. resolved 2025-11-03 20:29 UTC

   The incident with our API has been resolved. If you are still having issues please reach out to our support via live chat or at support@upcloud.com. We apologize for the issues caused by this incident and appreciate your understanding.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-20 07:34 UTC

   We are currently experiencing issues with our Live chat and emails. We are investigating the issue further and will report back as soon as possible. We thank you for your patience. All UpCloud Services remains fully functional.

2. identified 2025-10-20 08:09 UTC

   If you require urgent attention, please reach out to us via email at support@upcloud.com

3. identified 2025-10-20 09:14 UTC

   Our support team is available via Email only at support@upcloud.com, our live chat remains inaccessible. We thank you for your patience.

4. monitoring 2025-10-20 10:08 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-10-21 02:56 UTC

   Our live chat has now returned to full functionality. Thank you for your utmost patience.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UK-LON1: Storage Backends

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-08 11:48 UTC

   We are currently investigating a potential issue with storage backend services in UK-LON1

2. identified 2025-10-08 12:03 UTC

   We have identified the cause of the issue affecting the storage backend and are actively working on a fix. We apologise for the inconvenience and will provide further updates as more information becomes available If you have any further questions please contact support via live...

3. monitoring 2025-10-08 13:34 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-10-08 14:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: FI-HEL1: Storage Backends

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-07 07:16 UTC

   We have identified an issue with our Backups nodes in our FI-HEL1 data centre. This issue may cause the Backups to be unavailable at this moment. We are working to restore the services and resolve the situation as soon as possible. Please note that all data is still intact. If...

2. monitoring 2025-10-07 09:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-10-07 11:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: US-SJO1: Managed Kubernetes

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-07 01:20 UTC

   We are currently investigating an issue impacting Managed Kubernetes cluster creation and management operations in our US-SJO1 datacenter. During this time, users may experience errors provisioning new clusters, as well as making changes to existing clusters for both the cluster...

2. identified 2025-10-07 09:06 UTC

   We have identified the issue affecting cluster operations in the San Jose (us-sjo1) region and are working on a fix.

3. monitoring 2025-10-07 11:34 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-10-07 13:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: PL-WAW1: Network Connections, PL-WAW1: Managed Kubernetes

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-22 23:43 UTC

   We are currently investigating connectivity issues impacting services in the pl-waw1 region. Users of the affected services in the pl-waw1 region may experience degraded performance or intermittent connectivity errors. The provisioning of new Cloud Servers, Managed Object...

2. investigating 2025-07-23 00:13 UTC

   We have now added PL-WAW1 Virtualization Hosts and Network Connections, Users may experience degraded performance or intermittent connectivity errors.

3. identified 2025-07-23 02:49 UTC

   We have identified a connectivity issue that is impacting the creation and management of new and existing Cloud Servers, Managed Object Storage and Managed Kubernetes clusters in our PL-WAW1 data center. During this time, users may experience failures or delays when provisioning...

4. monitoring 2025-07-23 03:04 UTC

   We have implemented a fix to address the connectivity issue affecting the creation and management of new and existing Cloud Servers, Managed Object Storage and Managed Kubernetes clusters in our PL-WAW1 data center. Initial reports indicate that impacted services are now...

5. resolved 2025-07-23 06:27 UTC

   We have successfully resolved the connectivity issue affecting the creation and management of new and existing Cloud Servers, Managed Object Storage and Managed Kubernetes clusters in our PL-WAW1 data center. The impacted services are now functioning as expected. If you continue...

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-07-16 01:39 UTC

   We have identified an issue affecting our public website. During this time, users may experience difficulties when attempting to access certain pages at https://upcloud.com/ The UpCloud Control Panel (https://hub.upcloud.com/) remains accessible and is unaffected. We apologize...

2. resolved 2025-07-16 13:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: DE-FRA1: Managed Kubernetes

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-10 13:43 UTC

   We are currently investigating an issue affecting the Managed Kubernetes service in our DE-FRA1 datacenter. During this time, users may experience new Managed Kubernetes service deployment failing or the Kube API temporarily failing. We are actively working on identifying the...

2. monitoring 2025-07-10 14:27 UTC

   A fix has been implemented for the issue affecting the Managed Kubernetes service in our DE-FRA1 datacenter. We will continue to monitor the situation. If you are still having issues feel free to reach out to our support at support@upcloud.com.

3. monitoring 2025-07-10 14:27 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-07-10 15:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: ES-MAD1: Managed Kubernetes

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-19 15:40 UTC

   We are currently investigating an issue affecting the Managed Kubernetes service in our ES-MAD1 datacenter. During this time, users may experience new Managed Kubernetes service deployment failing or services not completing terminations. We are actively working on identifying...

2. monitoring 2025-06-19 17:41 UTC

   A fix has been implemented for the issue affecting the Managed Kubernetes service in our ES-MAD1 datacenter. We will continue to monitor the situation. If you are still having issues feel free to reach out to our support at support@upcloud.com.

3. resolved 2025-06-19 18:58 UTC

   This incident has been resolved. If you are still experiencing issues please contact our support at support@upcloud.com.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: US-CHI1: Managed Kubernetes

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-06 05:17 UTC

   We are currently investigating an issue affecting the Managed Kubernetes service in our US-CHI1 data center. During this time, users may experience new Managed Kubernetes service deployment failing. We are actively working on identifying the root cause of the issue and will post...

2. monitoring 2025-06-06 07:57 UTC

   We have successfully resolved the issue that impacted the Managed Kubernetes service in our US-CHI1 data center. New Managed Kubernetes service deployment should now be working as expected. Thank you for your patience while we worked to address the issue. If you are still...

3. resolved 2025-06-06 09:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: AU-SYD1: Managed Load Balancer, ES-MAD1: Managed Load Balancer, PL-WAW1: Managed Load Balancer, SG-SIN1: Managed Load Balancer, UK-LON1: Managed Load Balancer, US-CHI1: Managed Load Balancer, US-SJO1: Managed Load Balancer, DE-FRA1: Managed Load Balancer, FI-HEL1: Managed Load Balancer, NL-AMS1: Managed Load Balancer, US-NYC1: Managed Load Balancer, SE-STO1: Managed Load Balancer, FI-HEL2: Managed Load Balancer

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-22 15:44 UTC

   We have identified an issue with our Managed Load Balancer service across all data centres. Our team is actively investigating the root cause and working on a resolution.

2. identified 2025-05-22 17:00 UTC

   We are continuing to work on a fix for this issue. You may experience intermittent issues fetching load balancer details and timeouts accessing the Managed Load Balancer page from the Dashboard. Deployed Managed Load Balancers may have intermittent timeouts as we work on the...

3. identified 2025-05-22 17:22 UTC

   We've deployed a fix we believe has resolved the issues with our Managed Load Balancer service. We will continue to monitor the situation closely.

4. monitoring 2025-05-22 18:24 UTC

   The deployed fix has successfully resolved the issues affecting our Managed Load Balancer service. We will continue to closely monitor the service to ensure continued stability.

5. resolved 2025-05-22 19:24 UTC

   This incident has been resolved. If you have any questions about this, we have our 24/7 support team available via live chat in the control panel or via email at support@upcloud.com.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-04-02 19:14 UTC

   We are currently experiencing issues with our public website. We are investigating the issue further and will report back as soon as possible. The UpCloud dashboard and all resources are unaffected. If you have any questions or concerns, please reach out to our Support team via...

2. monitoring 2025-04-02 20:09 UTC

   We have implemented a fix and are monitoring the website. If you have any questions or concerns, please reach out to our Support team via email (support@upcloud.com) or live chat.

3. resolved 2025-04-02 21:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UpCloud Control Panel

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-04-02 05:01 UTC

   We are currently experiencing issues with login access to the UpCloud Control Panel. We are investigating the issue further and will report back as soon as possible. Please note that no customer resources are affected by this issue.

2. monitoring 2025-04-02 05:07 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2025-04-02 05:20 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-04-02 06:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on UpCloud's status page.

Affected: UK-LON1: Storage Backends

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-02-19 21:06 UTC

   We have identified an issue with one of our storage backend nodes in our UK-LON1 data centre. Some servers with Standard tier storage are affected. We are working to restore the service and resolve the situation as soon as possible. We recommend avoiding stopping or starting...

2. identified 2025-02-19 21:09 UTC

   We have identified some compute nodes that may be affected by this storage backend issue.

3. identified 2025-02-19 22:29 UTC

   We are continuing to work on a fix for this storage backend issue. A majority of affected services have been brought back online, though some instances in UK-LON1 remain impacted and will need to be restarted.

4. identified 2025-02-19 23:37 UTC

   We are continuing to work on a fix for this storage backend issue. Most remaining affected services have been restored.

5. identified 2025-02-20 00:26 UTC

   We are continuing to work on a fix for this storage backend issue. More affected services have been restored. Some Object Storage EOL services experienced temporary disruptions during this restoration process.

6. monitoring 2025-02-20 01:57 UTC

   Our team has implemented a fix to resolve the storage backend issue in our UK-LON1 data centre and all affected services should be operational again. We thank you for your continued patience throughout this recovery process and sincerely apologize for any inconvenience caused....

7. resolved 2025-02-20 02:46 UTC

   Our team has resolved the issue and all affected services are now working as expected. If you continue to experience any further issues, please contact our Support team via Live Chat or email support@upcloud.com Pleae accept our sincere apologise again for any inconvenience...

Excerpts are shortened. Read the full incident on UpCloud's status page.