Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Upcloud outage history

    59 recorded Upcloud incidents since August 2024, with official updates, affected components, duration and resolution information.

    Back to current status

    UpCloud API and Control Panel Connectivity Issues

    Started October 23, 2026 at 12:20 AM UTC · 1h 48m

    IssuesMinor incident
    Affected components
    UpCloud Control PanelAPI
    1. October 23, 2026 at 12:20 AM UTCinvestigating

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

    2. October 23, 2026 at 12:51 AM UTCmonitoring

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

    3. October 23, 2026 at 2:09 AM UTCresolved

      This incident has been resolved.

    [SG-SIN1] Managed Object Storage Issue

    Started October 6, 2026 at 6:58 AM UTC · 7d 7h

    IssuesMinor incident
    Affected components
    APAC-1: Managed Object Storage
    1. October 6, 2026 at 6:58 AM UTCidentified

      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. October 6, 2026 at 6:13 PM UTCmonitoring

      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. October 13, 2026 at 2:50 PM UTCresolved

      This incident has been resolved.

    [FI-HEL2]: File Storage Issues

    Started September 28, 2026 at 2:01 PM UTC · 2h 40m

    IssuesMinor incident
    Affected components
    FI-HEL2: File Storage
    1. September 28, 2026 at 2:01 PM UTCinvestigating

      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. September 28, 2026 at 3:34 PM UTCmonitoring

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

    3. September 28, 2026 at 4:41 PM UTCresolved

      This incident has been resolved.

    [DE-FRA1]: Storage Backend Issue

    Started August 25, 2026 at 11:45 PM UTC · 7h 4m

    IssuesMinor incident
    Affected components
    DE-FRA1: Storage Backends
    1. August 25, 2026 at 11:45 PM UTCinvestigating

      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. August 26, 2026 at 3:47 AM UTCmonitoring

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

    3. August 26, 2026 at 6:49 AM UTCresolved

      This incident has been resolved.

    Cloud Server Deployment Error

    Started August 11, 2026 at 9:12 AM UTC · 1h 57m

    OutageMajor incident
    Affected components
    SG-SIN1: Cloud ServersPL-WAW1: Cloud ServersAU-SYD1: Cloud ServersDK-CPH1: Cloud ServersUK-LON1: Cloud ServersSE-STO1: Cloud ServersUS:CHI1: Cloud ServersDE-FRA1: Cloud ServersNO-SVG1: Cloud ServersNL-AMS1: Cloud ServersFI-HEL2: Cloud ServersES-MAD1: Cloud ServersUS-NYC1: Cloud ServersUS-SJO1: Cloud ServersFI-HEL1: Cloud Servers
    1. August 11, 2026 at 9:12 AM UTCidentified

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

    2. August 11, 2026 at 9:23 AM UTCidentified

      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. August 11, 2026 at 9:48 AM UTCidentified

      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. August 11, 2026 at 10:05 AM UTCmonitoring

      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. August 11, 2026 at 11:09 AM UTCresolved

      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.

    Live Chat Temporarily Unavailable

    Started August 3, 2026 at 3:29 PM UTC · 5h 26m

    IssuesMinor incident
    Affected components
    UpCloud Control Panel
    1. August 3, 2026 at 3:29 PM UTCidentified

      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. August 3, 2026 at 8:55 PM UTCresolved

      This incident has been resolved.

    [EUROPE 2]: Object Storage Issue Identified

    Started July 7, 2026 at 12:02 PM UTC · 1h 1m

    IssuesMinor incident
    Affected components
    EUROPE-2: Managed Object Storage
    1. July 7, 2026 at 12:02 PM UTCidentified

      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. July 7, 2026 at 12:18 PM UTCmonitoring

      A fix have been implemented and we are monitoring this.

    3. July 7, 2026 at 1:02 PM UTCresolved

      This incident has been resolved.

    DNS Resolution Issues in FI-HEL1 and FI-HEL2

    Started June 16, 2026 at 10:18 AM UTC · 3h 12m

    Pending
    Affected components
    GeneralFI-HEL2: OtherFI-HEL1: Other
    1. June 16, 2026 at 10:18 AM UTCmonitoring

      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. June 16, 2026 at 1:30 PM UTCresolved

      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/.

    Payment processor issues with American Express

    Started June 15, 2026 at 1:12 PM UTC · 23d 20h

    Pending
    1. June 15, 2026 at 1:12 PM UTCinvestigating

      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. June 18, 2026 at 12:43 PM UTCidentified

      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. July 8, 2026 at 1:44 PM UTCmonitoring

      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. July 9, 2026 at 9:18 AM UTCresolved

      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

    [SG-SIN1]: Networking issue

    Started June 5, 2026 at 2:50 PM UTC · 4h 21m

    IssuesMinor incident
    Affected components
    SG-SIN1: Managed KubernetesAU-SYD1: Managed KubernetesAPAC-1: Managed Object StorageSG-SIN1: Network Connections
    1. June 5, 2026 at 2:50 PM UTCidentified

      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. June 5, 2026 at 2:58 PM UTCinvestigating

      We are currently investigating this issue.

    3. June 5, 2026 at 3:32 PM UTCidentified

      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. June 5, 2026 at 4:10 PM UTCmonitoring

      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. June 5, 2026 at 7:11 PM UTCresolved

      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.

    Error with new cloud service deployments

    Started May 26, 2026 at 2:42 PM UTC · 3h 2m

    OutageMajor incident
    Affected components
    General
    1. May 26, 2026 at 2:42 PM UTCinvestigating

      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. May 26, 2026 at 3:15 PM UTCmonitoring

      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. May 26, 2026 at 5:44 PM UTCresolved

      This incident has been resolved.

    [SG-SIN1]: Managed Kubernetes Issue

    Started May 13, 2026 at 3:26 AM UTC · 9h 13m

    IssuesMinor incident
    Affected components
    SG-SIN1: Managed Kubernetes
    1. May 13, 2026 at 3:26 AM UTCinvestigating

      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. May 13, 2026 at 6:11 AM UTCidentified

      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. May 13, 2026 at 8:20 AM UTCmonitoring

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

    4. May 13, 2026 at 12:39 PM UTCresolved

      This incident has been resolved.

    Control Panel https://hub.upcloud.com/ login issues

    Started May 4, 2026 at 11:15 AM UTC · 2h 6m

    Pending
    Affected components
    UpCloud Control PanelAPI
    1. May 4, 2026 at 11:15 AM UTCidentified

      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 issue does not affect your active cloud services. If you experience any issues, please do not hesitate to contact our support team via email [email protected]. We apologise for the inconvenience.

    2. May 4, 2026 at 12:28 PM UTCidentified

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

    3. May 4, 2026 at 12:35 PM UTCmonitoring

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

    4. May 4, 2026 at 1:21 PM UTCresolved

      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.

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

    Started April 29, 2026 at 6:28 PM UTC · 3h 23m

    IssuesMinor incident
    Affected components
    EUROPE-1: Managed Object Storage
    1. April 29, 2026 at 6:28 PM UTCidentified

      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. April 29, 2026 at 7:30 PM UTCidentified

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

    3. April 29, 2026 at 8:43 PM UTCmonitoring

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

    4. April 29, 2026 at 9:51 PM UTCresolved

      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.

    [SG-SIN1]: Compute node issue

    Started April 22, 2026 at 3:47 AM UTC · 3h 10m

    IssuesMinor incident
    Affected components
    SG-SIN1: Cloud Servers
    1. April 22, 2026 at 3:47 AM UTCidentified

      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. April 22, 2026 at 4:53 AM UTCmonitoring

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

    3. April 22, 2026 at 5:07 AM UTCmonitoring

      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. April 22, 2026 at 6:57 AM UTCresolved

      This incident has been resolved.

    Issue with new Cloud Server Deployments

    Started April 15, 2026 at 7:44 AM UTC · 3h 33m

    IssuesMinor incident
    Affected components
    US-SJO1: Cloud Servers
    1. April 15, 2026 at 7:44 AM UTCinvestigating

      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. April 15, 2026 at 8:09 AM UTCidentified

      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. April 15, 2026 at 9:00 AM UTCmonitoring

      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. April 15, 2026 at 11:17 AM UTCresolved

      This incident has been resolved.

    [US-NYC1]: Storage backend issue

    Started March 31, 2026 at 1:48 AM UTC · 4h 45m

    IssuesMinor incident
    Affected components
    US-NYC1: Storage Backends
    1. March 31, 2026 at 1:48 AM UTCinvestigating

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

    2. March 31, 2026 at 6:03 AM UTCmonitoring

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

    3. March 31, 2026 at 6:33 AM UTCresolved

      This incident has been resolved.

    [FI-HEL1]: Compute Node Issue

    Started March 16, 2026 at 7:28 PM UTC · 17h 33m

    Pending
    Affected components
    FI-HEL1: Managed Load BalancerFI-HEL1: Managed KubernetesFI-HEL1: Cloud Servers
    1. March 16, 2026 at 7:28 PM UTCidentified

      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. March 16, 2026 at 8:33 PM UTCidentified

      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. March 16, 2026 at 9:34 PM UTCidentified

      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. March 16, 2026 at 11:37 PM UTCidentified

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

    5. March 17, 2026 at 12:36 AM UTCidentified

      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.

    6. March 17, 2026 at 1:38 AM UTCmonitoring

      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.

    7. March 17, 2026 at 1:01 PM UTCresolved

      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/

    [APAC-1]: Object Storage 503 Errors

    Started March 16, 2026 at 12:02 PM UTC · 3h 4m

    IssuesMinor incident
    Affected components
    APAC-1: Managed Object Storage
    1. March 16, 2026 at 12:02 PM UTCinvestigating

      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. March 16, 2026 at 2:32 PM UTCmonitoring

      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. March 16, 2026 at 3:06 PM UTCresolved

      This incident has been resolved.

    [Europe-1] Object Storage

    Started March 12, 2026 at 1:24 PM UTC · 5h 5m

    IssuesMinor incident
    Affected components
    EUROPE-1: Managed Object Storage
    1. March 12, 2026 at 1:24 PM UTCinvestigating

      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. March 12, 2026 at 4:36 PM UTCmonitoring

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

    3. March 12, 2026 at 6:29 PM UTCresolved

      This incident has been resolved.