View All Products
Compute
Storage
Networking
Databases
Services
Developer Tools
Industries
Pricing
Community
Engage With Us

Linode Status

← Current Status
Maintenance for Cloud Manager, API, and CLI
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 12, 2025 - 03:01 UTC
Update - To avoid conflicting with another maintenance on our platform, we've updated our previously scheduled February 5 maintenance window to February 12
Feb 12, 2025 03:00-06:00 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 03:00 UTC and 06:00 UTC on Wednesday, February 12th, 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.
Feb 12, 2025 03:00-06:00 UTC
Connectivity Issue - ASIA Data Centers
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 Under Maintenance
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
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
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
Emergency Network Maintenance - US-IAD (Washington) Feb 13, 2025 04:00-11:00 UTC
We will be performing emergency network maintenance in our US-IAD (Washington) data center between 04:00 UTC and 11:00 UTC on February 13, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Posted on Feb 10, 2025 - 16:17 UTC
Cloud Manager, API, CLI, linode.com Maintenance Feb 25, 2025 14:00-16:00 UTC
Update - To avoid conflicting with another maintenance on our platform, we've updated our previously scheduled February 11 maintenance window to February 25
Feb 04, 2025 - 14:53 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, February 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.
Jan 09, 2025 - 11:11 UTC
Cloud Manager, API, CLI, linode.com Maintenance Feb 27, 2025 14:00-16:00 UTC
Update - To avoid conflicting with another maintenance on our platform, we've updated our previously scheduled February 12 maintenance window to February 27
Feb 04, 2025 - 14:53 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, February 27, 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.
Jan 09, 2025 - 11:08 UTC
Past Incidents
Feb 12, 2025
Emergency Network Maintenance - FR-PAR (Paris)
Completed - The scheduled maintenance has been completed.
Feb 12, 03:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 11, 22:00 UTC
Scheduled - We will be performing emergency network maintenance in our FR-PAR (Paris) data center between 22:00 UTC on February 11, 2025, and 03:00 UTC on February 12, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Feb 10, 16:17 UTC
Feb 11, 2025
Feb 10, 2025
API Maintenance
Completed - The scheduled maintenance has been completed.
Feb 10, 13:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 10, 12:30 UTC
Scheduled - The API will be undergoing scheduled maintenance between 12:30 UTC and 13:30 UTC, Monday, February 10, 2025. During this window, brief periods of impact may be experienced when attempting to use the API. Running Linodes and related services should not be disrupted. We will update this status page if we encounter any unexpected issues.
Feb 7, 23:02 UTC
Feb 9, 2025

No incidents reported.

Feb 8, 2025

No incidents reported.

Feb 7, 2025

No incidents reported.

Feb 6, 2025
Cloud Manager and API performance degradation
Resolved - 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.
Feb 6, 20:41 UTC
Monitoring - Our team is aware of an issue that affected the Cloud Manager and API service between 07:19 UTC and 10:45 UTC on February 6, 2025. During this time, users may have experienced connection timeouts and errors with this service. Our team identified the issue affecting the Cloud Manager and API service. At this time, we have been able to correct the issues affecting the Cloud Manager and API 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.
Feb 6, 15:50 UTC
Scheduled Network Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
Feb 6, 13:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 6, 05:30 UTC
Scheduled - We will be performing a network maintenance in our US-Central (Dallas) data center from 05:30 (UTC) until 13:30 (UTC) on Thursday, February 6th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Jan 29, 13:02 UTC
Service Issue - Linode Kubernetes Engine
Resolved - We haven’t observed any additional issues with the LKE and LKE-E services, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Feb 6, 05:14 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.
Feb 6, 04:50 UTC
Update - We are continuing to work on a fix for this issue. We will provide the next update as we make progress.
Feb 6, 03:12 UTC
Identified - We have identified the issue affecting LKE, LKE-E, and other services, where image pull requests to DockerHub over IPv6 are being rate-limited. We are working on implementing a fix to resolve the rate limiting issue, and we will provide an update once the solution is in place. Thank you for your patience.
Feb 6, 01:06 UTC
Investigating - We are aware of an issue affecting DockerHub over IPv6, causing rate limiting between certain Linode data centers and DockerHub. This is impacting products like LKE, LKE-E, and other services that rely on image pulls from DockerHub repositories. We are actively investigating the issue, and will provide additional updates as more information becomes available.
Feb 5, 22:48 UTC
Feb 5, 2025
Connectivity Issue - Toronto
Resolved - We haven’t observed any additional connectivity issues in our our service provider Toronto data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Feb 5, 23:02 UTC
Update - We are continuing to monitor for any further issues.
Feb 5, 20:03 UTC
Monitoring - Our team became aware of an issue affecting connectivity in our service provider Toronto data center caused by a power outage. The issue started at approximately 18:21 UTC on February 05, 2025 and was mitigated at approximately 19:13 UTC on February 05, 2025. During this time, users could have experienced intermittent connection timeouts and errors for all services deployed in this 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.
Feb 5, 19:37 UTC
Maintenance for Linode Kubernetes Engine (LKE)
Completed - The scheduled maintenance has been completed.
Feb 5, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 06:00 UTC
Scheduled - The LKE team will be performing regular maintenance on Wednesday Feb 5, 2025 from 06:00 UTC to 23:00 UTC. During this time, we anticipate no workload interruption for High Availability customers, however, we recommend pausing administrative activities during this time. During maintenance, you may encounter occasional and brief failures in Kubernetes API requests, in addition you may observe Container Storage Interface (CSI) pods restarting. Please retry your requests, and if issues persist, contact our support team for assistance.
Jan 24, 16:52 UTC
Scheduled Network Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
Feb 5, 13:30 UTC
Verifying - Verification is currently underway for the maintenance items.
Feb 5, 08:18 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 08:15 UTC
Scheduled - We will be undergoing scheduled maintenance during this time.
Feb 5, 08:14 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 05:30 UTC
Scheduled - We will be performing a network maintenance in our US-Central (Dallas) data center from 05:30 (UTC) until 13:30 (UTC) on Wednesday, February 5th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Jan 29, 12:59 UTC
Connectivity Issue - DE-FRA-2 (Frankfurt 2)
Postmortem - Read details
Feb 6, 03:03 UTC
Resolved - We haven’t observed any additional connectivity issues in our DE-FRA-2 (Frankfurt 2) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Feb 5, 06:05 UTC
Monitoring - Between 03:22 UTC and 03:52 UTC on February 5, 2025, our DE-FRA-2 (Frankfurt 2) data center experienced a network disruption that may have affected connectivity for some customers. Instances remained powered on and running locally during this period. Our team identified the issue and implemented a resolution, restoring normal network operations at 03:57 UTC. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Feb 5, 04:09 UTC
Feb 4, 2025
Service Issue - Object Storage
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.
Feb 4, 20:36 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.
Feb 4, 20:29 UTC
Update - We are continuing to work on a fix for this issue. If you continue to experience problems, please open a Support ticket for assistance.
Feb 4, 20:28 UTC
Update - We are continuing to work on a fix for this issue. If you continue to experience problems, please open a Support ticket for assistance.
Feb 4, 20:19 UTC
Identified - Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Feb 4, 20:11 UTC
Monitoring - Our team is aware of an issue that affected Object Storage service between 18:30 UTC and 19:25 UTC. During this time, users may have experienced connection timeouts and errors with this service. Our team identified the issue affecting the Object Storage service. We have implemented a fix. 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.
Feb 4, 20:07 UTC
Cloud Manager and API performance degradation
Resolved - At this time we have been able to correct the issues, and haven't observed any additional issues with the Cloud Manager and API service since. If you continue to experience problems, please open a Support ticket for assistance. If you continue to experience problems, please open a Support ticket for assistance.
Feb 4, 18:50 UTC
Update - We are continuing to work on a fix for this issue.
Feb 4, 00:53 UTC
Update - We are continuing to work on a fix for this issue.
Feb 3, 08:52 UTC
Update - After additional investigation, we have confirmed that the impact caused by this issue during the impact window was not limited to Cloud Manager & API Object Storage and LKE requests only. This issue, also included degradation for a portion of all Cloud Manager and API requests.

We are continuing to work on a fix for this issue.
Feb 2, 21:56 UTC
Update - We are continuing to work on a fix for this issue.
Feb 2, 21:20 UTC
Identified - Our team became aware of a service issue that affects the Linode Cloud Manager and API.
The issue started at approximately 15:55 UTC on February 2nd, 2025 and was mitigated at 16:25 UTC on February 2nd, 2025.
During that time, some users may have experienced performance degradation when attempting Object Storage and LKE requests.

Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Feb 2, 18:42 UTC
Feb 3, 2025
Feb 2, 2025
Feb 1, 2025

No incidents reported.

Jan 31, 2025

No incidents reported.

Jan 30, 2025
Service Issue - Object Storage - US-MIA (Miami)
Resolved - Our team has identified an issue affecting the Object Storage service between approximately 21:30 UTC on January 30, 2025, and 01:30 UTC on January 31, 2025. During this time, users may have experienced 403 errors.
We have implemented a fix as of 01:30 UTC, on January 31, 2025, and haven't observed any additional issues with the Object Storage service since. If you continue to experience problems, please open a Support ticket for assistance.
Jan 30, 20:30 UTC
Jan 29, 2025
Service Issue - Block Storage Osaka
Resolved - We haven’t observed any additional issues with the Block Storage service in Osaka, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jan 29, 00:13 UTC
Monitoring - At this time we have been able to correct the issues affecting the Block Storage service in Osaka. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Jan 28, 20:48 UTC
Investigating - Our team is investigating a recurrence of the issue affecting the Block Storage service in our Osaka data center. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Jan 28, 20:04 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.
Jan 28, 19:04 UTC
Update - We are continuing to investigate this issue.
Jan 28, 18:46 UTC
Investigating - Our team is investigating an issue affecting the Block Storage service in our Osaka data center. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Jan 28, 18:45 UTC
← Incident History Powered by Atlassian Statuspage