View all products
Compute
Storage
Networking
Databases
Services
Solutions
Pricing
Library
Technical Resources
Community
Marketplace
What's New

Linode Status

← Current Status
Email Deliverability issues to Yahoo! addresses
Investigating - Our team is currently investigating an issue with email deliverability to Yahoo! addresses. Customers using Yahoo! email addresses on their accounts may be unable to receive One-Time Passcode messages when logging in, as well as Support ticket responses from our team. Customers using Yahoo! email addresses who are able to log into Cloud Manager are encouraged to temporarily update their user email to an alternate address. Customers using Yahoo! email addresses that are currently experiencing issues logging into Cloud Manager should call into our Support phone line:

- U.S. 855-454-6633
- Global +1-609-380-7100

We will provide updates here as they become available.
Aug 01, 2025 - 23:12 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

Scheduled Longview Maintenance - All Regions Aug 5, 2025 04:30-06:30 UTC

We will be performing scheduled maintenance on our Longview service, starting at 04:30 UTC on August 5th, and is expected to last two hours (until 06:30 UTC, August 5th). During this period, graphs will operate in read-only mode and new updates to the graphs will be temporarily unavailable during the downtime.
Posted on Aug 04, 2025 - 13:29 UTC

Scheduled Network Maintenance - US-IAD (Washington) Aug 12, 2025 04:00-12:00 UTC

Update - The scheduled network maintenance in our US-IAD (Washington) data center originally planned for 04:00 (UTC) until 12:00 (UTC) on Tuesday, August 5th has been delayed and will be performed from 04:00 (UTC) until 12:00 (UTC) on Tuesday, August 12th. Brief network outages and the possibility of live migrations for linodes are expected.
Jul 31, 2025 - 21:01 UTC
Scheduled - We will be performing a scheduled network maintenance in our US-IAD (Washington) data center from 04:00 (UTC) until 12:00 (UTC) on Tuesday, August 5th. Brief network outages and the possibility of live migrations for linodes are expected.
Jul 18, 2025 - 19:04 UTC

Scheduled Network Maintenance(Cloud Firewall2) - EMEA Region Aug 14, 2025 14:00-23:00 UTC

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.
Posted on Jul 30, 2025 - 07:51 UTC

Scheduled Network Maintenance(Cloud Firewall2) - AMER Region Aug 28, 2025 04:00-14:00 UTC

We will be performing network maintenance at the following data centers on August 28, 2025, from 04:00 UTC to 14:00 UTC: -
BR-GRU (São Paulo), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-East (Newark), CA-Central (Toronto), US-IAD (Washington), US-ORD (Chicago), US-SEA (Seattle), US-LAX (Los Angeles).
While we do not anticipate any impact, there may be brief connectivity disruptions during this window.
Posted on Jul 30, 2025 - 09:31 UTC
Aug 4, 2025

No incidents reported today.

Aug 3, 2025

No incidents reported.

Aug 2, 2025

No incidents reported.

Aug 1, 2025
Service Issue - All Services - US-EAST (Newark)
Resolved - We haven’t observed any additional issues with the Newark, NJ (us-east) region, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Aug 1, 15:39 UTC
Monitoring - At this time we have been able to correct the issues affecting all services in our Newark, NJ (us-east) data center. This included Linode Kubernetes Engine (LKE), Linode compute instances, Block and Object Storage, and additional services. Some downstream impact was observed in other data centers due to interdependencies with Newark, and those services have also been fully restored. We will be monitoring this closely to ensure continued stability. If you continue to experience problems, please open a Support ticket for assistance.
Jul 28, 16:42 UTC
Update - We are continuing to work on restoring full functionality to Linode Kubernetes Engine (LKE) and Linode compute instances in our Newark (us-east) data center. Our teams are actively engaged in recovery efforts and closely monitoring progress.

We appreciate your continued patience as we work to fully resolve this incident.
Jul 28, 14:51 UTC
Update - Mitigation efforts are continuing with our subject matter experts actively working to restore the remaining services. We will continue to provide updates as progress is made.
Jul 28, 10:50 UTC
Update - Mitigation efforts are continuing with our subject matter experts actively working to restore the remaining services. We will continue to provide updates as progress is made.
Jul 28, 08:50 UTC
Update - Mitigation efforts are continuing with our subject matter experts actively working to restore the remaining services. We will continue to provide updates as progress is made.
Jul 28, 05:16 UTC
Update - Our SMEs are working towards bringing up the remaining services online. The situation is improving. We will provide further updates as further progress is made.
Jul 28, 02:29 UTC
Update - Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.
Jul 27, 23:54 UTC
Update - Our SMEs continue to work bringing our services back online. We have been able to correct the issues impacting LKE in our Dallas, Fremont, Sydney, Tokyo 2, Toronto and Washington data centers. Issues impacting Block Storage, Object Storage, and Nodebalancers in Newark were also restored per previous updates . We are still working to mitigate impact to LKE and individual Linode instances in Newark and will provide updates as progress is made.
Jul 27, 22:42 UTC
Update - At this time we have been able to correct the issues affecting Nodebalancer as of 19:00 UTC. We will be monitoring this to ensure that it remains stable.
Efforts to bring our services back continue, we will provide updates as progress is made.
Jul 27, 21:36 UTC
Update - Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.
Jul 27, 21:00 UTC
Update - We are continuing to work on a fix for this issue.
Jul 27, 19:56 UTC
Update - We are continuing to work on a fix for this issue.
Jul 27, 19:56 UTC
Update - At this time we have been able to correct the issues affecting LKE in our Dallas, Fremont, Sydney, Tokyo 2, Toronto and Washington data centers. Issues in Newark are still being worked at this moment.
We can also confirm Block Storage has recovered as of 14:13 UTC, as well as Object Storage at 17:52 UTC. We will be monitoring this to ensure that it remains stable.
Efforts to bring our services back continue, we will provide updates as progress is made.
Jul 27, 19:16 UTC
Update - Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.
Jul 27, 17:37 UTC
Update - In regards of the LKE impact caused in the identified data centers due to this issue, customers would have inability to provision new clusters and degraded ability to recover from control plane failures for already running clusters while this issue is active. Autoscaling of existing node pools is not impacted except for Newark data center. We continue to work bringing our services back online, and we will provide an update as soon as progress is made.
Jul 27, 16:16 UTC
Update - Impact to LKE services has been confirmed to have also extended to our data centers in Dallas, Fremont, Sydney, Tokyo 2, Toronto and Washington due to the interaction with our data center in Newark. We continue to work bringing our services back online, and we will provide an update as soon as progress is made.
Jul 27, 14:24 UTC
Identified - Our team has identified the issue affecting connectivity in our US-EAST (Newark) data center. The issue is related to heating/cooling complications in the data center due to a power outage . The power outage has been fixed and we are working quickly to bring our services back online, and we will provide an update as soon as the solution is in place.
Jul 27, 13:59 UTC
Update - Our team continues investigating an issue affecting connectivity in our US-EAST (Newark) data center. During this time, users may experience unavailability issues for all services deployed in this data center. We will share additional updates as we have more information.
Jul 27, 13:29 UTC
Update - Our team is investigating an issue affecting connectivity in our US-EAST (Newark) data center. During this time, users may experience unavailability issues for all services deployed in this data center. We will share additional updates as we have more information.
Jul 27, 12:34 UTC
Investigating - Our team is investigating an emerging service issue affecting All Services in US-EAST (Newark). We will share additional updates as we have more information.
Jul 27, 10:08 UTC
Jul 31, 2025
Scheduled Network Maintenance(Cloud Firewall2) - APAC Region
Completed - The scheduled maintenance has been completed.
Jul 31, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 31, 12:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jul 29, 11:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jul 29, 10:57 UTC
Scheduled - We will be performing network maintenance at the following data centers on July 31, 2025, from 12:00 UTC to 21:00 UTC: -
AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-Southeast (Sydney), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta), AU-MEL (Melbourne), IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), JP-TYO-3 (Tokyo 3) .

While we do not anticipate any impact, there may be brief connectivity disruptions during this window.
Jul 18, 09:16 UTC
Emergency Network Maintenance - AP-West (Mumbai)
Completed - The scheduled maintenance has been completed.
Jul 31, 14:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 31, 10:30 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center beginning 31 July 2025 10:30 (UTC) until 31 July 2025 14: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
Jul 31, 09:55 UTC
Jul 30, 2025
Emergency Network Maintenance - AP-West (Mumbai)
Completed - The scheduled maintenance has been completed.
Jul 30, 21:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 30, 17:30 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center beginning 30 July 2025 17:30 (UTC) until 30 July 2025 21: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
Jul 30, 08:15 UTC
Jul 29, 2025
Connectivity Issue - US-MIA (Miami)
Postmortem - Read details
Jul 31, 21:11 UTC
Resolved - We haven’t observed any additional connectivity issues in our US-MIA (Miami) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jul 29, 18:52 UTC
Update - At this time we have been able to correct the issues affecting connectivity in our US-MIA (Miami) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Jul 22, 19:00 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our US-MIA (Miami) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Jul 19, 16:41 UTC
Update - Our team has identified the issue affecting connectivity in our US-MIA (Miami) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Jul 19, 15:02 UTC
Investigating - Our team is investigating an issue affecting connectivity in our US-MIA (Miami) 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.
Jul 19, 14:09 UTC
Jul 28, 2025
Jul 27, 2025
Jul 26, 2025

No incidents reported.

Jul 25, 2025

No incidents reported.

Jul 24, 2025
Emerging Service Issue - Object Storage - Chicago
Resolved - This incident has been resolved.
Jul 24, 20:46 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 24, 20:40 UTC
Identified - Between approximately 19:45 UTC 20:15 UTC our Object Storage endpoint in Chicago experienced unusually high error rates. During this time, a subset of customers experienced timeouts or server errors when attempting to create or delete buckets via the Linode API or access objects within their buckets.
Jul 24, 20:38 UTC
Investigating - Our team is investigating an emerging service issue affecting Object Storage in Chicago. We will share additional updates as we have more information.
Jul 24, 20:25 UTC
Scheduled Network Maintenance(Cloud Firewall2) - US-MIA (Miami)
Completed - The scheduled maintenance has been completed.
Jul 24, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 24, 04:00 UTC
Scheduled - We will perform network maintenance at the US-MIA (Miami) data center on July 24, 2025, from 04:00 UTC to 10:00 UTC. While we do not anticipate any impact, there may be brief connectivity disruptions during this window, and the firewall will be offline for a short period.
Jul 18, 06:43 UTC
Maintenance for Linode Support Ticketing System
Completed - The scheduled maintenance has been completed.
Jul 24, 04:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 24, 03:00 UTC
Scheduled - On Wednesday, July 23rd at 11:00PM EDT (Thursday, July 24th at 3:00AM UTC), scheduled maintenance will be performed on the Linode Support Ticketing System. Expected downtime for this maintenance will be about 60 minutes.

This should not impact the ability to access services or utilize Cloud Manager. Customers who need assistance from Linode Support during this time will need to call 855-454-6633 (+1-609-380-7100 outside of the United States) to contact our Support team. Please note that our Support team will not be able to assist with issues related to the Cloud Manager or API, authenticate users to their accounts, or respond to Support tickets for the duration of the maintenance window.

As soon as our Support team regains access, we will answer tickets in the order they are received.
Jul 15, 21:08 UTC
Jul 23, 2025
Scheduled failover testing for Linode API service
Completed - The scheduled maintenance has been completed.
Jul 23, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 23, 14:00 UTC
Scheduled - The Linode API will undergo scheduled failover testing between 14:00 UTC and 16:00 UTC on July 23, 2025. During this window, the API service should be operational except for a brief (<5min) period during the route switching . We will update this status page if we encounter any unexpected issues.
Jul 21, 20:23 UTC
Maintenance for Linode Cloud Manager, API, and CLI
Completed - The scheduled maintenance has been completed.
Jul 23, 04:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 23, 02:00 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 04:00 UTC on July 23, 2025. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Please ensure that you complete critical or important jobs in the Cloud Manager or API before the maintenance window. We will update this status page once this event is complete and Linode customers have full access to all Linode services.

Customers who need assistance from Linode Support during this time will need to call 855-454-6633 (+1-609-380-7100 outside of the United States) to contact our Support team. Please note that our Support team will not be able to assist with issues related to the Cloud Manager or API, authenticate users to their accounts, or respond to Support tickets for the duration of the maintenance window. As soon as our Support team regains access, we will answer tickets in the order they are received.

Impacts on Current Linode Customers:
Current Linode customers will not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes Create, Remove, Boot, Migrate, Back Up, Shut Down, etc.

The scheduled maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, including items such as autoscaling, recycling, rebooting, attaching/detaching PVCs, Node Balancer provisioning, as well as the ability to create new clusters. Cluster nodes and running workloads will not be affected.

Impacts on Users Trying to Create Linode Accounts / Awaiting Account Authentication:
While the Linode Cloud Manager is offline during the maintenance period, we are unable to accept requests for new accounts or authenticate accounts for users awaiting full account access.

Thank you for your patience and understanding.
Jul 7, 20:22 UTC
Jul 22, 2025
Jul 21, 2025
Service Issue - LKE and Object Storage - All Regions
Postmortem - Read details
Jul 21, 17:31 UTC
Resolved - We haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jul 21, 14:54 UTC
Update - We have successfully corrected the issue affecting the Object Storage E2/E3 endpoints in Melbourne, London, Tokyo, Washington, Singapore, Frankfurt, Mumbai, Seattle, and Chicago. Also, the Linode Kubernetes Engine (LKE) service has been restored and is working as expected. We will be monitoring this to ensure that the service remains 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.
Jul 19, 19:10 UTC
Monitoring - At this time, we have successfully corrected the issue affecting the Object Storage E2/E3 endpoints in Melbourne, London, Tokyo, Washington, Singapore, Frankfurt, Mumbai, and Seattle. Also, the Linode Kubernetes Engine (LKE) service has been restored and is working as expected. We will be monitoring this to ensure that the service remains 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.
Jul 19, 15:51 UTC
Update - The efforts to establish Object Storage E2/E3 endpoints in Seattle have been successfully completed, following similar achievements in Melbourne, London, Tokyo, Washington, Singapore, Frankfurt, and Mumbai. Work on the remaining Object Storage E2/E3 endpoints is still ongoing, and it will require additional time to fully resolve these issues. We appreciate your patience and will provide further updates as progress is made.
Jul 19, 15:21 UTC
Update - The efforts to establish Object Storage E2/E3 endpoints in Frankfurt and Mumbai have been successfully completed, following similar achievements in Melbourne, London, Tokyo, Washington, and Singapore. Work on the remaining Object Storage E2/E3 endpoints is still ongoing, and it will require additional time to fully resolve these issues. We appreciate your patience and will provide further updates as progress is made.
If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 19, 13:49 UTC
Update - The efforts for Object Storage E2/E3 endpoints from London, Melbourne, Tokyo, Washington and Singapore are completed. For the remaining Object Storage E2/E3 endpoints, the mitigation efforts are ongoing and will require additional time to fully resolve the issue. We appreciate your patience and will provide further updates as progress continues.
If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 19, 12:58 UTC
Update - The efforts for Object Storage E2/E3 endpoints from London, Melbourne and Tokyo are completed. For the remaining Object Storage E2/E3 endpoints, the mitigation efforts are ongoing and will require additional time to fully resolve the issue. We appreciate your patience and will provide further updates as progress continues.
If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 19, 12:09 UTC
Update - The efforts for Object Storage E2/E3 endpoints from London and Melbourne are completed. For the remaining Object Storage E2/E3 endpoints, the mitigation efforts are ongoing and will require additional time to fully resolve the issue. We appreciate your patience and will provide further updates as progress continues.
If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 19, 08:24 UTC
Update - Our subject matter experts are continuing to work on mitigating the impact. The efforts for Object Storage E2/E3 endpoints from Melbourne are completed. For the remaining Object Storage E2/E3 endpoints, the mitigation efforts are ongoing and will require additional time to fully resolve the issue. We appreciate your patience and will provide further updates as progress continues.
If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 19, 03:27 UTC
Update - Our subject matter experts are continuing to work on mitigating the impact. The efforts for Object Storage E2/E3 endpoints from Melbourne are completed. For the remaining Object Storage E2/E3 endpoints, the mitigation efforts are ongoing and will require additional time to fully resolve the issue. We appreciate your patience and will provide further updates as progress continues.
If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 19, 00:05 UTC
Update - Our subject matter experts are continuing to work on mitigating the impact. The Linode Kubernetes Engine (LKE) service has been largely restored, and we continue to work on mitigating the impact in the London and Chicago regions. Mitigation efforts for Object Storage E2/E3 endpoints are ongoing and will require additional time to fully resolve the issue. We appreciate your patience and will provide further updates as progress continues.
Jul 18, 18:43 UTC
Update - We are continuing to work on mitigating the impact of this incident. The Linode Kubernetes Engine (LKE) service has been largely restored and is operating normally for most customers. Mitigation efforts for Object Storage E2/E3 endpoints are ongoing and will require additional time to fully resolve. We appreciate your patience and will provide further updates as progress continues.
Jul 18, 14:10 UTC
Update - Our subject matter experts are actively working on the recovery of the impacted Object Storage E2/E3 endpoints. We will share further updates as we make progress. We apologize for the impact and thank you for your patience and continued support. If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 18, 09:20 UTC
Update - Current Status
Our teams are actively working to resolve issues impacting Object Storage E2 and E3 endpoints. While Standard (E0/E1) endpoints were not affected, we are working on system recovery for all E2 and E3 endpoints. These issues are being prioritized, and expert teams are engaged in resolving the impact.

Object Storage E2 and E3 Endpoint Recovery Plan
We are employing an incremental approach to ensure a safe and methodical recovery.

> Recovery order by Datacenter: We understand that you may have questions about the recovery process for your specific region. At this time, we are taking a step-by-step approach, and as a result, we do not yet have a determined order for datacenter recovery. Our focus is on restoring systems safely, working to minimize impact across all customers. We will share updates regularly as recovery progresses and will notify you promptly once we can confirm timelines for your specific E2/E3 Endpoint region(s).
> Testing and Validation: To ensure stability and avoid service disruptions, all systems will undergo extensive testing prior to resuming regular operations.

Impact and Timelines
While we are devoting 24/7 engineering resources to this recovery operation, complete resolution will depend on the results of our ongoing diagnostics. Full recovery for affected regions may require multiple days and our teams are looking for ways to optimize and parallelize recovery operations. As we make further progress over the next few hours, we expect to be able to provide more specific updates on estimated recovery times.

Our Commitment
We deeply regret the impact being caused by this disruption and want to assure you of our commitment to restoring full operations as quickly and safely as possible. We will keep you updated with progress and key milestones throughout the recovery process. If you have any questions or concerns, please do not hesitate to reach out to our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 18, 02:39 UTC
Identified - Affected services have begun to come back online. Currently, the following services are up:
• Creating and restoring images to Linodes
• LKE and LKE-Enterprise new cluster provisioning, except in London
• Managed Databases

We are working to restore service to all affected Object Storage E2 and E3 endpoints and will continue to provide updates as more services come back online.
Jul 18, 01:06 UTC
Update - We are continuing to investigate this issue. The appropriate subject matter experts are engaged. We will continue to provide hourly updates until we have a clearer picture about the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.
Jul 17, 23:43 UTC
Update - We have confirmed that the issue is impacting the following services:
• Object Storage Key and bucket management using the Linode Cloud Manager and Linode APIv4
• The following Object Storage E2 and E3 endpoints are down:
• jp-osa-1.linodeobjects.com
• us-sea-9.linodeobjects.com
• au-mel-1.linodeobjects.com
• gb-lon-1.linodeobjects.com
• in-bom-1.linodeobjects.com
• jp-tyo-1.linodeobjects.com
• us-iad-13.linodeobjects.com
• us-ord-10.linodeobjects.com
• de-fra-1.linodeobjects.com
• sg-sin-1.linodeobjects.com
• Linode Kubernetes Engine (LKE) and LKE-Enterprise
• Creating clusters
• Restoring clusters from a backup
• Creating and restoring images, including deployment of Linodes from images
• Managed Databases
• Provisioning new clusters
• Resizing existing clusters
• Resuming a suspended cluster
• Restoring existing clusters from backup
• Multi-node clusters will be able to recover from a primary node failure automatically as long as cluster standby Linodes are online
• Automatic recreation of failed nodes is unavailable at this time


We will continue to share updates as we have more information.
Jul 17, 22:32 UTC
Investigating - Our team is investigating an emerging service issue affecting LKE and Object Storage in all regions. We will share additional updates as we have more information.
Jul 17, 20:35 UTC
← Incident History Powered by Atlassian Statuspage