Linode experienced a minor incident on June 3, 2026 affecting US-East (Newark) Block Storage, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 03, 2026, 08:58 AM UTC
Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.
- investigating Jun 03, 2026, 10:53 AM UTC
We are continuing to investigate this issue.
- monitoring Jun 03, 2026, 11:25 AM UTC
At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
- investigating Jun 03, 2026, 12:55 PM UTC
Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.
- monitoring Jun 03, 2026, 03:44 PM UTC
At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
- resolved Jun 04, 2026, 09:11 AM UTC
We haven’t observed any additional issues with the Block Storage service in Newark, US, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
- postmortem Jun 04, 2026, 12:55 PM UTC
Between 22:50 UTC on June 2, 2026 and 19:00 UTC on June 3, 2026, some customers experienced intermittent performance degradation and long access times when interacting with the Compute Block Storage cluster in Newark, US. During this period, intermittent component instability triggered intensive background recovery operations. This elevated system load resulted in a temporary degradation of data redundancy, higher read/write latency, and reduced throughput for the affected volumes. To mitigate the impact, Akamai successfully restored the affected storage drives to operation, stabilizing the cluster and eliminating active customer impact. Following this, additional actions aim to fully restore standard system redundancy. 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.