Linode Status

Current Status
Update - We are continuing to monitor for any further issues.
Aug 26, 2025 - 18:00 UTC
Monitoring - At this time we have been able to correct the issue affecting the Cloud Manager, API, and CLI. We will be monitoring this to ensure that the services remain stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.
Aug 26, 2025 - 17:48 UTC
Update - We are continuing to work on a fix for this issue.
Aug 26, 2025 - 17:31 UTC
Update - The Linode API and OBJ bucket operations have been restored as of ~16:13 UTC. A subset of API requests are currently being queued while we continue to resolve the underlying service issue. At this time, we do not recommend performing any operations on running Compute instances, including power off and reboot operations, as these requests may be delayed or not successful.

Akamai Cloud Support ticket functionality has also been restored, and you may open a Support ticket if you have any issues or questions.

Aug 26, 2025 - 17:07 UTC
Identified - Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix and have begun to see early signs of success. While we do not have an ETA for full mitigation of this issue, the Cloud Manager and Linode API are now partially restored for some customers, and we are continuing to work towards full restoration of these services. We will continue to provide updates here as this incident develops.
Aug 26, 2025 - 16:17 UTC
Investigating - Our team is investigating an emerging service issue affecting Linode Cloud Manager, API, and CLI in all regions. We will share additional updates as we have more information.
Aug 26, 2025 - 15:06 UTC
Linode.com Operational
Linode Manager and API Operational
Hosted DNS Service Operational
Longview Operational
Managed Databases Operational
Regions Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
US-IAD (Washington) Operational
US-ORD (Chicago) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
FR-PAR (Paris) Operational
AP-South (Singapore) Operational
AP-Northeast-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) Operational
SE-STO (Stockholm) Operational
US-SEA (Seattle) Operational
IT-MIL (Milan) Operational
JP-OSA (Osaka) Operational
IN-MAA (Chennai) Operational
ID-CGK (Jakarta) Operational
BR-GRU (São Paulo) Operational
NL-AMS (Amsterdam) Operational
US-MIA (Miami) Operational
US-LAX (Los Angeles) Operational
ES-MAD (Madrid) Operational
AU-MEL (Melbourne) Operational
GB-LON (London 2) Operational
IN-BOM-2 (Mumbai 2) Operational
SG-SIN-2 (Singapore 2) Operational
DE-FRA-2 (Frankfurt 2) Operational
JP-TYO-3 (Tokyo 3) Operational
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) Operational
Backups Operational
US-East (Newark) Backups Operational
US-Central (Dallas) Backups Operational
US-West (Fremont) Backups Operational
US-Southeast (Atlanta) Backups Operational
US-IAD (Washington) Backups Operational
US-ORD (Chicago) Backups Operational
CA-Central (Toronto) Backups Operational
EU-West (London) Backups Operational
EU-Central (Frankfurt) Backups Operational
FR-PAR (Paris) Backups Operational
AP-South (Singapore) Backups Operational
AP-Northeast-2 (Tokyo 2) Backups Operational
AP-West (Mumbai) Backups Operational
AP-Southeast (Sydney) Backups Operational
SE-STO (Stockholm) Backups Operational
US-SEA (Seattle) Backups Operational
JP-OSA (Osaka) Backups Operational
IN-MAA (Chennai) Backups Operational
BR-GRU (São Paulo) Backups Operational
NL-AMS (Amsterdam) Backups Operational
ES-MAD (Madrid) Backups Operational
IT-MIL (Milan) Backups Operational
US-MIA (Miami) Backups Operational
ID-CGK (Jakarta) Backups Operational
US-LAX (Los Angeles) Backups Operational
GB-LON (London 2) Backups Operational
AU-MEL (Melbourne) Backups Operational
IN-BOM-2 (Mumbai 2) Backups Operational
DE-FRA-2 (Frankfurt 2) Backups Operational
SG-SIN-2 (Singapore 2) Backups Operational
JP-TYO-3 (Tokyo) Backups Operational
Block Storage Operational
US-East (Newark) Block Storage Operational
US-Central (Dallas) Block Storage Operational
US-West (Fremont) Block Storage Operational
US-Southeast (Atlanta) Block Storage Operational
US-IAD (Washington) Block Storage Operational
US-ORD (Chicago) Block Storage Operational
CA-Central (Toronto) Block Storage Operational
EU-West (London) Block Storage Operational
EU-Central (Frankfurt) Block Storage Operational
FR-PAR (Paris) Block Storage Operational
AP-South (Singapore) Block Storage Operational
AP-Northeast-2 (Tokyo 2) Block Storage Operational
AP-West (Mumbai) Block Storage Operational
AP-Southeast (Sydney) Block Storage Operational
SE-STO (Stockholm) Block Storage Operational
US-SEA (Seattle) Block Storage Operational
JP-OSA (Osaka) Block Storage Operational
IN-MAA (Chennai) Block Storage Operational
BR-GRU (São Paulo) Block Storage Operational
NL-AMS (Amsterdam) Block Storage Operational
ES-MAD (Madrid) Block Storage Operational
IT-MIL (Milan) Block Storage Operational
US-MIA (Miami) Block Storage Operational
ID-CGK (Jakarta) Block Storage Operational
US-LAX (Los Angeles) Block Storage Operational
GB-LON (London 2) Block Storage Operational
AU-MEL (Melbourne) Block Storage Operational
IN-BOM-2 (Mumbai 2) Block Storage Operational
DE-FRA-2 (Frankfurt 2) Block Storage Operational
SG-SIN-2 (Singapore 2) Block Storage Operational
JP-TYO-3 (Tokyo 3) Block Storage Operational
NodeBalancers Operational
US-East (Newark) NodeBalancers Operational
US-Central (Dallas) NodeBalancers Operational
US-West (Fremont) NodeBalancers Operational
US-Southeast (Atlanta) NodeBalancers Operational
US-IAD (Washington) NodeBalancers Operational
US-ORD (Chicago) NodeBalancers Operational
CA-Central (Toronto) NodeBalancers Operational
EU-West (London) NodeBalancers Operational
EU-Central (Frankfurt) NodeBalancers Operational
FR-PAR (Paris) NodeBalancers Operational
AP-South (Singapore) NodeBalancers Operational
AP-Northeast-2 (Tokyo 2) NodeBalancers Operational
AP-West (Mumbai) NodeBalancers Operational
AP-Southeast (Sydney) NodeBalancers Operational
SE-STO (Stockholm) NodeBalancers Operational
US-SEA (Seattle) NodeBalancers Operational
JP-OSA (Osaka) NodeBalancers Operational
IN-MAA (Chennai) NodeBalancers Operational
BR-GRU (São Paulo) NodeBalancers Operational
NL-AMS (Amsterdam) NodeBalancers Operational
ES-MAD (Madrid) NodeBalancers Operational
IT-MIL (Milan) NodeBalancers Operational
US-MIA (Miami) NodeBalancers Operational
ID-CGK (Jakarta) NodeBalancers Operational
US-LAX (Los Angeles) NodeBalancers Operational
GB-LON (London 2) NodeBalancers Operational
AU-MEL (Melbourne) NodeBalancers Operational
IN-BOM-2 (Mumbai 2) NodeBalancers Operational
DE-FRA-2 (Frankfurt 2) NodeBalancers Operational
SG-SIN-2 (Singapore 2) NodeBalancers Operational
JP-TYO-3 (Tokyo 3) NodeBalancers Operational
Object Storage Operational
US-East (Newark) Object Storage Operational
US-Southeast (Atlanta) Object Storage Operational
US-IAD (Washington) Object Storage Operational
US-ORD (Chicago) Object Storage Operational
EU-Central (Frankfurt) Object Storage Operational
AP-South (Singapore) Object Storage Operational
FR-PAR (Paris) Object Storage Operational
SE-STO (Stockholm) Object Storage Operational
US-SEA (Seattle) Object Storage Operational
JP-OSA (Osaka) Object Storage Operational
IN-MAA (Chennai) Object Storage Operational
ID-CGK (Jakarta) Object Storage Operational
BR-GRU (Sao Paulo) Object Storage Operational
ES-MAD (Madrid) Object Storage Operational
GB-LON (London 2) Operational
AU-MEL (Melbourne) Operational
NL-AMS (Amsterdam) Object Storage Operational
IT-MIL (Milan) Object Storage Operational
US-MIA (Miami) Object Storage Operational
US-LAX (Los Angeles) Object Storage Operational
GB-LON (London 2) Object Storage Operational
AU-MEL (Melbourne) Object Storage Operational
IN-BOM-2 (Mumbai 2) Object Storage Operational
DE-FRA-2 (Frankfurt 2) Object Storage Operational
SG-SIN-2 (Singapore 2) Object Storage Operational
JP-TYO-3 (Tokyo 3) Object Storage Operational
Linode Kubernetes Engine Operational
US-East (Newark) Linode Kubernetes Engine Operational
US-Central (Dallas) Linode Kubernetes Engine Operational
US-West (Fremont) Linode Kubernetes Engine Operational
US-Southeast (Atlanta) Linode Kubernetes Engine Operational
US-IAD (Washington) Linode Kubernetes Engine Operational
US-ORD (Chicago) Linode Kubernetes Engine Operational
CA-Central (Toronto) Linode Kubernetes Engine Operational
EU-West (London) Linode Kubernetes Engine Operational
EU-Central (Frankfurt) Linode Kubernetes Engine Operational
FR-PAR (Paris) Linode Kubernetes Engine Operational
AP-South (Singapore) Linode Kubernetes Engine Operational
AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine Operational
AP-West (Mumbai) Linode Kubernetes Engine Operational
AP-Southeast (Sydney) Linode Kubernetes Engine Operational
SE-STO (Stockholm) Linode Kubernetes Engine Operational
US-SEA (Seattle) Linode Kubernetes Engine Operational
JP-OSA (Osaka) Linode Kubernetes Engine Operational
IN-MAA (Chennai) Linode Kubernetes Engine Operational
ID-CGK (Jakarta) Linode Kubernetes Engine Operational
BR-GRU (São Paulo) Linode Kubernetes Engine Operational
NL-AMS (Amsterdam) Linode Kubernetes Engine Operational
ES-MAD (Madrid) Linode Kubernetes Engine Operational
IT-MIL (Milan) Linode Kubernetes Engine Operational
US-MIA (Miami) Linode Kubernetes Engine Operational
US-LAX (Los Angeles) Linode Kubernetes Engine Operational
GB-LON (London 2) Linode Kubernetes Engine Operational
AU-MEL (Melbourne) Linode Kubernetes Engine Operational
IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine Operational
DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine Operational
SG-SIN-2 (Singapore 2) Linode Kubernetes Engine Operational
JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine Operational
Metadata Service Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
US-IAD (Washington) Operational
US-ORD (Chicago) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
FR-PAR (Paris) Operational
AP-South (Singapore) Operational
AP-Northeast-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) Operational
SE-STO (Stockholm) Operational
US-SEA (Seattle) Operational
IT-MIL (Milan) Operational
JP-OSA (Osaka) Operational
IN-MAA (Chennai) Operational
ID-CGK (Jakarta) Operational
BR-GRU (São Paulo) Operational
NL-AMS (Amsterdam) Operational
US-MIA (Miami) Operational
US-LAX (Los Angeles) Operational
ES-MAD (Madrid) Operational
AU-MEL (Melbourne) Operational
GB-LON (London 2) Operational
IN-BOM-2 (Mumbai 2) Operational
SG-SIN-2 (Singapore 2) Operational
DE-FRA-2 (Frankfurt 2) Operational
JP-TYO-3 (Tokyo 3) Operational
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Emergency Network Maintenance - AU-MEL (Melbourne, AU) Sep 3, 2025 18:00-22:00 UTC

We will be performing emergency network maintenance in our AU-MEL (Melbourne, AU) data center beginning on September 3, 2025 at 18:00 (UTC) until September 3, 2025 22:00 (UTC). Customers in this region may experience brief connectivity disruptions during this window.
Posted on Aug 22, 2025 - 20:46 UTC

Scheduled Network Maintenance(Cloud Firewall2) on US-IAD (Washington) Sep 4, 2025 04:00-10:00 UTC

We will perform network maintenance at the IAD3 data centers on September 4, 2025, from 04:00 to 10:00 UTC.
During this window, the Linode Cloud Firewall will be upgraded. Only Linodes using Cloud Firewalls will be impacted. There will be a brief disruption of connectivity and the underlying table tracking flows in the Cloud Firewall will be reset. Only very uncommon cases such as non-TCP unidirectional traffic flows may experience connection breakage. For normal bidirectional traffic flows, we expect a maximum of a few dropped packets in one direction after which active traffic flows will re-establish entries in the connection tracking table, and hence will be unaffected.

Posted on Aug 22, 2025 - 15:50 UTC

Emergency Network Maintenance - US-SEA (Seattle, WA) Sep 8, 2025 10:00-14:00 UTC

We will be performing emergency network maintenance in our US-SEA (Seattle, WA) data center beginning on September 8, 2025 at 10:00 (UTC) until September 8, 2025 14:00 (UTC). Customers in this region may experience brief connectivity disruptions during this window.
Posted on Aug 22, 2025 - 20:51 UTC

Emergency Network Maintenance - US-LAX (Los Angeles, CA) Sep 10, 2025 10:00-14:00 UTC

We will be performing emergency network maintenance in our US-LAX (Los Angeles, CA) data center beginning on September 10, 2025 at 10:00 (UTC) until September 10, 2025 14:00 (UTC). Customers in this region may experience brief connectivity disruptions during this window.
Posted on Aug 22, 2025 - 20:53 UTC

Emergency Network Maintenance - IN-MAA (Chennai, IN) Sep 11, 2025 22:00 - Sep 12, 2025 02:00 UTC

We will be performing emergency network maintenance in our IN-MAA (Chennai, IN) data center beginning on September 11, 2025 at 22:00 (UTC) until September 12, 2025 02:00 (UTC). Customers in this region may experience brief connectivity disruptions during this window.
Posted on Aug 22, 2025 - 20:55 UTC

Network Maintenance - IT-MIL (Milan, IT) Sep 16, 2025 03:00-07:00 UTC

We will be performing network maintenance in our IT-MIL (Milan, IT) data center beginning on September 16, 2025 at 03:00 (UTC) until September 16, 2025 07:00 (UTC). Customers in this region may experience brief connectivity disruptions during this window.
Posted on Sep 16, 2025 - 03:00 UTC

Network Maintenance - SE-STO (Stockholm, SE) Sep 17, 2025 03:00-07:00 UTC

Network Maintenance - SE-STO (Stockholm, SE)
We will be performing network maintenance in our SE-STO (Stockholm, SE) data center beginning on September 17, 2025 at 03:00 (UTC) until September 17, 2025 07:00 (UTC). Customers in this region may experience brief connectivity disruptions during this window.

Posted on Aug 22, 2025 - 21:03 UTC
Aug 26, 2025
Resolved - We haven’t observed any additional connectivity issues in our Madrid data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Aug 26, 20:53 UTC
Update - We are continuing to monitor for any further issues.
Aug 26, 19:54 UTC
Update - We are continuing to monitor for any further issues. Impact time was from 17:25 to 17:38 UTC, during which customers may have experienced performance degradation and traffic impact.
Aug 26, 19:02 UTC
Monitoring - Our team has identified an issue affecting connectivity in our Madrid data center, and we were been able to quickly implement a fix. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Aug 26, 18:15 UTC
Completed - The scheduled maintenance has been completed.
Aug 26, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 13:00 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 13:00 UTC and 15:00 UTC, August 26, 2025. During this window service should not be disrupted. We will update this status page if we encounter any unexpected issues.
Aug 6, 20:14 UTC
Postmortem - Read details
Aug 26, 03:25 UTC
Resolved - We haven’t observed any additional connectivity issues in our Madrid data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Aug 26, 02:14 UTC
Monitoring - We have identified a connectivity issue in our Madrid data center that resulted in intermittent packet loss from 22:42 to 23:56 UTC. Impact has been mitigated, and we will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Aug 26, 00:12 UTC
Aug 25, 2025

No incidents reported.

Aug 24, 2025

No incidents reported.

Aug 23, 2025

No incidents reported.

Aug 22, 2025
Resolved - We haven’t observed any additional issues with the Block Storage service in the Osaka region [OSA], and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Aug 22, 14:50 UTC
Monitoring - 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.
Aug 22, 11:13 UTC
Update - Our team continues investigating the issue affecting the Block Storage service in the Osaka region. We will share additional updates as we have more information.
Aug 22, 10:30 UTC
Investigating - Our team is investigating an emerging service issue affecting Blockstorage in the Osaka region [OSA]. We will share additional updates as we have more information.
Aug 22, 09:06 UTC
Aug 21, 2025
Completed - The scheduled maintenance has been completed.
Aug 21, 02:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 20, 14:00 UTC
Scheduled - We will be performing network maintenance at the following data centers on August 14, 2025, from 14:00 UTC to 23:00 UTC: -
EU-West (London), EU-Central (Frankfurt), FR-PAR (Paris), NL-AMS (Amsterdam), SE-STO (Stockholm), ES-MAD (Madrid), GB-LON (London 2), DE-FRA-2 (Frankfurt 2)

While we do not anticipate any impact, there may be brief connectivity disruptions during this window.

Jul 30, 07:51 UTC
Resolved - This incident has been resolved.
Aug 21, 01:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 21, 01:33 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 21, 01:27 UTC
Update - We are continuing to investigate this issue.
Aug 21, 00:51 UTC
Update - We are continuing to investigate this issue. We will share additional updates as we have more information.
Aug 21, 00:01 UTC
Investigating - Our team is investigating an emerging service issue affecting Object Storage in AP-South (Singapore). We will share additional updates as we have more information.
Aug 20, 23:06 UTC
Aug 20, 2025
Completed - The scheduled maintenance has been completed.
Aug 20, 17:50 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 20, 16:30 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center beginning 20 Aug 2025 16:30 (UTC) until 20 Aug 2025 20:30 (UTC). During this time, users with resources in the AP-West (Mumbai) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region
Aug 20, 06:05 UTC
Aug 19, 2025

No incidents reported.

Aug 18, 2025

No incidents reported.

Aug 17, 2025

No incidents reported.

Aug 16, 2025

No incidents reported.

Aug 15, 2025
Postmortem - Read details
Aug 22, 00:47 UTC
Resolved - This incident has been resolved.
Aug 15, 22:37 UTC
Identified - Between approximately 19:02 – 19:07 UTC, and then again between 19:20 – 20:04 UTC, we observed a period of connectivity issues in MAD2. The issue subsided after we took a border router out of service. No further network issues have been observed since the loss subsided around 20:04 UTC. We identified the issue and a fix is being implemented.
Aug 15, 21:19 UTC
Investigating - Our team is investigating an issue affecting connectivity in our ES-MAD (Madrid) data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.
Aug 15, 20:26 UTC
Aug 14, 2025

No incidents reported.

Aug 13, 2025
Postmortem - Read details
Aug 15, 16:20 UTC
Resolved - Our team investigated a service issue that affected the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users might have experienced issues when attempting to access these systems.
At this time we have been able to correct the issue affecting the Cloud Manager and API.
We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.

Aug 13, 16:35 UTC
Resolved - Between ~6:00 AM UTC and 6:17 AM UTC, Cloud Manager (cloud.linode.com) experienced slowness followed by 500 errors, with potential API impact. The issue was caused by high load on the database, which has since been resolved by switching to a backup instance and addressing problematic queries. All services are now operating normally.
if you are experiencing any current issues with cloud manager or require more information, please call us at +1-609-380-7100.

Aug 13, 07:21 UTC
Investigating - We are currently experiencing a database connectivity issue that is causing slowness on cloud.linode.com. Our teams are actively working to resolve it.
Aug 13, 06:20 UTC
Aug 12, 2025
Completed - The scheduled maintenance has been completed.
Aug 12, 18:53 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 12, 16:30 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center beginning 12 Aug 2025 16:30 (UTC) until 12 Aug 2025 20:30 (UTC). During this time, users with resources in the AP-West (Mumbai) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region
Aug 12, 13:04 UTC
Completed - The scheduled maintenance has been completed.
Aug 12, 06:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 12, 04:30 UTC
Scheduled - We will be performing scheduled maintenance on our Longview service, starting at 04:30 UTC on August 12th. The maintenance period is expected to last two hours ending 06:30 UTC, August 12th. During this period, graphs will operate in read-only mode and new updates to the graphs will be temporarily unavailable during the downtime.
Aug 11, 13:05 UTC