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

Linode Status

← Current Status

All Systems Operational

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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Scheduled Network Maintenance - US-Central (Dallas) May 28, 2025 05:00-09:00 UTC

We will be performing an emergency network maintenance in our US-Central (Dallas) data center from 05:00 (UTC) until 09:00 (UTC) on Wednesday, May 28th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Posted on May 20, 2025 - 14:19 UTC

Scheduled Network Maintenance - JP-TYO-3 (Tokyo 3) Jun 17, 2025 13:00-17:00 UTC

We will be performing network maintenance in our JP-TYO-3 (Tokyo 3) data center from 13:00 UTC to 17:00 UTC on June 17, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Posted on May 22, 2025 - 15:31 UTC

Maintenance for Linode Support Ticketing System Jun 21, 2025 06:30-07:30 UTC

On Saturday, May 17th at 2:30AM EDT (Saturday, May 17th at 6:30 AM 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.
Posted on May 14, 2025 - 14:45 UTC
May 22, 2025
Emergency Network Maintenance - AP-West (Mumbai)
Completed - The scheduled maintenance has been completed.
May 22, 18:54 UTC
Verifying - Verification is currently underway for the maintenance items.
May 22, 18:42 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 22, 18:00 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center beginning 22 May 2025 18:00 (UTC) until 22 May 2025 20:00 (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
May 22, 05:55 UTC
May 21, 2025
Scheduled Emergency Network Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
May 21, 09:00 UTC
Verifying - Verification is currently underway for the maintenance items.
May 21, 08:59 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 05:00 UTC
Scheduled - We will be performing an emergency network maintenance in our US-Central (Dallas) data center from 05:00 (UTC) until 09:00 (UTC) on Wednesday, May 20th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
May 20, 14:15 UTC
Maintenance for Cloud Manager, API, and CLI
Completed - The scheduled maintenance has been completed.
May 21, 05:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 02:00 UTC
Update - This scheduled maintenance has been rescheduled to occur on May 21st.
May 12, 14:06 UTC
Update - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on May 14, 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, to include 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.
Apr 15, 20:06 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on May 14, 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, to include 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.
Apr 4, 16:48 UTC
May 20, 2025

No incidents reported.

May 19, 2025

No incidents reported.

May 18, 2025

No incidents reported.

May 17, 2025

No incidents reported.

May 16, 2025
Connectivity Issue - IN-MAA (Chennai) and IN-BOM-2
Resolved - The networking issue caused by an upstream problem with one of our peering partners has been resolved. The impacted regions were IN-MAA (Chennai) and IN-BOM-2 (Mumbai), occurring between 19:00 and 21:00 UTC.

If you continue to experience problems, please open a Support ticket for assistance.
May 16, 23:21 UTC
Investigating - Our team is investigating an issue that affected connectivity in our IN-MAA (Chennai) and IN-BOM-2 data centers, related to a suspected outage with one of our peering partners. During this time, users may had experienced Packet loss and intermittent connection errors for services deployed in these data centers. We will share additional updates as we have more information.
May 16, 21:20 UTC
Emerging Service Issue - Mumbai
Resolved - The networking issue caused by an upstream problem with one of our peering partners has been resolved. The impacted regions were Mumbai (ap-west) and Mumbai 2 (in-bom-2), occurring between 1845 and 2000 UTC.


If you continue to experience problems, please open a Support ticket for assistance.
May 16, 20:42 UTC
Investigating - Our team is investigating an emerging upstream networking issue affecting connectivity in Mumbai. We will share additional updates as we have more information.
May 16, 19:51 UTC
May 15, 2025

No incidents reported.

May 14, 2025
Emergency Network Maintenance - AP-West (Mumbai)
Completed - The scheduled maintenance has been completed.
May 14, 18:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 18:00 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center beginning 14 May 2025 18:00 (UTC) until 14 May 2025 20:00 (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
May 14, 12:00 UTC
May 13, 2025
Connectivity Issue - BR-GRU (São Paulo)
Postmortem - Read details
May 21, 15:44 UTC
Resolved - We haven’t observed any additional connectivity issues in our BR-GRU (São Paulo) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
May 13, 20:12 UTC
Update - We are continuing to monitor for any further issues.
May 13, 17:35 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our BR-GRU (São Paulo) 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.
May 13, 17:28 UTC
Investigating - Our team is investigating an issue affecting connectivity in our BR-GRU (São Paulo) 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.
May 13, 16:42 UTC
May 12, 2025
Service Issue - Compute - AP-Northeast-2 and JP-TYO-3
Postmortem - Read details
May 13, 01:30 UTC
Resolved - We haven’t observed any additional connectivity issues in our AP-Northeast-2 (Tokyo 2) and JP-TYO-3 (Tokyo 3) data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
May 12, 09:29 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our AP-Northeast-2 (Tokyo 2) and JP-TYO-3 (Tokyo 3) data centers. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
May 12, 03:04 UTC
Update - Our subject matter experts are continuing to investigate this issue. The next update will be provided as we make progress.
May 12, 02:33 UTC
Investigating - Our team is investigating an emerging service issue affecting connectivity to Compute Instances in our Tokyo 2 data center. We will share additional updates as we have more information.
May 12, 00:44 UTC
May 11, 2025

No incidents reported.

May 10, 2025

No incidents reported.

May 9, 2025

No incidents reported.

May 8, 2025
Maintenance for Linode Support Ticketing System
Completed - The scheduled maintenance has been completed.
May 8, 13:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 8, 13:00 UTC
Scheduled - On Thursday, May 8th, 2025, at 9:00AM EDT (May 8th, 2025, at 13:00 UTC), scheduled maintenance will be performed on the Linode Support Ticketing System.

Expected downtime for this maintenance will be about 20-30 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.
May 6, 14:51 UTC
← Incident History Powered by Atlassian Statuspage