We will be performing network maintenance in the Amsterdam data center on the 24th of June 2026, 20:00 UTC - 25th of June 2026, 04:00 UTC (24th of June 2026, 22:00 CEST - 25th of June 2026, 06:00 CEST).
The maintenance might cause network connectivity to be slow for several minutes, but no other disruptions are expected.
If you have any questions or concerns regarding this maintenance, please reach out to us via 24/7 live chat or by email (support@upcloud.com). Posted on
May 25, 2026 - 08:34 UTC
We will be performing network maintenance in the Amsterdam data center on the 25th of June 2026, 20:00 UTC - 26th of June 2026, 04:00 UTC (25th of June 2026, 22:00 CEST - 26th of June 2026, 06:00 CEST).
The maintenance might cause network connectivity to be slow for several minutes, but no other disruptions are expected.
If you have any questions or concerns regarding this maintenance, please reach out to us via 24/7 live chat or by email (support@upcloud.com). Posted on
May 25, 2026 - 08:34 UTC
Completed -
The scheduled maintenance has been completed.
Jun 9, 16:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 9, 12:00 UTC
Scheduled -
We will be performing network maintenance in the Sydney data center on the 9th of June 2026, 12:00 - 16:00UTC (9th of June 2026, 22:00 - 10th of June 2026, 02:00 AEST).
The maintenance might cause network connectivity to be slow for several minutes, but no other disruptions are expected.
If you have any questions or concerns regarding this maintenance, please reach out to us via 24/7 live chat or by email (support@upcloud.com).
May 25, 08:23 UTC
Resolved -
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 support@upcloud.com.
Thank you for your patience and we apologize for any inconvenience caused.
Jun 5, 19:11 UTC
Monitoring -
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 support@upcloud.com.
We apologise for the incident.
Jun 5, 16:10 UTC
Identified -
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: support@upcloud.com or Live Chat in our control panel https://hub.upcloud.com
Jun 5, 15:32 UTC
Investigating -
We are currently investigating this issue.
Jun 5, 14:58 UTC
Identified -
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.
Jun 5, 14:50 UTC