What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

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

Updates (6)

Jul 31, 2026, 06:57 PM
Service Issue - Host Job Performance Degradation - Several Regions
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
Linode ↗
Jul 29, 2026, 12:27 PM
Service Issue - Host Job Performance Degradation - Several Regions
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.
Linode ↗
Jul 28, 2026, 10:51 PM
Service Issue - Host Job Performance Degradation - Several Regions
A fix has been implemented and we are monitoring the results.
Linode ↗
Jul 28, 2026, 08:17 PM
Service Issue - Host Job Performance Degradation - Several Regions
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.
Linode ↗
Jul 28, 2026, 07:27 PM
Service Issue - Host Job Performance Degradation - Several Regions
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.
Linode ↗
Jul 28, 2026, 06:14 PM
Service Issue - Host Job Performance Degradation - Several Regions
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.
Linode ↗

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.