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 apologize for any inconvenience caused.
Posted Aug 11, 2026 - 11:09 UTC
Monitoring
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 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.
Posted Aug 11, 2026 - 10:05 UTC
Update
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.
Posted Aug 11, 2026 - 09:48 UTC
Update
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: support@upcloud.com
Posted Aug 11, 2026 - 09:23 UTC
Identified
The issue has been identified, and we are working on fixing it. It affects all new deployments in all zones.
Posted Aug 11, 2026 - 09:12 UTC
This incident affected: AU-SYD1 - Australia (AU-SYD1: Cloud Servers), DE-FRA1 - Germany (DE-FRA1: Cloud Servers), ES-MAD1 - Spain (ES-MAD1: Cloud Servers), FI-HEL1 - Finland (FI-HEL1: Cloud Servers), FI-HEL2 - Finland (FI-HEL2: Cloud Servers), NL-AMS1 - Netherlands (NL-AMS1: Cloud Servers), PL-WAW1 - Poland (PL-WAW1: Cloud Servers), SG-SIN1 - Singapore (SG-SIN1: Cloud Servers), UK-LON1 - United Kingdom (UK-LON1: Cloud Servers), US-CHI1 - USA (US:CHI1: Cloud Servers), US-NYC1 - USA (US-NYC1: Cloud Servers), US-SJO1 - USA (US-SJO1: Cloud Servers), SE-STO1 - Sweden (SE-STO1: Cloud Servers), DK-CPH1 - Denmark (DK-CPH1: Cloud Servers), and NO-SVG1 - Norway (NO-SVG1: Cloud Servers).