Linode Outage History
Uptime record, past incidents, and downtime history for Linode.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| April 2026 | 0% | 10 | 10 |
| March 2026 | 22.6% | 31 | 24 |
| February 2026 | 69.6% | 23 | 7 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 64 Days)
Feb 6
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
Service Issue - Networking in US-IAD (Washington)
Started: Apr 9, 11:32 PM
investigating
We are continuing to investigate the issue. We will provide the next update as we make progress.
Apr 10, 1:04 AM
investigating
Our team continues to investigate the issue affecting networking in US-IAD (Washington) 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 within the next 60 minutes.
Apr 10, 12:27 AM
investigating
Our team is investigating an emerging service issue affecting networking in US-IAD (Washington). We will share additional updates as we have more information.
Apr 9, 11:32 PM
Emerging Service Issue - Network - London 2(gb-lon)
Started: Apr 7, 9:02 AM
monitoring
We've determined that the impact of the issue caused by an upstream AS has been mitigated. We continue to monitor the situation until we recieve further confirmation of the resolution.
Apr 7, 10:17 AM
investigating
Our team is investigating an emerging service issue affecting connectivity to our Linode infrastructure in the London 2(gb-ion) region likely caused due to a upstream AS. We will continue to share more details as we verify this.
Apr 7, 9:02 AM
Emerging Service Issue - Object Storage - us-east-1
Started: Apr 7, 12:50 AM
identified
The issue has been identified and a fix is being implemented.
Apr 7, 1:13 AM
investigating
Our team is investigating an emerging service issue affecting Object Storage in us-east-1. We will share additional updates as we have more information.
Apr 7, 12:50 AM
March 2026
Service Issue - New Linode Creation
Started: Mar 24, 5:59 PM
investigating
Our team is investigating an emerging service issue affecting the deployment of new compute instances where the swap disk size is set to 0. This is also impacting our Managed Databases service. We will share additional updates as we have more information.
Mar 24, 5:59 PM
Connectivity Issue - Jakarta, ID (id-cgk)
Started: Mar 20, 11:29 AM
monitoring
At this time we have been able to correct the issues affecting connectivity in our Jakarta, ID data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Mar 20, 5:28 PM
identified
We are continuing to work on resolving the connectivity issue in our Jakarta, ID (id-cgk) data center. Thank you for your patience as we restore full service.
Mar 20, 4:58 PM
identified
We are making steady progress toward full recovery of the connectivity issue at our Jakarta, ID (id-cgk) data center. Most services in Jakarta are now operational. However, some Linodes and Linode Kubernetes Engine (LKE) clusters may still be affected, especially if nodes are provisioned or attempt to provision on impacted Linodes. The dependency issues that previously affected Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel) have been resolved.
We continue to work on restoring ...
Mar 20, 4:07 PM
identified
Our teams are continuing to mitigate the connectivity issue in Jakarta, ID and are working to restore full service. We appreciate your patience as we resolve the remaining disruptions.
Mar 20, 3:13 PM
identified
We are continuing to address the connectivity issue at our Jakarta, ID (id-cgk) data center. Most services have recovered, but some compute services in Jakarta remain affected. Due to backend dependencies, customers in the Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel) data centers may also experience disruptions, particularly with Linode Kubernetes Engine (LKE) deployments. Our teams are actively working to resolve these issues and restore full service. We appreciate your pati...
Mar 20, 2:23 PM
identified
We are still working to resolve the connectivity issue at our Jakarta, ID data center. While most services are recovering, some compute services in Jakarta may still be affected. Due to backend dependencies, there may also be impacts to nearby data centers Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel). Linode Kubernetes Engine (LKE) in these regions could experience disruptions because of a dependency with Jakarta, ID (id-cgk). We appreciate your patience and will provide furt...
Mar 20, 1:31 PM
identified
We are continuing to implement a fix for the connectivity issue in our Jakarta, ID data center.
Mar 20, 12:57 PM
investigating
Our team has identified the issue affecting connectivity in our Jakarta, ID data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 20, 12:11 PM
investigating
Our team has identified the issue affecting connectivity in our Jakarta data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 20, 11:29 AM
Service Issue - Linode Kubernetes Engine Enterprise (LKE-E) - Chicago, IL (us-ord)
Started: Mar 17, 1:04 PM
monitoring
At this time we have been able to correct the issues affecting the LKE-E service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Mar 17, 1:27 PM
identified
Our team has identified the issue affecting the LKE-E service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 17, 1:14 PM
investigating
Our team is investigating an issue affecting the Linode Kubernetes Engine Enterprise (LKE-E) service. We will share additional updates as we have more information.
Mar 17, 1:04 PM
Emerging Service Issue - Networking in Washington, DC (US-IAD)
Started: Mar 13, 5:58 PM
identified
Our team has identified the issue affecting connectivity in our Washington data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 13, 7:02 PM
investigating
Our team has identified the issue affecting connectivity in our Washington data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 13, 6:59 PM
investigating
We are continuing to investigate the issue. We will share additional updates as we have more information.
Mar 13, 6:42 PM
investigating
Our team is investigating an emerging service issue affecting networking in our Washington, DC location (US-IAD). We will share additional updates as we have more information.
Mar 13, 5:58 PM
Service Issue - LKE-Enterprise - JP-OSA (Osaka)
Started: Mar 13, 12:45 AM
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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Mar 13, 1:53 AM
investigating
We are continuing to investigate this issue.
Mar 13, 1:31 AM
investigating
Our team is investigating an emerging service issue affecting the deployment of new LKE Enterprise Clusters in JP, OSA (Osaka). We will share additional updates as we have more information.
Mar 13, 12:45 AM
December 2025
Service Issue - GPU and VPU Booting issues
Started: Dec 3, 3:15 PM
identified
We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Apr 6, 1:39 PM
identified
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.
Mar 19, 8:13 PM
identified
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, 3:42 PM
identified
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, 4:41 PM
identified
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 3, 3:34 PM
identified
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 5, 7:30 PM
identified
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 5, 5:16 PM
identified
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, 1:40 PM
identified
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 4, 8:51 PM
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 3, 4:48 PM
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 3, 3:15 PM