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

Linode Status

← Current Status
Connectivity Issue - ASIA Data Centers
Update - The third-party continues working on a fix for this issue, and due to the complexity of this problem, it will take longer to mitigate it completely. In the meantime, we continue monitoring our systems. If you are still experiencing issues, please open a Support ticket for assistance.
Feb 25, 2025 - 19:44 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity from our Asia to Europe 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.
Jan 27, 2025 - 10:16 UTC
Identified - Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. 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.
Jan 25, 2025 - 16:49 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 (Sao 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
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
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
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
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
AP-West (Mumbai) Operational
EU-West (London) Operational
GB-LON (London 2) Operational
AU-MEL (Melbourne) 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) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Managed Databases Monitoring and Alerting Maintenance Apr 8, 2025 09:30-11:30 UTC

The Akamai Cloud Pulse observability suite which enables Monitoring and Alerting for our Managed Databases offering is scheduled to undergo maintenance on April 8th, 2025, between 9:30 AM and 11:30 AM UTC. During this window there is the potential for duplicate alerts configured for your Managed Databases services to be triggered. This maintenance WILL NOT impact the functionality of our Managed Databases service, only the Monitoring and Alerting features. We will update this status page if we encounter any unexpected issues.
Posted on Mar 27, 2025 - 12:49 UTC

Scheduled Network Maintenance - AU-MEL (Melbourne) Apr 18, 2025 02:00-06:00 UTC

We will be performing network maintenance in our AU-MEL (Melbourne) data center between 02:00 UTC and 06:00 UTC on April 18, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Posted on Apr 03, 2025 - 23:27 UTC
Apr 4, 2025

No incidents reported today.

Apr 3, 2025
Service Issue - Linode Kubernetes Engine
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.
Apr 3, 01:09 UTC
Monitoring - At this time we have been able to correct the issues affecting the LKE 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.
Apr 1, 23:03 UTC
Identified - Our team has identified the underlying cause of the issue affecting DNS functionality within the Linode Kubernetes Engine (LKE) service. We are in the process of implementing a fix. Users may have experienced difficulty connecting to their cluster's control plane, but internal cluster services remain unaffected at this time.

We will continue to provide updates as we work to fully resolve the issue. Thank you for your patience.
Apr 1, 22:29 UTC
Update - Our team is actively investigating an issue impacting DNS functionality within the Linode Kubernetes Engine (LKE) service. We will provide further updates as more information becomes available.
Apr 1, 21:33 UTC
Investigating - Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Apr 1, 20:28 UTC
Apr 2, 2025

No incidents reported.

Apr 1, 2025
Mar 31, 2025
Emerging Service Issue - Object Storage - SEA
Resolved - At this time, we have been able to correct the issues affecting the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 31, 13:08 UTC
Update - Our team continues to investigate the issue affecting the Object Storage in Seattle. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 31, 10:25 UTC
Identified - Our team has identified the issue affecting the Object Storage in Seattle. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 31, 07:06 UTC
Investigating - Our team is investigating an emerging service issue affecting Object Storage in SEA. We will share additional updates as we have more information.
Mar 31, 03:50 UTC
Emerging Service Issue - Linode Kubernetes Engine - Multiple Regions
Resolved - We haven’t observed any additional issues with the LKE Control Plane pods, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 31, 00:37 UTC
Monitoring - At this time we have been able to correct the LKE control plane pod issues across all regions. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Mar 30, 05:13 UTC
Identified - Our team has identified the issue affecting the LKE Control Plane Pods. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 30, 03:38 UTC
Update - We are continuing to investigate this issue.
Mar 30, 02:10 UTC
Investigating - Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
Mar 30, 00:09 UTC
Mar 30, 2025
Mar 29, 2025

No incidents reported.

Mar 28, 2025
Emerging Service Issue - Node Balancers - All Regions
Resolved - We haven’t observed any additional issues with the Node Balancers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 28, 09:05 UTC
Monitoring - At this time we have been able to correct the issues affecting the NodeBalancer service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a ticket with our Support Team.
Mar 28, 05:56 UTC
Update - We are continuing to investigate this issue.
Mar 28, 01:07 UTC
Update - We are continuing to investigate this issue.
Mar 27, 23:45 UTC
Investigating - Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
Mar 27, 22:57 UTC
Mar 27, 2025
Mar 26, 2025

No incidents reported.

Mar 25, 2025
Cloud Manager, API, CLI, linode.com Maintenance
Completed - The scheduled maintenance has been completed.
Mar 25, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 25, 14:00 UTC
Scheduled - The Linode Cloud Manager, API, CLI, and linode.com will be undergoing scheduled maintenance between 14:00 UTC and 16:00 UTC, Tuesday, March 25, 2025. During this window, running Linodes and related services should not be disrupted. We will update this status page if we encounter any unexpected issues.
Mar 7, 18:18 UTC
Mar 24, 2025
Service Issue - Object Storage (LON)
Resolved - We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 24, 21:31 UTC
Monitoring - At this time we have been able to correct the issues affecting the Object 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.
Mar 24, 21:01 UTC
Update - Our team continues to investigate the issue affecting the Object Storage service in London. During this time, users may experience connection timeouts and errors with this service.
Mar 24, 19:54 UTC
Investigating - Our team is investigating an issue affecting the Object Storage service in London. During this time, users may experience connection timeouts and errors with this service.
Mar 24, 17:08 UTC
Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025
Emergency Network Maintenance - AP-WEST (Mumbai)
Completed - The scheduled maintenance has been completed.
Mar 21, 00:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 20, 18:30 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-WEST (Mumbai) data center beginning 20 March 2025, 18:30 UTC until 21 March 2025, 00: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.
Mar 20, 16:05 UTC
← Incident History Powered by Atlassian Statuspage