Linode deployments and Block Storage attachment failing in 11 data centers

We have not identified any further issues with the affected services in these regions and will now mark this incident as resolved. If you continue to experience problems, please open a Support ticket for assistance.

We continue to work toward implementing a fix. In the meantime, affected customers may be successful in deploying a Linode or attaching a Block Storage volume to an existing Linode by trying the operation again.

Our team has identified the issue affecting deployments and Block Storage attachments and is working to implement a fix. We will update again tomorrow (1 November), or as progress is made.

We are continuing to investigate this issue. The appropriate subject matter experts are engaged, should you face issues deploying VMs or try to attach storage to already existing ones across those 11 Data Centers, you may be able to deploy by trying again. We will continue to provide updates as progress is made, until we have a clearer picture about the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.

We are continuing to investigate this issue. The appropriate subject matter experts are engaged, should you face issues deploying Linodes or try to attach storage to already existing ones across those 11 Data Centers, you may be able to deploy by trying again. We will continue to provide updates as progress is made, until we have a clearer picture about the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.

We have identified an issue which may prevent the deployment of new Linodes across 11 data centers (Paris, 2 Frankfurt locations, Mumbai, Atlanta, Newark, Chicago, Osaka, Seattle, 2 Singapore locations) or attach storage to already existing ones. We are actively working on creating the action plan to mitigate this issue and will provide another update within the next 60 minutes.