Linode Status

Current Status
Service Issue - Block Storage
Incident Report for Linode
Postmortem

At approximately 22:30 UTC on June 21, 2024, Akamai Compute Support began receiving reports of issues with Block Storage creations, modifications, and deletions.

It was identified at approximately 02:00 UTC on June 22, 2024 that a release involving adding IPv6 addressing to DNS resolution caused a networking issue regarding the Block Storage service.

To mitigate the issue, and return services to normal operation, a rollback of the release was initiated. The rollback successfully resolved the networking issue by 02:50 UTC on June 22, 2024.

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 Jun 26, 2024 - 04:05 UTC

Resolved
We haven’t observed any additional issues with the Block Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Posted Jun 22, 2024 - 04:39 UTC
Monitoring
At this time we have been able to correct the issues affecting the Block Storage service. Investigation showed that the issue was caused by a planned release. We have reverted the release to mitigate the issue. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Posted Jun 22, 2024 - 02:50 UTC
Identified
Our team has identified the issue affecting the Block Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Posted Jun 22, 2024 - 02:36 UTC
Update
We are continuing to investigate this issue.
Posted Jun 22, 2024 - 02:13 UTC
Investigating
Our team is investigating an issue affecting the Block Storage service where customer may be unable to create new or modify Block Storage Volumes. We will share additional updates as we have more information.
Posted Jun 22, 2024 - 01:44 UTC
This incident affected: Block Storage (US-East (Newark) Block Storage, US-Central (Dallas) Block Storage, US-West (Fremont) Block Storage, US-Southeast (Atlanta) Block Storage, US-IAD (Washington) Block Storage, US-ORD (Chicago) Block Storage, CA-Central (Toronto) Block Storage, EU-West (London) Block Storage, EU-Central (Frankfurt) Block Storage, FR-PAR (Paris) Block Storage, AP-South (Singapore) Block Storage, AP-Northeast-2 (Tokyo 2) Block Storage, AP-West (Mumbai) Block Storage, AP-Southeast (Sydney) Block Storage, SE-STO (Stockholm) Block Storage, US-SEA (Seattle) Block Storage, JP-OSA (Osaka) Block Storage, IN-MAA (Chennai) Block Storage).