Minor impactResolvedCloud

Linode incident: Service Issue - Block Storage Newark, US

Linode reported this minor-impact incident on its official status page on Jun 3, 2026, 08:58 UTC. It was resolved after 1d.

Right now Linode is operational. Live Linode status →

🔔 Get alerted when Linode has issuesFree · email alerts · no credit card
Jun 3, 2026, 08:58 UTC
started
Jun 4, 2026, 09:11 UTC
resolved
1d
duration
Minor
impact

Affected components

  • US-East (Newark) Block Storage
  1. postmortemJun 4, 2026, 12:55 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.

  2. resolvedJun 4, 2026, 09:11 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

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

  4. investigatingJun 3, 2026, 12:55 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.

  5. monitoringJun 3, 2026, 11:25 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

  6. investigatingJun 3, 2026, 10:53 UTC

    We are continuing to investigate this issue.

  7. investigatingJun 3, 2026, 08:58 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Linode's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Linode have incidents?

Linode reported 10 incidents in the last 90 days. A typical incident lasted 2h 15m. See Linode's uptime and incident history

Linode incident on Jun 3, 2026: Service Issue - Block Storage Newark, US · APIStatus.watch