City Network Status

Incident: Block Storage Region STO2 (limited)

2020-03-04 – 12:20 CET: This issue is solved as storage service have been stabilised the last 15 hours and all storage related work are done. 

2020-03-03 – 21:55 CET: The affected vms/instances have been rebooted. The load is stabilised  and we keep on monitoring and update. If there still are any issues, please contact support.

2020-03-03 – 20:40 CET: Load on one of the compute went up which might impact some vms/instances on that compute.We recommend to reboot the VMs if you see any I/O error. We are monitoring the computes and the situation. If there still are any issues, please contact support.

2020-03-03 – 12:45 CET:  Load have been low since last post 07:30 and we continue to monitor this issue over the day. As mentioned earlier VMs not working should be hard rebooted. If there still are any issues, please contact support.

2020-03-03 – 07:30 CET:  Due to increase load on some compute nodes are likely to have customer impact for instances/applications with disk I/O need. We recommend to reboot the VMs. If you still have any issue with your VM, please contact us at support@citycloud.com. We are still monitoring the situation and will update on new change.

2020-03-03 – 06:30 CET:CN Service Operations have received metrics indicating storage related disturbances in the Stockholm region. Currently technicians are looking into the situation.

2020-03-02 – 14:00 CET: After 12:15 the load stabilised at a low level. We are still monitoring the situation and will update on new change. If you still have any issue with your VM, please contact us at support@citycloud.com.

2020-03-02 – 11:45 CET: Technicians have now taken steps trying to lower the load situation and are watching the situation.

2020-03-02 – 10:45 CET: Load is still going up and down in the storage system and work is ongoing to mitigate this issue.

2020-03-02 – 10:00 CET: Affected compute nodes is fixed now and VMs on those should work. However, there is an general load issues ongoing and technicians are investigating.

2020-03-02 – 08:00 CET: The compute nodes affected by the storage disruption requires hard reboot as all attempts to solve it gracefully have failed.

2020-03-02 – 06:00 CET: Attempts to have the issue resolved on the three nodes in question have been unsuccessful so far.

2020-03-02 – 04:15 CET: System load across all compute nodes is back at normal levels, though three nodes still suffers from high system load. Those nodes are likely to have customer impact for instances/applications with disk I/O need.

2020-03-02 – 04:00 CET: CN Service Operations have received metrics indicating storage related disturbances in the Stockholm region.