Service Issue - Block Storage Newark, US

Summary

Service Issue - Block Storage Newark, US

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.

• Started

  Jun 3, 2026 · 8:58 AM

• Resolved

  Jun 4, 2026 · 9:11 AM

• Duration

  1d 13m

• Severity

  Minor

• ◐

  Investigating

  Jun 3 · 8:58 AM Linode

  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 3 · 10:53 AM Linode

  We are continuing to investigate this issue.

• ◉

  Monitoring

  Jun 3 · 11:25 AM Linode

  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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

• ◐

  Investigating

  Jun 3 · 12:55 PM Linode

  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 3 · 3:44 PM Linode

  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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

• ✓

  Resolved

  Jun 4 · 9:11 AM Linode

  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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

• ✓

  Postmortem

  Jun 4 · 12:55 PM Linode

  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.