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 |
|---|---|---|---|
| July 2026 | 0% | 9 | 9 |
| June 2026 | 0% | 30 | 30 |
| May 2026 | 0% | 31 | 31 |
| April 2026 | 0% | 21 | 21 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Apr 10
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
July 2026
Emerging Service Issue - Cloud Manager
Started: Jul 9, 4:57 PM
monitoring
At this time we have been able to correct the issue affecting the Cloud Manager logins. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.
Jul 9, 5:49 PM
investigating
We are continuing to investigate this issue. We will provide an update within the next 30 minutes.
Jul 9, 5:24 PM
investigating
Our team is investigating an emerging service issue affecting Cloud Manager logins. We will share additional updates as we have more information.
Jul 9, 4:57 PM
Emerging Service Issue - Managed Databases - All Regions
Started: Jul 6, 6:04 PM
investigating
Our team is investigating an emerging service issue affecting Managed Databases across all regions. Customers may experience latency when provisioning new databases or deleting existing ones. There is no observed impact to the performance or availability of active, running databases at this time. We will provide updates as more information becomes available.
Jul 6, 6:04 PM
Service Issue - Linode Automated Networking
Started: Jul 1, 5:21 PM
monitoring
A fix has been implemented to resolve the automated network configuration issue on Linodes using Network Helper. We recommend rebooting your Linode to restore full network functionality. We are actively monitoring the results to ensure continued stability.
Jul 1, 6:09 PM
identified
Our team is investigating a service issue that affects the auto configuration of networking on Linodes by Network Helper to fail. During that time, some users may have Linodes provision but appear to have no connectivity. This also can impact Linodes created by the Linode Kubernetes Engine and impact autoscaling or provisioning of clusters. Customers can still manually configure networking via the LISH console to mitigate this issue. Please see our guide on <a href="https://techdocs.akamai.co...
Jul 1, 5:21 PM
June 2026
Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)
Started: Jun 30, 6:54 PM
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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Jun 30, 10:10 PM
identified
We are continuing to work on a fix for this issue.
Jun 30, 9:36 PM
identified
Our team has identified the issue affecting the Block Storage service in our Singapore Expansion, SP (sg-sin-2) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Jun 30, 8:36 PM
investigating
We are continuing to investigate this issue.
Jun 30, 7:55 PM
investigating
Our team is investigating an emerging issue affecting the Block Storage service in our Singapore Expansion, SP (sg-sin-2) 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.
Jun 30, 6:54 PM
Service Issue - ACLP Metrics
Started: Jun 26, 5:35 PM
monitoring
We are continuing to monitor for any further issues.
Jun 30, 12:02 AM
monitoring
We have not observed a recurrence of the issue affecting the Cloud Pulse Metrics (ACLP Metrics) for several hours. Our team will continue to monitor the service closely while we investigate the underlying cause. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Jun 26, 9:13 PM
investigating
We are continuing to investigate this issue.
Jun 26, 8:04 PM
investigating
We are continuing to investigate this issue. We will provide further updates as we have more information.
Jun 26, 7:08 PM
investigating
We are continuing to investigate this issue. We will share additional updates as we have more information.
Jun 26, 6:19 PM
investigating
Our team is investigating an issue affecting the Cloud Pulse Metrics (ACLP Metrics), specifically impacting Managed Database Metrics reporting. The issue appears to be intermittent. We will share additional updates as we have more information.
Jun 26, 5:35 PM
Connectivity Issue - US-IAD
Started: Jun 26, 5:14 PM
investigating
Our team is investigating an issue affecting connectivity in our US-IAD data center. During this time, users may experience intermittent connection timeouts and errors for services deployed in this data center. We will share additional updates as we have more information.
Jun 26, 5:14 PM
Emerging Service Issue - Migrations
Started: Jun 25, 2:33 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 25, 2:50 PM
investigating
Our team is investigating an emerging service issue affecting migrations and resizes in all regions. At this time, Linode migrations and plan resizes may be delayed. We will share additional updates as we have more information.
Jun 25, 2:33 PM
Emerging Service Issue - GPU Instances - All Regions
Started: Jun 24, 6:53 PM
monitoring
At 20:32 UTC on June 24th, 2026 we have been able to correct the issue that is causing intermittent boot failures on GPU Instances in all Regions. 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.
Jun 24, 9:12 PM
investigating
We continue to investigate the issue that is causing intermittent boot failures on GPU Instances in all Regions. We will share additional updates as we have more information.
Jun 24, 8:00 PM
investigating
Our team is investigating an emerging service issue that is causing intermittent boot failures on GPU Instances in all Regions. We will share additional updates as we have more information.
Jun 24, 6:53 PM
Emerging Service Issue - Networking - US-MIA (Miami)
Started: Jun 16, 2:29 PM
investigating
Our team is investigating an emerging service issue affecting networking in US-MIA (Miami). We will share additional updates as we have more information.
Jun 16, 2:29 PM
Service Issue: Longview
Started: Jun 16, 8:56 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 16, 9:48 AM
identified
The issue has been identified and a fix is being implemented.
Jun 16, 9:46 AM
investigating
Our team is investigating an issue affecting the Longview service. During this time, users may experience "waiting for data" in cloud manager and might not see the expected metrics. We will share additional updates as we have more information.
Jun 16, 8:56 AM
Emerging Service Issue - Linode Migrations
Started: Jun 16, 3:44 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 16, 5:14 AM
identified
Our team is investigating an emerging service issue affecting Linode Migrations in all regions. Migrations might be slow or pending for long time. We will share additional updates as we have more information.
Jun 16, 3:44 AM
Emerging Service Issue - LKE Enterprise - All Regions
Started: Jun 5, 2:23 PM
investigating
We are currently investigating an emerging service issue affecting LKE Enterprise clusters across all regions. During this time, users may experience failures when deploying new clusters or upgrading existing ones. Our team is working to resolve this, and we will provide updates here as they become available.
Jun 5, 2:23 PM
Emerging Service Issue - Support Phone Line
Started: Jun 3, 2:22 PM
investigating
Our team is continuing to investigate an upstream service issue affecting our Support phone line. While stability of the service has improved, we have not yet identified the cause of the issue. We will share additional updates as we have more information.
If you are having difficulty reaching us over the phone during this time, please <a href="https://cloud.linode.com/support/tickets?dialogOpen=true">open a Support ticket from the Cloud Manager.</a>
Jun 3, 6:33 PM
investigating
Our team is investigating an upstream emerging service issue affecting our Support phone line due to problems with an upstream provider. We will share additional updates as we have more information.
If you are having difficulty reaching us over the phone during this time, please reach us through a ticket.
Jun 3, 2:22 PM
Service Issue - Block Storage Newark, US
Started: Jun 3, 8:58 AM
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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Jun 3, 3:44 PM
investigating
Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.
Jun 3, 12:55 PM
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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Jun 3, 11:25 AM
investigating
We are continuing to investigate this issue.
Jun 3, 10:53 AM
investigating
Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.
Jun 3, 8:58 AM
Linode Community Maintenance
Started: Jun 2, 1:26 AM
monitoring
At this time we have been able to correct the issue affecting connectivity to Linode.com and the Community Site. We will be monitoring this to ensure that connectivity remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Jun 8, 5:59 PM
identified
We are continuing to work on a fix for this issue.
Jun 2, 1:33 AM
identified
Our team has identified issues with the Community Site (https://www.linode.com/community/questions/). During this time, the page has been moved under maintenance mode. We will share additional updates as we have more information.
Jun 2, 1:26 AM
May 2026
Service Issue - Paris (FR-PAR3)
Started: May 22, 11:22 AM
monitoring
The issue subsided by 11:30 UTC on May 22, 2026, the impact was observed between 09:10 UTC to 11:30 UTC on May 22, 2026. We are actively monitoring to ensure that the service remains stable . If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
May 22, 1:14 PM
investigating
We are continuing to investigate the issue
May 22, 12:24 PM
investigating
We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.
May 22, 11:22 AM
Emerging Service Issue - GPU Deployment
Started: May 19, 7:48 PM
monitoring
At this time we have been able to correct the issues affecting GPU provisioning in all regions as of 21:27 UTC. on May 19th, 2026. 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.
May 19, 9:58 PM
identified
The issue with deployment of RTX PRO 6000 Blackwell plans appears to have started around 15:00 UTC on May 19, 2026. We are actively working to deploy an API hotfix that is expected to be rolled out within 1 hour. We apologize for the impact.
May 19, 9:06 PM
identified
Our team is investigating an emerging service issue affecting GPU provisioning in all regions. At this time deployment of RTX PRO 6000 Blackwell plans in unavailable. We will share additional updates as we have more information.
May 19, 7:48 PM
Emerging Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
Started: May 16, 12:42 AM
identified
The issue has been identified and a fix has been implemented.
May 16, 1:27 AM
investigating
We are continuing to investigate this issue.
May 16, 1:06 AM
investigating
Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.
May 16, 12:42 AM
Investigating - Linode VM Migration Delays (All Regions)
Started: May 15, 2:24 AM
investigating
We are currently investigating an issue causing delays to both cold and live migrations globally. A number of migrations are stuck, and additional migrations are queued and pending across all regions.
Customer Impact: Cold and live migrations along with linode resize may be delayed or unresponsive. We recommend avoiding initiating new migrations and resizes until this is resolved.
We are actively investigating the root cause and will provide an update shortly.
May 15, 2:24 AM
[Fragnesia] Linux Privilege Escalation Vulnerability
Started: May 13, 9:02 PM
investigating
We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.
We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.
[1] h...
Jun 5, 8:24 PM
investigating
We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.
We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.
[1] h...
May 15, 5:30 PM
investigating
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising ...
May 13, 9:02 PM
Connectivity Issue - NL-AMS
Started: May 13, 9:42 AM
monitoring
At this time we have been able to confirm that no customers should be impacted by the issues affecting connectivity in our NL-AMS 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.
May 13, 10:44 AM
investigating
Our team is investigating an issue affecting connectivity in our NL-AMS 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, 9:42 AM
Connectivity Issue - AP-West (Mumbai) and IN-MAA (Chennai)
Started: May 12, 5:12 PM
identified
We are continuing to work with our service provider on a fix for this issue.
May 12, 10:47 PM
identified
Our third-party service provider has identified the issue affecting connectivity in our AP-West (Mumbai) and IN-MAA (Chennai) data centers, and a fix is being implemented. We will provide an update as soon as the solution is in place.
May 12, 7:52 PM
investigating
We are continuing to investigate the issue with our service provider. We will share additional updates as we have more information.
May 12, 5:54 PM
investigating
Our team is investigating an issue affecting connectivity in our AP-West (Mumbai) and IN-MAA (Chennai) data centers. During this time, users may experience intermittent connection timeouts and errors for all services deployed in these data centers. We will share additional updates as we have more information.
May 12, 5:12 PM
[DirtyFrag] Linux Privilege Escalation Vulnerability
Started: May 8, 1:40 PM
investigating
We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.
We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.
[1] h...
Jun 5, 8:23 PM
investigating
We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.
We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.
[1] h...
May 15, 5:28 PM
investigating
We have updated our latest Linode kernel to version 7.0.5, which contains the upstream fix from kernel.org for the DirtyFrag vulnerabilities as well as the previous fixes for the recent CopyFail vulnerability. This kernel is available in Cloud Manager and we recommend customers using the Linode-compiled kernel update their configurations to this kernel. We are in parallel tracking the upstream Linux distributions and will provide another update when fixed versions have been released.
May 9, 2:40 PM
investigating
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distribu...
May 8, 1:40 PM
(Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]
Started: May 1, 5:51 PM
investigating
We are continuing to investigate this issue.
May 1, 5:52 PM
investigating
Akamai is aware of the recently disclosed “Copy Fail” vulnerability (CVE-2026-31431). We are assessing the issue and are working to address it across our product portfolio and internal systems. While we have not observed any related malicious exploits targeting our infrastructure, Akamai continuously works to reduce risks and enhance our security posture. We are taking both immediate and longer-term steps to mitigate potential impacts and help ensure the continued confidence of our custom...
May 1, 5:51 PM
April 2026
Object Storage Key creation and validation failing with error 403 in multiple data centers
Started: Apr 29, 9:22 AM
investigating
We are continuing to investigate this issue.
Apr 29, 12:41 PM
investigating
We are continuing to investigate this issue.
Apr 29, 11:42 AM
investigating
Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.
Apr 29, 10:30 AM
investigating
We are aware that some customers have been experiencing 403 (InvalidAccessKeyId) errors when attempting to access object storage, beginning yesterday evening. We will share additional updates as we have more information.
Apr 29, 9:22 AM
Service Issue - Connectivity Issues - Chennai (IN-MAA)
Started: Apr 28, 5:17 PM
identified
We were able to identify a solution which resulted in additional capacity for the Chennai, IN region and did not experience any degradation over the peak hours on April 29, 2026, we anticipate this to be the case going forward, but will continue providing updates until we successfully replace the impacted network component. The replacement of the network component has been briefly delayed. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in p...
Apr 29, 10:13 PM
identified
Our team has identified the issue affecting connectivity in our Chennai (IN-MAA) data center as a degraded network component and are working to expedite replacement as quickly as possible. At this time there is no customer impact, but due to lessened capacity as a result of this hardware degradation, we do expect intermittent delays or timeouts during peak traffic hours in the Chennai (IN-MAA) region. The current ETA for replacing this hardware is end of day on April 29, 2026. We are working ...
Apr 28, 9:35 PM
identified
Our team is investigating an emerging service issue affecting the network and connectivity in our Chennai (IN-MAA) data center. Customers may see intermittent delays and timeouts during peak traffic hours in the region.
If you are seeing impact that may be related, please <a href="https://cloud.linode.com/support/tickets?dialogOpen=true">open a Support Ticket</a>.
Apr 28, 5:17 PM
Service Issue - Linode Kubernetes Engine (LKE)
Started: Apr 24, 7:27 PM
monitoring
At this time we have been able to correct the issues affecting the NodeBalancer service at 23:36 UTC on April 24, 2026. 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 ticket</a> with our Support Team.
Apr 24, 11:53 PM
identified
We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place.
Apr 24, 11:06 PM
identified
We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place.
Apr 24, 10:07 PM
identified
Our team has identified the issue affecting the LKE and newly updated/created NodeBalancer configurations. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Apr 24, 9:46 PM
identified
Our team has identified that due to this issue, customers may also experience issues creating new nodebalancers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Apr 24, 8:48 PM
identified
Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Apr 24, 8:19 PM
investigating
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine (LKE) service across multiple regions. We will share additional updates as we have more information.
Apr 24, 7:27 PM
Emerging Service Issue - Connectivity issues in Frankfurt (DE-FRA-2)
Started: Apr 20, 11:49 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 20, 1:57 PM
investigating
We are continuing to investigate this issue.
Apr 20, 12:25 PM
investigating
Our team is investigating an emerging service issue impacting connectivity in Frankfurt (DE-FRA-2). We will share additional updates as we have more information.
Apr 20, 11:49 AM
Linode Kubernetes Engine Standard and Enterprise in all regions
Started: Apr 16, 1:20 PM
monitoring
As of 16:27 UTC on April 16, 2026 we have corrected the issues affecting the LKE service. The issue was caused by an expired certificate, which has been updated. 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.
Apr 16, 4:53 PM
identified
As of 15:53 UTC on April 16, 2026 we are starting to see nodes successfully provisioning, however the service is not fully back up yet. Some customers may remain impacted at this time. We are working to stabilize the service, and will provide another update within the next 30 minutes.
Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 4:09 PM
identified
Our team continues to work on implementing a fix for the issue affecting the Linode Kubernetes Engine. We will continue to provide updates until a solution is in place.
Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 3:40 PM
identified
Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 3:10 PM
investigating
Our team continues to investigate the issue affecting the Linode Kubernetes Engine (LKE). We will share additional updates as we have more information.
Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 2:41 PM
investigating
Our team continues to investigate the issue with the Linode Kubernetes Engine. Affected customers may be unable to deploy new clusters or add new nodes to a cluster. We will share additional updates as we have more information.
Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 2:12 PM
investigating
Our team is investigating an emerging service issue affecting Linode Kubernetes Engine Standard and Enterprise in all regions. We will share additional updates as we have more information.
Apr 16, 1:20 PM
Service Issue - Cloud Manager and API
Started: Apr 15, 4:57 PM
monitoring
At this time we have been able to correct the issue affecting the Cloud Manager and API. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.
Apr 15, 6:35 PM
identified
We are continuing to implement a fix, and we will provide an update as soon as the solution is in place.
Apr 15, 6:28 PM
identified
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. During this time, customers may be unable to create new Linodes, make changes to Cloud Firewalls, initiate migrations or resize operations. LKE autoscaling may also be delayed during this time.
Apr 15, 4:57 PM
Service Issue - Dedicated CPU - Several Regions
Started: Apr 14, 6:33 PM
identified
We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May.
Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support.
We will provide additional updates as we approach the deployment date.
Apr 15, 10:40 PM
identified
Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Apr 14, 8:45 PM
investigating
Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.
Apr 14, 6:33 PM
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 months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Jul 3, 1:55 PM
identified
We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
May 26, 9:17 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.
May 13, 8:59 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 15, 3:12 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