UpCloud Outage History

UpCloud is up right now

Pingoru has recorded 51 incidents for UpCloud: 38 in the last 12 months and 6 in the last 90 days.

Source: status.upcloud.com

51incidents recorded
38last 12 months
6last 90 days
24 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct33%
Pingoru began tracking UpCloud in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026310 of 720 (1%)
May 2026314 of 744 (2%)
June 20263340 of 720 (47%)
July 202611 of 744 (0%)
August 2026314 of 744 (2%)
September 202613 of 720 (0%)
October 20262178 of 535 (33%)

Incidents, newest first

Minor October 23, 2026 UpCloud API and Control Panel Connectivity Issues 1h 48m UpCloud Control Panel, API

Started Oct 23, 2026, 12:20 AM UTC· resolved Oct 23, 2026, 02:09 AM UTC

  1. investigating Oct 23, 2026, 12:20 AM UTC

    We are investigating a connectivity issue with the Control Panel and API.

  2. monitoring Oct 23, 2026, 12:51 AM UTC

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

  3. resolved Oct 23, 2026, 02:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 6, 2026 [SG-SIN1] Managed Object Storage Issue 7d 7h APAC-1: Managed Object Storage

Started Oct 06, 2026, 06:58 AM UTC· resolved Oct 13, 2026, 02:50 PM UTC

  1. identified Oct 06, 2026, 06:58 AM 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 the issue and fully restore service. We apologize for the inconvenience and will provide further updates as soon as possible. If you have any questions, please contact our support team via live chat or email [email protected]

  2. monitoring Oct 06, 2026, 06:13 PM 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 inconvenience caused. If you experience any issues, please contact our support team via live chat or at [email protected].

  3. resolved Oct 13, 2026, 02:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 28, 2026 [FI-HEL2]: File Storage Issues 2h 39m FI-HEL2: File Storage

Started Sep 28, 2026, 02:01 PM UTC· resolved Sep 28, 2026, 04:41 PM UTC

  1. investigating Sep 28, 2026, 02:01 PM 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 isolate the remaining issues and return the backend to its normal state. During these additional failovers for some of FI-HEL2 the File Storage NFS services can happen. We are sorry for the inconvenience.

  2. monitoring Sep 28, 2026, 03:34 PM UTC

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

  3. resolved Sep 28, 2026, 04:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 25, 2026 [DE-FRA1]: Storage Backend Issue 7h 3m DE-FRA1: Storage Backends

Started Aug 25, 2026, 11:45 PM UTC· resolved Aug 26, 2026, 06:49 AM UTC

  1. investigating Aug 25, 2026, 11:45 PM 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 patience as we work to address this. If you have any questions or concerns, please feel free to contact our 24/7 live support in our control panel or via email at [email protected].

  2. monitoring Aug 26, 2026, 03:47 AM UTC

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

  3. resolved Aug 26, 2026, 06:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 11, 2026 Cloud Server Deployment Error 1h 56m AU-SYD1: Cloud Servers, DE-FRA1: Cloud Servers, ES-MAD1: Cloud Servers, FI-HEL1: Cloud Servers and 11 more

Started Aug 11, 2026, 09:12 AM UTC· resolved Aug 11, 2026, 11:09 AM UTC

  1. identified Aug 11, 2026, 09:12 AM UTC

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

  2. identified Aug 11, 2026, 09:23 AM 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 avoid unexpected complications while we work to bring all affected services back online as swiftly as possible. We apologize for the inconvenience and will provide further updates as more information becomes available. If you have any questions or concerns regarding your services, please reach out to our support team via live chat at or via email: [email protected]

  3. identified Aug 11, 2026, 09:48 AM 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 Aug 11, 2026, 10:05 AM 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 [email protected]. We are compiling a detailed post-mortem to outline the sequence of events, the steps taken to rectify the situation, and the measures we are implementing to prevent such occurrences in the future. We understand the gravity of this disruption and extend our sincerest apologies to all affected customers.

  5. resolved Aug 11, 2026, 11:09 AM 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 [email protected] Thank you for your patience, and we apologize for any inconvenience caused.

Read the full incident report →

Minor August 3, 2026 Live Chat Temporarily Unavailable 5h 26m UpCloud Control Panel

Started Aug 03, 2026, 03:29 PM UTC· resolved Aug 03, 2026, 08:55 PM UTC

  1. identified Aug 03, 2026, 03:29 PM UTC

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

  2. resolved Aug 03, 2026, 08:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026 [EUROPE 2]: Object Storage Issue Identified 1h EUROPE-2: Managed Object Storage

Started Jul 07, 2026, 12:02 PM UTC· resolved Jul 07, 2026, 01:02 PM UTC

  1. identified Jul 07, 2026, 12:02 PM 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 possible.

  2. monitoring Jul 07, 2026, 12:18 PM UTC

    A fix have been implemented and we are monitoring this.

  3. resolved Jul 07, 2026, 01:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 16, 2026 DNS Resolution Issues in FI-HEL1 and FI-HEL2 3h 12m General, FI-HEL1: Other, FI-HEL2: Other

Started Jun 16, 2026, 10:18 AM UTC· resolved Jun 16, 2026, 01:30 PM UTC

  1. monitoring Jun 16, 2026, 10:18 AM 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 impact. We are continuing to monitor performance closely while we investigate the root cause. We apologise for the inconvenience. If you have any questions, please don't hesitate to contact us via email [email protected] or via live chat https://hub.upcloud.com/.

  2. resolved Jun 16, 2026, 01:30 PM 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 situation is stable. We apologise for the inconvenience. If you have any questions, please don't hesitate to contact us via email [email protected] or via live chat https://hub.upcloud.com/.

Read the full incident report →

Notice June 15, 2026 Payment processor issues with American Express 23d 20h

Started Jun 15, 2026, 01:12 PM UTC· resolved Jul 09, 2026, 09:18 AM UTC

  1. investigating Jun 15, 2026, 01:12 PM 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 successful. As a workaround, customers can use an alternative payment method while we work with our payment provider to resolve the issue. Available payment methods are listed here: https://upcloud.com/docs/getting-started/billing/payment-methods/ We will provide further updates as they become available. If you have any questions or need further assistance, please reach out to us via email: [email protected] or Live Chat in our control panel https://hub.upcloud.com

  2. identified Jun 18, 2026, 12:43 PM 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. Available payment methods are listed here: https://upcloud.com/docs/getting-started/billing/payment-methods/ We will provide further updates as they become available. If you have any questions or need further assistance, please reach out to us via email: [email protected] or Live Chat in our control panel https://hub.upcloud.com

  3. monitoring Jul 08, 2026, 01:44 PM 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 via email at [email protected] or via Live Chat in our control panel: https://hub.upcloud.com

  4. resolved Jul 09, 2026, 09:18 AM UTC

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

Read the full incident report →

Minor June 5, 2026 [SG-SIN1]: Networking issue 4h 20m SG-SIN1: Network Connections, SG-SIN1: Managed Kubernetes, AU-SYD1: Managed Kubernetes, APAC-1: Managed Object Storage

Started Jun 05, 2026, 02:50 PM UTC· resolved Jun 05, 2026, 07:11 PM UTC

  1. identified Jun 05, 2026, 02:50 PM 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. investigating Jun 05, 2026, 02:58 PM UTC

    We are currently investigating this issue.

  3. identified Jun 05, 2026, 03:32 PM 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 Unavailable (Cannot create, view, delete, scale, or modify clusters) 🟢 Managed Object Storage Workloads: Not Affected (100% Uptime) 🔴 UpCloud Managed Object Storage API & Control Panel Section: Temporarily Unavailable (Cannot create, view, delete, scale, or modify clusters) We are actively working to resolve the incident. We sincerely apologise for any inconvenience this may cause to your operations. We will provide regular updates here as more information becomes available. If you have any questions or need further assistance, please reach out to us via email: [email protected] or Live Chat in our control panel https://hub.upcloud.com

  4. monitoring Jun 05, 2026, 04:10 PM 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 Kubernetes API & Control Panel Section: Temporarily Unavailable (Cannot create, view, delete, scale, or modify clusters) 🟢 Managed Object Storage Workloads: Not Affected (100% Uptime) 🟢UpCloud Managed Object Storage API & Control Panel Section: Temporarily Unavailable (Cannot create, view, delete, scale, or modify clusters) If your services is still not fully functional, please contact our support at [email protected]. We apologise for the incident.

  5. resolved Jun 05, 2026, 07:11 PM 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 our Support team via Live Chat or email [email protected]. Thank you for your patience and we apologize for any inconvenience caused.

Read the full incident report →

Major May 26, 2026 Error with new cloud service deployments 3h 2m General

Started May 26, 2026, 02:42 PM UTC· resolved May 26, 2026, 05:44 PM UTC

  1. investigating May 26, 2026, 02:42 PM 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 May 26, 2026, 03:15 PM 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: [email protected] or via live chat from our control panel.

  3. resolved May 26, 2026, 05:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2026 [SG-SIN1]: Managed Kubernetes Issue 9h 12m SG-SIN1: Managed Kubernetes

Started May 13, 2026, 03:26 AM UTC· resolved May 13, 2026, 12:39 PM UTC

  1. investigating May 13, 2026, 03:26 AM 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 as more information becomes available. We apologise for any inconvenience this may cause.

  2. identified May 13, 2026, 06:11 AM 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 May 13, 2026, 08:20 AM UTC

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

  4. resolved May 13, 2026, 12:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 4, 2026 Control Panel https://hub.upcloud.com/ login issues 2h 5m UpCloud Control Panel, API

Started May 04, 2026, 11:15 AM UTC· resolved May 04, 2026, 01:21 PM UTC

  1. identified May 04, 2026, 11:15 AM 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. Please note that this issue is limited to the control panel login process. It does not affect your active cloud services. If you experience any issues when logging in, please do not hesitate to contact our support team via email [email protected] We apologise for the inconvenience.

  2. identified May 04, 2026, 12:28 PM UTC

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

  3. identified May 04, 2026, 12:28 PM UTC

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

  4. monitoring May 04, 2026, 12:35 PM UTC

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

  5. resolved May 04, 2026, 01:21 PM UTC

    This incident has been fully resolved. Please contact our support team via live chat or [email protected] if you have any further questions regarding the incident.

Read the full incident report →

Minor April 29, 2026 [FI-HEL2]: EUROPE-1 Managed Object Storage Performance Issues 3h 22m EUROPE-1: Managed Object Storage

Started Apr 29, 2026, 06:28 PM UTC· resolved Apr 29, 2026, 09:51 PM UTC

  1. identified Apr 29, 2026, 06:28 PM 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 (Europe-2, Europe-3, US-1, APAC-1) are unaffected. If you have any questions or concerns regarding your services, please reach out to our support team via live chat at https://hub.upcloud.com/ or via email: [email protected]

  2. identified Apr 29, 2026, 07:30 PM UTC

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

  3. monitoring Apr 29, 2026, 08:43 PM UTC

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

  4. resolved Apr 29, 2026, 09:51 PM 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 Chat or email [email protected] Thank you for your patience and we apologize for any inconvenience caused.

Read the full incident report →

Minor April 22, 2026 [SG-SIN1]: Compute node issue 3h 9m SG-SIN1: Cloud Servers

Started Apr 22, 2026, 03:47 AM UTC· resolved Apr 22, 2026, 06:57 AM UTC

  1. identified Apr 22, 2026, 03:47 AM 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 Apr 22, 2026, 04:53 AM UTC

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

  3. monitoring Apr 22, 2026, 05:07 AM 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 inconvenience and appreciate your patience as we continue working to address the situation. If you have any questions or concerns regarding your services, please reach out to our Support team via Live Chat or via email [email protected]

  4. resolved Apr 22, 2026, 06:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2026 Issue with new Cloud Server Deployments 3h 32m US-SJO1: Cloud Servers

Started Apr 15, 2026, 07:44 AM UTC· resolved Apr 15, 2026, 11:17 AM UTC

  1. investigating Apr 15, 2026, 07:44 AM 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 Apr 15, 2026, 08:09 AM 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 services, please reach out to our support team via Live Chat or email [email protected]

  3. monitoring Apr 15, 2026, 09:00 AM 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 any persistent issues with your cloud services in the US-SJO1 region, please reach out to our support team immediately via Live Chat or email [email protected]

  4. resolved Apr 15, 2026, 11:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2026 [US-NYC1]: Storage backend issue 4h 44m US-NYC1: Storage Backends

Started Mar 31, 2026, 01:48 AM UTC· resolved Mar 31, 2026, 06:33 AM UTC

  1. investigating Mar 31, 2026, 01:48 AM UTC

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

  2. monitoring Mar 31, 2026, 06:03 AM UTC

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

  3. resolved Mar 31, 2026, 06:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 16, 2026 [FI-HEL1]: Compute Node Issue 17h 32m FI-HEL1: Cloud Servers, FI-HEL1: Managed Load Balancer, FI-HEL1: Managed Kubernetes

Started Mar 16, 2026, 07:28 PM UTC· resolved Mar 17, 2026, 01:01 PM UTC

  1. identified Mar 16, 2026, 07:28 PM 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 clusters and load balancers in this zone. We are working to bring all affected services back online and resolve the situation as soon as possible. If you have any questions or concerns regarding your services, please reach out to our support team via live chat or at [email protected].

  2. identified Mar 16, 2026, 08:33 PM 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 regarding your services, please reach out to our support team via live chat at hub.upcloud.com or via email: [email protected]

  3. identified Mar 16, 2026, 09:34 PM 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 Mar 16, 2026, 10:36 PM UTC

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

  5. identified Mar 16, 2026, 11:37 PM UTC

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

  6. identified Mar 17, 2026, 12:36 AM 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 Mar 17, 2026, 01:38 AM 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 [email protected] or reach out to us via live chat at hub.upcloud.com We apologise for the incident.

  8. resolved Mar 17, 2026, 01:01 PM 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 Kubernetes clusters in that region. We sincerely apologise for this incident and we continue our internal investigation. If you have any remaining questions, please contact us via email at [email protected] or through our live chat https://hub.upcloud.com/

Read the full incident report →

Minor March 16, 2026 [APAC-1]: Object Storage 503 Errors 3h 4m APAC-1: Managed Object Storage

Started Mar 16, 2026, 12:02 PM UTC· resolved Mar 16, 2026, 03:06 PM UTC

  1. investigating Mar 16, 2026, 12:02 PM 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 Mar 16, 2026, 02:32 PM 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 [email protected] We are compiling a detailed post-mortem to outline the sequence of events, the steps taken to rectify the situation, and the measures we are implementing to prevent such occurrences in the future. We understand the gravity of this disruption and extend our sincerest apologies to all affected customers.

  3. resolved Mar 16, 2026, 03:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026 [Europe-1] Object Storage 5h 4m EUROPE-1: Managed Object Storage

Started Mar 12, 2026, 01:24 PM UTC· resolved Mar 12, 2026, 06:29 PM UTC

  1. investigating Mar 12, 2026, 01:24 PM 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 this. If you have any questions or concerns, please feel free to contact our 24/7 live Support team in our control panel or by emailing [email protected].

  2. monitoring Mar 12, 2026, 04:36 PM UTC

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

  3. resolved Mar 12, 2026, 06:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 6, 2026 [FI-HEL1]: Compute node issue 5m FI-HEL1: Cloud Servers, FI-HEL1: Storage Backends

Started Feb 06, 2026, 04:22 AM UTC· resolved Feb 06, 2026, 04:27 AM UTC

  1. identified Feb 06, 2026, 04:22 AM 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 Feb 06, 2026, 04:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 1, 2026 [UK-LON1]: Storage Backend Issue 2h 22m UK-LON1: Storage Backends

Started Feb 01, 2026, 04:34 PM UTC· resolved Feb 01, 2026, 06:57 PM UTC

  1. investigating Feb 01, 2026, 04:34 PM 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 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 this. If you have any questions or concerns, please feel free to contact our 24/7 live support in our control panel.

  2. resolved Feb 01, 2026, 06:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 23, 2026 [ES-MAD1]: Networking issue 2h 8m ES-MAD1: Network Connections

Started Jan 23, 2026, 08:39 AM UTC· resolved Jan 23, 2026, 10:47 AM UTC

  1. identified Jan 23, 2026, 08:39 AM 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 Jan 23, 2026, 09:39 AM UTC

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

  3. resolved Jan 23, 2026, 10:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 22, 2026 [ES-MAD1]: Networking Issue 3h 25m ES-MAD1: Network Connections

Started Jan 22, 2026, 09:24 PM UTC· resolved Jan 23, 2026, 12:49 AM UTC

  1. investigating Jan 22, 2026, 09:24 PM 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 Jan 22, 2026, 09:55 PM 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 Jan 22, 2026, 10:55 PM 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 ([email protected]).

  4. resolved Jan 23, 2026, 12:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 20, 2026 Issue with TLS Certification 16h 51m DK-CPH1: Managed Load Balancer, NO-SVG1: Managed Load Balancer, AU-SYD1: Managed Load Balancer, DE-FRA1: Managed Load Balancer and 30 more

Started Jan 20, 2026, 12:40 PM UTC· resolved Jan 21, 2026, 05:31 AM UTC

  1. identified Jan 20, 2026, 12:40 PM 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 inconvenience that this may cause and are working towards resolving the issue as soon as possible.

  2. identified Jan 20, 2026, 12:40 PM UTC

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

  3. identified Jan 20, 2026, 04:22 PM UTC

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

  4. monitoring Jan 21, 2026, 03:03 AM UTC

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

  5. resolved Jan 21, 2026, 05:31 AM UTC

    This incident has been resolved.

Read the full incident report →