Linode Status

Current Status
Linode deployments and Block Storage attachment failing in 11 data centers
Incident Report for Linode
Postmortem

Between October 21st and 28th a change was deployed across Paris, Frankfurt, Mumbai, Atlanta, Newark, Chicago, Osaka, Seattle, and Singapore Data Centers that inadvertently caused deployment failures for customers in these regions.

Our team identified the cause of the issue to be a new Disk Scrubber version introduced on October 21st in Paris and on October 27th in the other 10 Data Centers. The Disk Scrubber cleans our host disk before a new Virtual Machine's storage is provisioned. The issue was not noticed until October 27th.

Due to a race condition, volumes were not always successfully cleaned causing the process to fail and preventing new VMs from being provisioned on the host.

In order to mitigate this issue, we switched the faulty Disk Scrubber to another build and manually cleaned the affected hosts.

To avoid this issue in the future, the faulty Disk Scrubber will be fixed and our scrub failure alerting improved. We will re-deploy the Disk Scrubber after rigorous testing.

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Posted Nov 12, 2024 - 18:12 UTC

Resolved
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.
Posted Nov 04, 2024 - 19:45 UTC
Update
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.
Posted Nov 01, 2024 - 17:28 UTC
Identified
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.
Posted Oct 31, 2024 - 21:58 UTC
Update
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.
Posted Oct 30, 2024 - 23:58 UTC
Update
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.
Posted Oct 30, 2024 - 20:45 UTC
Investigating
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.
Posted Oct 30, 2024 - 20:01 UTC
This incident affected: Regions (US-East (Newark), US-Southeast (Atlanta), US-ORD (Chicago), EU-Central (Frankfurt), FR-PAR (Paris), AP-South (Singapore), AP-West (Mumbai), US-SEA (Seattle), JP-OSA (Osaka), SG-SIN-2 (Singapore 2)).