UpCloud Outage History

UpCloud is up right now

There were 8 UpCloud outages since February 3, 2026 totaling 40h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.upcloud.com

Minor April 29, 2026

[FI-HEL2]: EUROPE-1 Managed Object Storage Performance Issues

Detected by Pingoru
Apr 29, 2026, 06:28 PM UTC
Resolved
Apr 29, 2026, 09:51 PM UTC
Duration
3h 22m
Affected: EUROPE-1: Managed Object Storage
Timeline · 4 updates
  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

Detected by Pingoru
Apr 22, 2026, 03:47 AM UTC
Resolved
Apr 22, 2026, 06:57 AM UTC
Duration
3h 9m
Affected: SG-SIN1: Cloud Servers
Timeline · 4 updates
  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

Detected by Pingoru
Apr 15, 2026, 07:44 AM UTC
Resolved
Apr 15, 2026, 11:17 AM UTC
Duration
3h 32m
Affected: US-SJO1: Cloud Servers
Timeline · 4 updates
  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

Detected by Pingoru
Mar 31, 2026, 01:48 AM UTC
Resolved
Mar 31, 2026, 06:33 AM UTC
Duration
4h 44m
Affected: US-NYC1: Storage Backends
Timeline · 3 updates
  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

Detected by Pingoru
Mar 16, 2026, 07:28 PM UTC
Resolved
Mar 17, 2026, 01:01 PM UTC
Duration
17h 32m
Affected: FI-HEL1: Cloud ServersFI-HEL1: Managed Load BalancerFI-HEL1: Managed Kubernetes
Timeline · 8 updates
  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

Detected by Pingoru
Mar 16, 2026, 12:02 PM UTC
Resolved
Mar 16, 2026, 03:06 PM UTC
Duration
3h 4m
Affected: APAC-1: Managed Object Storage
Timeline · 3 updates
  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

Detected by Pingoru
Mar 12, 2026, 01:24 PM UTC
Resolved
Mar 12, 2026, 06:29 PM UTC
Duration
5h 4m
Affected: EUROPE-1: Managed Object Storage
Timeline · 3 updates
  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

Detected by Pingoru
Feb 06, 2026, 04:22 AM UTC
Resolved
Feb 06, 2026, 04:27 AM UTC
Duration
5m
Affected: FI-HEL1: Cloud ServersFI-HEL1: Storage Backends
Timeline · 2 updates
  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 →

Looking to track UpCloud downtime and outages?

Pingoru polls UpCloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when UpCloud reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track UpCloud alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring UpCloud for free

5 free monitors · No credit card required