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

Linode Status

← Current Status
Service Issue - GPU and VPU Booting issues
Update - We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Feb 26, 2026 - 15:42 UTC
Update - We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
Feb 19, 2026 - 16:41 UTC
Update - We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
Feb 03, 2026 - 15:34 UTC
Update - We have successfully identified a solution to address the issue at hand. We are currently in the testing phase prior to initiating the rollout of the fix. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
Jan 05, 2026 - 19:30 UTC
Update - We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
Jan 05, 2026 - 17:16 UTC
Update - We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
Dec 17, 2025 - 13:40 UTC
Update - We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
Dec 04, 2025 - 20:51 UTC
Identified - Our team has identified the issue affecting booting up GPU and VPU plans. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Dec 03, 2025 - 16:48 UTC
Investigating - Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.
Dec 03, 2025 - 15:15 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
FR-PAR-2 (Paris 2) 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 (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
ACLP Logs Operational
ACLP Logs Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Maintenance for Linode Cloud Manager, API, and CLI Mar 21, 2026 11:00-23:00 UTC

The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 11:00 UTC to 23:00 (UTC) on Saturday, March 21th, 2026. During this window, running Linodes and related services will not be disrupted, but there may be brief periods of increased latency of responses or unavailability of the Linode Cloud Manager, API, and CLI.

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 may 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 may 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 brief periods 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:
For brief periods during the maintenance window, current Linode customers may not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes actions such as create, remove, boot, migrate, back up, shut down, etc across all Linode services. While we expect the impact period to be approximately 10 minutes cumulatively across the maintenance window, a longer impact period is possible.

This maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, including autoscaling, recycling, rebooting, attaching/detaching PVCs, NodeBalancer 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:
The Linode Cloud Manager may be offline for brief periods 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.
Posted on Feb 17, 2026 - 16:55 UTC

Maintenance for Linode Cloud Manager, API, and CLI Apr 18, 2026 11:00-23:00 UTC

The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 11:00 UTC to 23:00 (UTC) on Saturday, April 18, 2026. During this window, running Linodes and related services will not be disrupted, but there may be brief periods of increased latency of responses or unavailability of the Linode Cloud Manager, API, and CLI.

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 may 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 may 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 brief periods 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:
For brief periods during the maintenance window, current Linode customers may not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes actions such as create, remove, boot, migrate, back up, shut down, etc across all Linode services. While we expect the impact period to be approximately 10 minutes cumulatively across the maintenance window, a longer impact period is possible.

This maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, including autoscaling, recycling, rebooting, attaching/detaching PVCs, NodeBalancer 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:
The Linode Cloud Manager may be offline for brief periods 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.
Posted on Feb 17, 2026 - 16:58 UTC
Mar 7, 2026

No incidents reported today.

Mar 6, 2026

No incidents reported.

Mar 5, 2026
Service Issue: RTX 4000 Ada GPU Errors Across Multiple Regions
Resolved - We haven’t observed any additional issues with the service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 5, 18:11 UTC
Monitoring - At this time we have been able to correct the issues affecting the 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 5, 17:01 UTC
Identified - Our team has identified the issue affecting the service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 5, 16:23 UTC
Update - We are continuing to investigate and will provide the next update as progress is made.
Mar 5, 14:48 UTC
Investigating - We are aware of a recurrence of this issue across multiple regions. We are continuing to investigate and will provide the next update as progress is made.
Mar 5, 10:50 UTC
Monitoring - Our team has identified the issue affecting the service and implemented a fix. 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 5, 07:34 UTC
Update - We are continuing to investigate the issue. We will provide the next update as progress is made.
Mar 5, 06:55 UTC
Update - Our subject matter experts are actively investigating the issue. We will provide the next update as progress is made.
Mar 5, 05:48 UTC
Investigating - We are investigating a critical service issue affecting NVIDIA RTX 4000 Ada GPU nodes across multiple regions, including Osaka (osa1), Seattle (sea1), and Chicago (ord1).
Affected GPU nodes may report an unrecoverable error state leading to failures in Vulkan initialization and GPU-accelerated workloads. Additionally, some LKE clusters in the Osaka region are currently experiencing Control Plane connectivity issues, resulting in timed-out API requests and errors.
Our engineering teams are currently investigating the root cause, focusing on a potential regression in the underlying host hypervisor or GPU firmware. We will provide more information as it becomes available
Mar 5, 02:07 UTC
Connectivity Issue - FRA datacenter (Frankfurt)
Postmortem - Read details
Mar 5, 21:32 UTC
Resolved - We haven’t observed any additional connectivity issues in our Frankfurt data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 5, 09:00 UTC
Mar 4, 2026
Emerging Issue - Linode Manager and API
Resolved - We haven't observed any additional issues, 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.
Mar 4, 23:50 UTC
Update - Our team is actively investigating the issue affecting Linode Manager and API, which is causing duplicate notification emails for some customers. We appreciate your patience as we work to resolve this. We will provide further updates as soon as we have more information.
Mar 4, 18:14 UTC
Update - We are continuing to investigate the issue. We will share additional updates as we have more information and once progress is made.
Mar 4, 12:48 UTC
Investigating - We are aware some customers are receiving duplicate notification emails in fixed intervals. Additional updates will be shared once we have more information.
Mar 4, 09:21 UTC
Mar 3, 2026
Connectivity Issue - Mumbai, IN (in-mum)
Resolved - We haven’t observed any additional connectivity issues in our Mumbai, IN (in-mum) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 3, 17:30 UTC
Monitoring - We have taken mitigation steps and escalated to our third-party service provider in our Mumbai, IN (in-mum) data center, who confirmed the impact was caused due to ongoing restoration activities on their cable system during that period, which has been completed.; based on current observations as of 13:40 UTC on February 28, 2026, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.
Feb 28, 17:43 UTC
Investigating - At this time we have been able to apply mitigation actions that improve the experience for customers connecting to our Mumbai, IN (in-mum) data center. In the meantime, we are actively investigating the issue with our third-party and will share additional updates as we have more information. If you are experiencing issues, please open a Support ticket for assistance.
Feb 28, 12:16 UTC
Identified - We are aware of an ongoing reoccurrence of this issue starting from 09:17 UTC on February 28, 2026, which may cause degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region.
Our team is investigating and we will share additional updates as we have more information. If you are experiencing issues, please open a Support ticket for assistance.
Feb 28, 11:11 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Mumbai, IN (in-mum) 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 27, 21:34 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Mumbai, IN (in-mum) 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.
Feb 27, 21:00 UTC
Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026
Feb 27, 2026
Connectivity Issue - Singapore (ap-south)
Resolved - We haven’t observed any additional connectivity issues in our Singapore data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Feb 27, 21:01 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Singapore data center starting at approximately 1905 UTC, February 27, 2026. 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.
Feb 27, 20:18 UTC
Connectivity Issue - Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2)
Resolved - We haven’t observed any additional connectivity issues in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Feb 27, 19:45 UTC
Update - We are continuing to monitor for any further issues.
Feb 27, 15:48 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) 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.
Feb 27, 14:35 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers 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.
Feb 27, 13:38 UTC
Connectivity Issue - EU-West (London) datacenter
Postmortem - Read details
Mar 3, 08:30 UTC
Resolved - We haven’t observed any additional connectivity issues in our EU-West (London) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Feb 27, 09:33 UTC
Investigating - Our team is investigating an emerging service issue affecting the connectivity in EU-West (London). We will share additional updates as we have more information.
Feb 27, 07:59 UTC
Feb 26, 2026

Unresolved incident: Service Issue - GPU and VPU Booting issues.

Feb 25, 2026
Maintenance for Linode API
Completed - The scheduled maintenance has been completed.
Feb 25, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 25, 13:30 UTC
Scheduled - On Wednesday, February 25, 2026, starting at 1:30 PM UTC, We will be performing planned maintenance on the Linode API Platform. There is no expected downtime.
Feb 24, 06:59 UTC
Feb 24, 2026
Network Maintenance - IAD (Washington DC)
Completed - The scheduled maintenance has been completed.
Feb 24, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 24, 05:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jan 30, 19:58 UTC
Scheduled - We will be performing a network maintenance in our IAD (Washington DC) data center from 05:00 (UTC) until 11:00 (UTC) on Tuesday, February 24th, 2026. While we do not expect any downtime, a brief period of increased latency or packet loss may occur. If you have questions surrounding this Scheduled Maintenance please open a Support ticket from the Linode Manager.
Jan 30, 19:56 UTC
Feb 23, 2026

No incidents reported.

Feb 22, 2026

No incidents reported.

Feb 21, 2026
Emerging Service Issue - Cloud Manager Login - All Regions
Postmortem - Read details
Mar 5, 16:39 UTC
Resolved - At this time, we have been able to correct the issues affecting the login to linode.com and Cloud Manager. We haven't observed any additional issues with Linode.com and Cloud Manager, and will now consider this incident resolved. If you are still experiencing additional issues, please open a Support ticket for assistance.
Feb 21, 21:07 UTC
Update - We are continuing to work on a fix for this issue. Subsequent updates around mitigation status will be posted as progress is made.
Feb 21, 20:36 UTC
Update - We are continuing to work on a fix for this issue. Subsequent updates around mitigation status will be posted as progress is made.
Feb 21, 19:59 UTC
Identified - Our team has identified the issue affecting the ability to log in to linode.com and Cloud Manager using Google TPA across all regions. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Feb 21, 19:35 UTC
Update - We are continuing to investigate an issue impacting the ability to log in to linode.com and Cloud Manager using Google TPA across all regions. We will share additional updates as we have more information and once progress is made.
Feb 21, 19:06 UTC
Update - We are continuing to investigate an issue impacting the ability to login using Google TPA to linode.com and Cloud Manager in all regions. We will share additional updates as we have more information and once progress is made.
Feb 21, 17:41 UTC
Investigating - Our team is investigating an emerging service issue affecting the ability to login to linode.com or Cloud Manager in all regions. We will share additional updates as we have more information.
Feb 21, 15:20 UTC
← Incident History Powered by Atlassian Statuspage