Cloud IaaS (OpenStack)

Service status history for the last 90 days
Dunsfold, Surrey, UK
Reading, Berkshire, UK

IaaS control plane degraded  degraded service

Wed 23 Jan 2019 7 a.m. GMT - Wed 23 Jan 2019 7:40 a.m. GMT (Resolved)
Affected services:
  • Cloud IaaS (OpenStack) Reading: The IaaS Control Plane operating in degraded node. Some infrastructure change actions may fail. Compute Plane not affected.

We have been alerted to an issue with Openstack in our Reading datacentre. Some services may be unavailable. We are investigating this as a matter of urgency.

Update: 23 Jan 2019, 7:37 a.m.

Service has now been fully restored.

Disruption to Openstack  degraded service

Tue 22 Jan 2019 10 p.m. GMT - Wed 23 Jan 2019 12:40 a.m. GMT (Resolved)
Affected services:
  • Cloud IaaS (OpenStack) Dunsfold: The IaaS Control Plane operating in degraded node. Some infrastructure change actions may fail. Compute Plane not affected.

We have been alerted to an issue with Openstack in our Dunsfold datacentre. Some services may be unavailable. We are investigating this as a matter of urgency.

Update: 23 Jan 2019, 1:03 a.m.

Service has now been fully restored.

Disruption to Storage Services  degraded service

Sun 20 Jan 2019 1:40 p.m. GMT - Tue 22 Jan 2019 12:53 a.m. GMT (Resolved)
Affected services:
  • Cloud VPS Reading
  • Cloud IaaS (OpenStack) Reading

We have been alerted to an issue with some of our storage services. This is currently affecting some customers in our Reading datacentre. Customers are experiencing issues with storage within OpenStack and Cloud VPS servers with additional block storage.

We are investigating this as a matter of urgency.

Update: 20 Jan 2019, 3:01 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 4:07 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 4:34 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 5:38 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 6:10 p.m.

We believe we have identified the fault in the cluster however service degradation continues while the cluster recovers

Update: 20 Jan 2019, 6:50 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 7:27 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 7:57 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 8:55 p.m.

We are continuing to investigate this issue but have no further update at this time

Update: 20 Jan 2019, 9:37 p.m.

We have now identified and corrected the underlying issue of this incident.
We expect IaaS Storage and Cloud VPS servers with additional block storage performance and functionality to be restored soon.

Update: 20 Jan 2019, 10:22 p.m.

We have now identified and corrected the underlying issue of this incident.
We expect IaaS Storage and Cloud VPS servers with additional block storage performance and functionality to be restored soon.

Update: 21 Jan 2019, 7:12 a.m.

We have now identified and corrected the underlying issue of this incident.
We expect IaaS Storage and Cloud VPS servers with additional block storage performance and functionality to be restored soon.

Update: 21 Jan 2019, 8:17 a.m.

Functionality has now been restored to our Cloud IaaS platform and almost all Cloud VPS customers.

Update: 21 Jan 2019, 11:54 a.m.

We are aware of continuing issues relating to the storage cluster. We are continuing to investigate but we advise customers with block storage in Reading do not reboot their Cloud VPS's at this time.

Update: 21 Jan 2019, 3:25 p.m.

We have now identified the root cause and normal service is now restored for the majority of customers. We are working through the outstanding related incidents that are in some cases preventing VPS from booting.

Update: 22 Jan 2019, 12:52 a.m.

We believe block storage issues are now resolved for all customers. Customers are advised to log a support ticket if they are still experiencing problems.