Companies / Linode (Akamai) / incidents

Linode (Akamai): Service Issue - Host Job Performance Degradation - Several Regions

Affected components: Block Storage - US-IAD (Washington) Block StorageUS-IAD (Washington) Block StorageBlock Storage - BR-GRU (São Paulo) Block StorageBR-GRU (São Paulo) Block StorageBlock Storage - DE-FRA-2 (Frankfurt 2) Block StorageDE-FRA-2 (Frankfurt 2) Block StorageBlock Storage - SE-STO (Stockholm) Block StorageSE-STO (Stockholm) Block StorageBlock Storage - ES-MAD (Madrid) Block StorageES-MAD (Madrid) Block StorageBlock Storage - FR-PAR (Paris) Block StorageFR-PAR (Paris) Block StorageBlock Storage - US-SEA (Seattle) Block StorageUS-SEA (Seattle) Block StorageAP-South (Singapore) Block StorageBlock Storage - AP-South (Singapore) Block StorageBlock Storage - US-Southeast (Atlanta) Block StorageUS-Southeast (Atlanta) Block StorageAU-MEL (Melbourne) Block StorageBlock Storage - AU-MEL (Melbourne) Block StorageBlock Storage - IT-MIL (Milan) Block StorageIT-MIL (Milan) Block StorageBlock Storage - EU-West (London) Block StorageEU-West (London) Block StorageBlock Storage - US-West (Fremont) Block StorageUS-West (Fremont) Block StorageBlock Storage - EU-Central (Frankfurt) Block StorageEU-Central (Frankfurt) Block StorageBlock Storage - US-Central (Dallas) Block StorageUS-Central (Dallas) Block StorageAP-Northeast-2 (Tokyo 2) Block StorageBlock Storage - AP-Northeast-2 (Tokyo 2) Block StorageBlock Storage - JP-TYO-3 (Tokyo 3) Block StorageJP-TYO-3 (Tokyo 3) Block StorageBlock Storage - JP-OSA (Osaka) Block StorageJP-OSA (Osaka) Block StorageBlock Storage - GB-LON (London 2) Block StorageGB-LON (London 2) Block StorageBlock Storage - IN-MAA (Chennai) Block StorageIN-MAA (Chennai) Block StorageBlock Storage - NL-AMS (Amsterdam) Block StorageNL-AMS (Amsterdam) Block StorageBlock Storage - US-LAX (Los Angeles) Block StorageUS-LAX (Los Angeles) Block StorageBlock Storage - ID-CGK (Jakarta) Block StorageID-CGK (Jakarta) Block StorageAP-West (Mumbai) Block StorageBlock Storage - AP-West (Mumbai) Block StorageBlock Storage - US-MIA (Miami) Block StorageUS-MIA (Miami) Block StorageBlock Storage - SG-SIN-2 (Singapore 2) Block StorageSG-SIN-2 (Singapore 2) Block StorageBlock Storage - US-ORD (Chicago) Block StorageUS-ORD (Chicago) Block StorageBlock Storage - IN-BOM-2 (Mumbai 2) Block StorageIN-BOM-2 (Mumbai 2) Block StorageAP-Southeast (Sydney) Block StorageBlock Storage - AP-Southeast (Sydney) Block StorageBlock Storage - CA-Central (Toronto) Block StorageCA-Central (Toronto) Block StorageBlock Storage - US-East (Newark) Block StorageUS-East (Newark) Block Storage

Timeline of updates

1. investigating2026-07-28 18:14 UTC

   Our team is investigating an issue affecting the Block Storage service in several data center regions. This issue largely impacts attaching and detaching Block Storage volumes. During this time, users may experience volume attach/detach hangs, timeouts and errors with this service. We will share additional updates as we have more information.

2. identified2026-07-28 19:27 UTC

   Our team has identified the issue affecting the Block Storage service in our data centers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

3. identified2026-07-28 20:17 UTC

   We would like to update that after additional investigation, the impact would manifest in delayed and sometimes failed host jobs, which could include many different actions on Linodes and not only impacting attaching and detaching Block Storage volumes as we mentioned in our initial update, we have updated the title to reflect the updated impact. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

4. monitoring2026-07-28 22:51 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved2026-07-29 12:27 UTC

   We haven’t observed any additional host jobs performance degradation issues, 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.

6. postmortem2026-07-31 18:57 UTC

   On 27 July 2026 at 3:30 UTC, Akamai observed an increase in errors when connecting to the Linode hosting database, primarily affecting Block Storage volume attachments. This resulted in host job failures and limited customer impact, with some users experiencing error messages and interrupted workflows. Elevated timeout rates were noted in logs for certain data center locations, coinciding with the incremental rollout of a new feature flag. Initial investigation revealed intermittent packet drops from the database proxy to client hosts during the TLS handshake. The current theory suggests that a DDoS-protection limit related to path MTU packet too big ICMP messages was reached. When the proxy sent TCP packets with a large MTU, the expected ICMP messages were dropped by Dallas gateway routers due to exceeding the configured allowable rate. This caused database proxy TCP connections to timeout to Compute Hosts. The issue was triggered by the enablement of the new feature flag, which changed the routing path and removed MTU clamping before packets reached the gateways. To mitigate the issue, Akamai rolled back the recent network change across affected Compute sites, starting at 20:50 UTC. As of 22:57 UTC, the rate of service restarts returned to pre-incident levels. Akamai is also planning a change to increase the allowable threshold for packet too big ICMP messages. 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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Linode (Akamai) profile · Recent Linode (Akamai) incidents · Markdown · JSON