All Systems Operational
UpCloud Control Panel Operational
API Operational
DE-FRA1: Network Connections Operational
DE-FRA1: Virtualization Hosts Operational
DE-FRA1: Storage Backends Operational
FI-HEL1: Network Connections Operational
FI-HEL1: Virtualization Hosts Operational
FI-HEL1: Storage Backends Operational
FI-HEL2: Network Connections Operational
FI-HEL2: Virtualization Hosts Operational
FI-HEL2: Storage Backends Operational
NL-AMS1: Network Connections Operational
NL-AMS1: Virtualization Hosts Operational
NL-AMS1: Storage Backends Operational
SG-SIN1: Network Connections Operational
SG-SIN1: Virtualization Hosts Operational
SG-SIN1: Storage Backends Operational
UK-LON1: Network Connections Operational
UK-LON1: Virtualization Hosts Operational
UK-LON1: Storage Backends Operational
US-CHI1: Network Connections Operational
US-CHI1: Virtualization Hosts Operational
US-CHI1: Storage Backends Operational
US-SJO1: Network Connections Operational
US-SJO1: Virtualization Hosts Operational
US-SJO1: Storage Backends Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
[SG-SIN1]: Network maintenance Apr 22, 19:00-20:00 UTC
We will be performing network maintenance in the SG-SIN1 data center between 2019-04-23 19:00 UTC and 2019-04-23 20:00 UTC. The maintenance might cause a short loss of network connectivity for 1-2 minutes but no other disruptions are expected.
Posted on Apr 16, 14:10 UTC
Past Incidents
Apr 18, 2019

No incidents reported today.

Apr 17, 2019

No incidents reported.

Apr 16, 2019

No incidents reported.

Apr 15, 2019

No incidents reported.

Apr 14, 2019

No incidents reported.

Apr 13, 2019

No incidents reported.

Apr 12, 2019

No incidents reported.

Apr 11, 2019
Postmortem - Read details
Apr 11, 09:08 UTC
Resolved - All affected cloud servers have been brought back online. We sincerely apologise for the long recovery period and impact this has had on our users. Please reach out to support if you have any further questions.

We will be updating users with a post mortem on the incident.
Apr 11, 03:42 UTC
Update - We have brought back 95% of the affected cloud servers in FI-HEL1 and continuing work on the remaining, do reach out to support if you have any questions.
Apr 11, 02:35 UTC
Update - API is fully operational now.
We are continuing to roll out fixes for FI-HEL1, do reach out to support if you have any questions.
Apr 11, 01:01 UTC
Update - We brought back into operational status almost all of the affected cloud servers in US-SJO1. In total, we have recovered almost 40% of affected cloud servers in both locations. We understand the significant impact this has for our users and are doing our utmost to bring back all cloud servers as soon as possible.

If cloud servers which are operational (green status) in the control panel continue to face issues, we advice our users to log in through VNC or console access to resolve any potential OS-level problems due to the sudden error state received.

We will continue to communicate the progress here.
Apr 10, 21:09 UTC
Update - We are progressing with the recovery efforts. Many of the affected cloud servers have already been restarted. We continue relentlessly with the work and will keep you updated here. You are always welcome to reach out to our support in case you require assistance.
Apr 10, 19:37 UTC
Identified - The root cause has been identified and we are working to get the affected cloud servers online.

To make sure we get all affected cloud servers back online as soon as possible, we are required to restart the affected host machines. This might in some cases also affect operational cloud servers to speed up recovery of the infrastructure.
Apr 10, 18:49 UTC
Update - We are still working on the issue. Affected customer servers in FI-HEL1 and US-SJO1 will be restarted and returned to running state.
Apr 10, 17:37 UTC
Update - The incident has caused some VMs to stop temporarily. We are working to restore these in working condition.
Apr 10, 16:54 UTC
Monitoring - We are aware of and currently working on fixing issues with API and deployments in all zones. We will update as soon as resolved.
Apr 10, 16:42 UTC
Apr 9, 2019

No incidents reported.

Apr 8, 2019
Resolved - This incident has been resolved.
Apr 8, 04:43 UTC
Identified - The issue has been identified; memory module failure and a fix is being implemented.
Apr 8, 04:27 UTC
Apr 7, 2019

No incidents reported.

Apr 6, 2019

No incidents reported.

Apr 5, 2019

No incidents reported.

Apr 4, 2019

No incidents reported.