Linode Outage History

Started Nov 02, 2026, 06:03 PM UTC· resolved Nov 02, 2026, 08:53 PM UTC

1. investigating Nov 02, 2026, 06:03 PM UTC

   Our team is investigating an issue affecting connectivity in our FR-PAR-2 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.

2. investigating Nov 02, 2026, 06:18 PM UTC

   We are continuing to investigate the issue.

3. resolved Nov 02, 2026, 08:53 PM UTC

   We haven’t observed any additional connectivity issues in our FR-PAR-2 data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Started Nov 01, 2026, 04:40 PM UTC· resolved Nov 01, 2026, 07:52 PM UTC

1. investigating Nov 01, 2026, 04:40 PM UTC

   Our team is investigating an issue affecting connectivity in our IN-MAA (Chennai) and IN-BOM-2 (Mumbai 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.

2. monitoring Nov 01, 2026, 05:23 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Nov 01, 2026, 07:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 31, 2026, 05:49 PM UTC· resolved Nov 02, 2026, 06:00 PM UTC

1. investigating Oct 31, 2026, 05:49 PM UTC

   We are investigating an emerging service issue affecting US-Southeast (Atlanta), related to an increasing number of host failures, resulting in compute instances being unable to boot. We will share additional updates as we have more information.

2. investigating Oct 31, 2026, 07:03 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 31, 2026, 08:17 PM UTC

   We are continuing to investigate the issue. We will share additional details as soon as we have them.

Read the full incident report →

Started Oct 23, 2026, 09:21 AM UTC· resolved Oct 23, 2026, 08:38 PM UTC

1. investigating Oct 23, 2026, 09:21 AM UTC

   Our team is currently investigating a connectivity issue in our Dallas data center. This is strictly affecting traffic routed via IPv6 to Google and its associated products, which may cause intermittent connection timeouts. We will post further updates as soon as more information becomes available.

2. monitoring Oct 23, 2026, 04:32 PM UTC

   This was identified to be an upstream issue and should be resolved at this time, we will continue to monitor to ensure things remain stable.

3. resolved Oct 23, 2026, 08:38 PM UTC

   This issue is considered resolved.

Read the full incident report →

Started Oct 22, 2026, 11:10 AM UTC· resolved Oct 22, 2026, 12:50 PM UTC

1. resolved Oct 22, 2026, 01:58 PM UTC

   Our team identified an issue affecting the Linode Kubernetes Engine (LKE). During the impact timeframe (~11:10-12:50 UTC), new worker nodes were unable to provision. We have been able to correct the issues affecting the LKE service and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

2. postmortem Oct 22, 2026, 04:00 PM UTC

   On October 22, 2026, starting around 11:10 UTC, a new Debian Kubernetes image was made available. The metadata for that image included malformed data, which resulted in Linode provisioning failures on LKE clusters due to validation errors. Akamai immediately began investigating the issue and working to correct it. We corrected the malformed data at 12:50 UTC on October 22, 2026 and service was restored. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Read the full incident report →

Started Oct 21, 2026, 02:44 PM UTC· resolved Oct 23, 2026, 08:37 PM UTC

1. investigating Oct 21, 2026, 02:44 PM UTC

   Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, some Quick Deploy Apps, speed test pages, and parts of the website may be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.

2. identified Oct 21, 2026, 05:41 PM UTC

   Updated Guidance after assessment: Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.

3. identified Oct 22, 2026, 06:19 PM UTC

   Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.

4. resolved Oct 23, 2026, 08:37 PM UTC

   Akamai has completed its assessment of the recently published PHP remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across our platform and infrastructure, and mitigation efforts are complete. Cloud Infrastructure Speed Tests will remain offline in the near term. We plan to bring them back online in the near future. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We appreciate your patience while our teams completed this work.

5. postmortem Oct 29, 2026, 08:40 AM UTC

   On October 10, 2026, Akamai became aware of two zero-day remote code execution \(RCE\) vulnerabilities affecting the PHP core engine, tracked as CVE-2026-109618 and CVE-2026-109619. Akamai began a platform-wide investigation, and deployed global Web Application Firewall \(WAF\) mitigation rules on October 21, 2026, and carried out remediation protocols across potentially impacted infrastructure. At this time, Akamai has observed no evidence that these vulnerabilities impacted core Akamai products, API calls, or the Akamai Control Center \(ACC\). The potential scope included PHP Core, Linode Speed Test Services, and Quick Deploy Marketplace applications. As a precaution, Akamai temporarily disabled Cloud Infrastructure Speed Tests while teams isolated and rebuilt related systems. Akamai deployed protective WAF rules across the Akamai edge platform to inspect and mitigate potential exploitation attempts. Marketplace application templates were also updated so new Linode Compute Marketplace deployments automatically use patched PHP packages. The existing customer-managed instances running vulnerable PHP versions require customer action to apply the latest official security updates from the upstream PHP project. Customers using Akamai App & API Protector or Kona Site Defender should confirm that default protective rule sets are active. Customers running PHP on Linode compute instances or other self-managed infrastructure should update PHP packages as soon as possible. The external asset scans confirmed that Akamai production environments remained secured and protected. Akamai's public security notice is available [here](https://www.akamai.com/blog/security-research/critical-remote-code-execution-vulnerabilities-php-core). This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Read the full incident report →

Started Oct 20, 2026, 12:29 PM UTC· resolved Oct 20, 2026, 09:42 PM UTC

1. identified Oct 20, 2026, 12:29 PM UTC

   We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.

2. identified Oct 20, 2026, 12:33 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Oct 20, 2026, 12:34 PM UTC

   We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.

4. identified Oct 20, 2026, 02:06 PM UTC

   Our team has identified the issue affecting the LKE Enterprise service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

5. resolved Oct 20, 2026, 09:42 PM UTC

   We haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

6. postmortem Oct 21, 2026, 03:49 PM UTC

   Starting October 17, 2026, customers were unable to create new Linode Kubernetes Engine-Enterprise \(LKE-E\) clusters globally. The impact was limited to newly provisioned LKE-E clusters, while the existing clusters, ongoing customer workloads, and cluster scaling remained fully functional and were unaffected throughout the event. Investigation revealed that the impact occurred after Linode Virtual Private Cloud \(VPC\) subnet IDs crossed 1,000,000 \(one million\), following growth on October 17, 2026. Due to a software logic flaw, the Cloud Controller Manager parsed these 7-digit IDs into scientific notation instead of raw integers, rendering the IDs invalid and causing required core components to remain pending on newly created clusters. To mitigate the issue, Akamai deployed a fix to enforce strict integer formatting and patched existing custom resources to restore the affected clusters. Akamai’s internal testing confirmed that the newly provisioned test clusters were fully operational. With the successful testing, Akamai deployed the fix across the platform, and the impact was considered mitigated at around 19:49 UTC on October 20, 2026. Akamai is working on the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. This summary reflects our current understanding of the incident based on available details. Our investigation remains ongoing, and findings may be updated as further information is reviewed.

Read the full incident report →

Started Oct 19, 2026, 02:49 PM UTC· resolved Oct 19, 2026, 08:33 PM UTC

1. investigating Oct 19, 2026, 02:49 PM UTC

   Our team has identified an issue affecting connectivity in our Chicago (US-ORD) 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.

2. monitoring Oct 19, 2026, 03:29 PM UTC

   At this time we have been able to correct the issues affecting connectivity in our Chicago (US-ORD) 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.

3. resolved Oct 19, 2026, 08:33 PM UTC

   We haven’t observed any additional connectivity issues in our Chicago (US-ORD) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

4. postmortem Oct 26, 2026, 07:33 PM UTC

   Beginning at approximately 14:23 UTC on October 19, 2026, as part of a planned internal maintenance, we migrated too many of the same routing resources at the same time. This resulted in route instability in certain network segments until the migration completed and routes were adopted and converged at 14:55 UTC on October 19, 2026. To prevent this issue from reoccurring, we are modifying our maintenance planning process to ensure that critical components are taken offline in a phased manner that doesn’t introduce customer impact. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Oct 15, 2026, 05:27 PM UTC· resolved Oct 30, 2026, 03:06 PM UTC

1. identified Oct 15, 2026, 05:27 PM UTC

   Akamai is aware of the recently published Guest-to-Host KVM Escape (CVE-2026-99999) vulnerability. Our teams have proactively identified its potential impact and are actively applying mitigations across our platform and infrastructure. There is potential for customer workload impact as a part of our platform response to this vulnerability. At this time, we have not observed evidence of this vulnerability being actively exploited on our platform. We will provide updates as additional information becomes available.

2. identified Oct 16, 2026, 08:53 AM UTC

   We have not identified any exploitation on the Akamai platform so far. As of now, our subject matter experts are continuing to work on patching server sets in phases across the Akamai platform. We are actively monitoring our platform while we perform the mitigation actions.

3. identified Oct 17, 2026, 05:07 AM UTC

   Akamai has completed patching Compute hypervisors for the known vulnerabilities related to CVE-2026-99999, also referred to as “PwnEscape”, and we have not identified any exploitation on the Akamai platform. We recommend that customers upgrade Linode guest VMs using kernels from upstream OS vendors as those become available, especially for cases where less trusted workloads are being run within containers or nested virtualization. We are in the process of preparing images containing fixes from upstream vendors.

4. resolved Oct 30, 2026, 03:06 PM UTC

   We have completed our investigation and response to the “PwnEscape” Guest-to-Host Escape vulnerability (CVE-2026-99999). We have published a documentation article with detailed guidance on available mitigations and recommended actions for affected systems: https://www.akamai.com/cloud/guides/cve-2026-99999-pwnescape-mitigation/ We encourage all customers to review the article and apply the appropriate mitigations to their environments. If you have questions or need assistance, please open a Support ticket, or contact us at 855-454-6633 (+1-609-380-7100 Intl.) / [email protected].

Read the full incident report →

Started Oct 09, 2026, 03:43 AM UTC· resolved Oct 13, 2026, 08:03 AM UTC

1. identified Oct 09, 2026, 03:43 AM UTC

   Our team has identified the issue affecting Cloud Manager logins, where customers may not receive verification codes in some scenarios. We are working quickly to implement a fix and will provide an update as soon as the solution is in place.

2. monitoring Oct 09, 2026, 05:23 AM UTC

   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 receive verification codes please open a Support ticket, call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].

3. resolved Oct 13, 2026, 08:03 AM UTC

   We haven't observed any additional issues with the Cloud Manager logins, and will now consider this incident resolved. If you continue to experience issues receiving verification codes, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Read the full incident report →

Started Oct 02, 2026, 04:01 PM UTC· resolved Oct 02, 2026, 08:17 PM UTC

1. investigating Oct 02, 2026, 04:01 PM UTC

   Our team is investigating an issue affecting the Object Storage for the US-Southeast (Atlanta) region. During this time, users may experience connection timeouts and errors with this service.

2. monitoring Oct 02, 2026, 04:59 PM UTC

   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.

3. resolved Oct 02, 2026, 08:17 PM UTC

   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.

Read the full incident report →

Started Sep 25, 2026, 03:09 PM UTC· resolved Sep 25, 2026, 04:21 PM UTC

1. investigating Sep 25, 2026, 03:09 PM UTC

   Our team is investigating a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users may experience issues when attempting to access these systems. We will share additional updates as we have more information.

2. resolved Sep 25, 2026, 04:21 PM UTC

   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 [email protected] for assistance.

Read the full incident report →

Started Sep 21, 2026, 05:13 PM UTC· resolved Sep 23, 2026, 03:26 AM UTC

1. investigating Sep 21, 2026, 05:13 PM UTC

   Our team is investigating an emerging service issue intermittently affecting Cloud Manager and API. We will share additional updates as we have more information.

2. resolved Sep 23, 2026, 03:26 AM UTC

   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 [email protected] for assistance.

Read the full incident report →

Started Sep 21, 2026, 04:50 PM UTC· resolved Sep 22, 2026, 12:04 AM UTC

1. investigating Sep 21, 2026, 04:50 PM UTC

   Our team is investigating an emerging service issue affecting our DNS service in the London 1 (EU-West) region. We will share additional updates as we have more information.

2. identified Sep 21, 2026, 06:41 PM UTC

   Our team has identified the issue affecting our DNS service in the London 1 (EU-West) region. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

3. identified Sep 21, 2026, 08:07 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Sep 21, 2026, 09:15 PM UTC

   We are continuing to work on a fix for this issue.

5. monitoring Sep 21, 2026, 10:06 PM UTC

   At this time 21:45 UTC September 21st, 2026 we have been able to correct the issue affecting our DNS service in the London 1 (EU-West) region. We will be monitoring this to ensure that connectivity remains stable. Customers can apply this fix by enabling Network Helper (https://techdocs.akamai.com/cloud-computing/docs/automatically-configure-networking) and rebooting the effected Linode or please open a ticket with our Support Team.

6. resolved Sep 22, 2026, 12:04 AM UTC

   This incident has been resolved.

7. postmortem Sep 24, 2026, 05:45 PM UTC

   On September 21, 2026, starting at approximately 16:10 UTC, Akamai observed degraded DNS resolution performance affecting a subset of Linode instances within the London \(`LON1`\) region. Platform-wide DNS resolution remained functional, and no other regions were affected. The disruption occurred during a drive transplant of a compute host at the London \(lon1\) data center, which temporarily took a customer-facing DNS resolver offline. Due to a software logic flaw, customer workload configurations deployed in the last year across the region were disproportionately reliant on this single resolver, causing DNS failures when it became unavailable. At 21:45 UTC, engineering teams deployed an emergency configuration update to rebalance and reorder active DNS resolver assignments in the region, returning DNS query performance to baseline levels. Post-remediation monitoring confirmed stable operations across `LON1`. Long-term engineering updates are currently being deployed to ensure provisioning utilities dynamically assign distinct, active DNS resolvers across all regions to prevent recurrence. This summary reflects our current understanding of the incident based on available details. Our investigation remains ongoing, and findings may be updated as further information is reviewed.

Read the full incident report →

Started Sep 07, 2026, 10:38 AM UTC· resolved Sep 07, 2026, 01:31 PM UTC

1. investigating Sep 07, 2026, 10:38 AM UTC

   Our team is investigating a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users may experience issues when attempting to access these systems. We will share additional updates as we have more information.

2. investigating Sep 07, 2026, 11:39 AM UTC

   We are continuing to investigate this issue.

3. investigating Sep 07, 2026, 12:12 PM UTC

   We are continuing to investigate this issue.

4. monitoring Sep 07, 2026, 01:27 PM UTC

   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 open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].

5. resolved Sep 07, 2026, 01:31 PM UTC

   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 [email protected] for assistance.

6. postmortem Sep 08, 2026, 09:26 AM UTC

   Between approximately 10:15 and 12:18 UTC on September 7, 2026, customers could have experienced elevated error rates and 5xx response codes when using Cloud Manager or performing API calls. The investigation revealed that the issue started due to increased API load that over-utilized our database resources which in turn led to the symptoms seen by users. To mitigate the issue, the team addressed the elevated API load issue which brought back utilization of our resources within normal ranges. Ongoing actions include monitoring platform stability, and planning enhancements to API rate limiting. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Aug 28, 2026, 10:26 AM UTC· resolved Aug 28, 2026, 05:44 PM UTC

1. investigating Aug 28, 2026, 10:26 AM UTC

   We are investigating an emerging service issue affecting us-sea (Seattle, WA). We will share additional updates as we have more information.

2. investigating Aug 28, 2026, 11:39 AM UTC

   We are continuing to investigate the issue. We will share additional details as soon as we have them.

3. investigating Aug 28, 2026, 12:15 PM UTC

   Our team is investigating the issue where users may experience host unreachability, failures with all Linode control plane operations, including, but not limited to: node creation and deletion, attaching or detaching Block Storage. The issue appears to have started around 09:45 UTC on August 28, 2026. We will share additional updates as we have more information.

4. monitoring Aug 28, 2026, 12:45 PM UTC

   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.

5. monitoring Aug 28, 2026, 12:48 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Aug 28, 2026, 05:44 PM UTC

   We haven't observed any additional issues with Linode control plane operations and will now consider this incident resolved. If you are still experiencing additional issues, please open a Support ticket for assistance.

7. postmortem Aug 28, 2026, 08:36 PM UTC

   Between approximately 09:51 and 12:18 UTC on August 28, 2028, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected. The investigation revealed that this was due to a Linux kernel issue that was triggered on a network router due to increased network traffic at this site while a specific BIOS setting was enabled. This caused system instability and affected job processing in the US-SEA region. To mitigate the impact, the Akamai team disabled a problematic setting and rebooted the affected system, restoring service and moving the situation to a monitoring state by 12:18 UTC on August 28, 2026. As preventive actions, Akamai will audit hardware configurations to ensure the problematic feature is explicitly disabled, and implement enhanced monitoring to detect similar issues in the future. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Aug 24, 2026, 09:52 PM UTC· resolved Aug 25, 2026, 01:11 AM UTC

1. investigating Aug 24, 2026, 09:52 PM UTC

   Our team is investigating an issue affecting the Object Storage service in US-SEA. During this time, users may experience intermittent 5xx errors with this service.

2. investigating Aug 24, 2026, 11:11 PM UTC

   We are continuing to investigate this issue.

3. investigating Aug 25, 2026, 12:31 AM UTC

   We are continuing to investigate this issue.

4. identified Aug 25, 2026, 12:55 AM UTC

   The issue has been identified and a fix is being implemented.

5. resolved Aug 25, 2026, 01:11 AM UTC

   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.

Read the full incident report →

Started Aug 21, 2026, 05:23 PM UTC· resolved Aug 21, 2026, 09:59 PM UTC

1. investigating Aug 21, 2026, 05:23 PM UTC

   Our team is investigating an emerging service issue affecting us-sea (Seattle, WA). We will share additional updates as we have more information.

2. resolved Aug 21, 2026, 09:59 PM UTC

   At this time we have been able to correct the issue and the service has resumed normal operation.

3. postmortem Sep 07, 2026, 06:36 PM UTC

   On August 21, 2026 starting approximately at 17:23 UTC, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected. The investigation revealed that this was due to a Linux kernel issue that was triggered on a network router due to increased network traffic at this site while a specific BIOS setting was enabled. This caused system instability and affected job processing in the US-SEA region. To mitigate the impact, the Akamai team disabled a problematic setting and rebooted the affected system, restoring service and moving the situation to a monitoring state by 21:59 UTC on August 21, 2026. As preventive actions, Akamai will audit hardware configurations to ensure the problematic feature is explicitly disabled, and implement enhanced monitoring to detect similar issues in the future. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Aug 14, 2026, 08:13 PM UTC· resolved Aug 14, 2026, 09:30 PM UTC

1. investigating Aug 14, 2026, 08:13 PM UTC

   Our team is investigating an issue affecting connectivity in our IT-MIL (Milan) 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.

2. investigating Aug 14, 2026, 09:18 PM UTC

   We are continuing to investigate this issue. We will share additional updates as we have more information.

3. resolved Aug 14, 2026, 09:30 PM UTC

   We haven’t observed any additional connectivity issues in our IT-MIL (Milan) data center and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

4. postmortem Aug 18, 2026, 07:02 PM UTC

   On August 14, 2026, starting around 17:30 UTC, during an event in our IT-MIL \(Milan\) data center, multiple alerts were triggered indicating that multiple hosts in this data center became unreachable. ‌ Akamai immediately began investigating the issue and working to restore the impacted hosts. During the impact window, customers would have experienced intermittent connection timeouts and errors across all services deployed in this data center. ‌ We restored the impacted hosts and fixed the connectivity issues at 21:20 UTC on August 14, 2026. We are still investigating the cause of the failure condition. ‌ We are committed to preventing future incidents and will conduct a thorough investigation into why the hosts became unreachable, implementing measures to enhance stability and reliability. ‌ This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Read the full incident report →

Started Aug 13, 2026, 09:13 PM UTC· resolved Aug 13, 2026, 11:24 PM UTC

1. investigating Aug 13, 2026, 09:13 PM UTC

   Our team is investigating an issue affecting creation of Linode Kubernetes Engine Enterprise (LKE-E) clusters in the IAD2 - Washington data center. This is a continuation of the issue reported earlier. We will share additional updates as we have more information.

2. monitoring Aug 13, 2026, 11:02 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 13, 2026, 11:24 PM UTC

   This incident has been resolved.

4. postmortem Aug 18, 2026, 08:32 PM UTC

   Between 17:25 UTC and 22:50 UTC on August 13, 2026, Linode Kubernetes Engine Enterprise \(LKE-E\) customers attempting to deploy G7 dedicated Linode instances in our Washington \(IAD2\) data center, received 403 provisioning error messages. Active workloads and running instances were not affected by this issue. Our investigation revealed that while total physical hardware capacity in IAD2 was sufficient, the provisioning request triggered an entitlement check failure due to an initial soft host-allocation threshold. Akamai resolved the issue by increasing the Linode-per-host limit from 5 to 20 in IAD2. Full deployment capabilities were restored and stabilized at 22:50 UTC. To prevent recurrence moving forward, we will implement dedicated alerting for entitlement and capacity issues, directly linked to response runbooks for rapid remediation. Additionally, we are building a centralized capacity overview dashboard to proactively track regional headroom. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Aug 13, 2026, 06:46 PM UTC· resolved Aug 14, 2026, 12:26 AM UTC

1. investigating Aug 13, 2026, 06:46 PM UTC

   Our team is investigating an emerging service issue affecting the API in all regions. We will share additional updates as we have more information.

2. monitoring Aug 13, 2026, 07:58 PM UTC

   As of 19:30 UTC have been able to correct the issue affecting API in all regions. We will be monitoring this to ensure that the service remains stable. 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 [email protected].

3. monitoring Aug 13, 2026, 07:59 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Aug 14, 2026, 12:26 AM UTC

   This incident has been resolved.

5. postmortem Aug 17, 2026, 05:38 PM UTC

   On August 13th, 2026, at approximately 18:15 UTC, Akamai observed a brief service outage affecting [_api.linode.com_](http://api.linode.com). The total service interruption lasted for approximately 3 minutes, concluding at 18:18 UTC. Following the restoration of initial connectivity, elevated API response latency persisted through 19:06 UTC, causing slower response times and intermittent delays for customers interacting with API services. To address the performance impact, Akamai engineering teams identified a configuration discrepancy on the secondary caching infrastructure node that prevented it from absorbing the full traffic load after the failover. Engineers completed a controlled migration and moved request caching traffic back over to the primary host. Following this change, API latency rapidly decreased to normal operational levels. The initial condition was triggered by an unexpected reboot of the primary caching node's physical host. While redundant infrastructure was active, the secondary node was unable to process the failover traffic seamlessly, causing the extended performance degradation. Our engineering teams are conducting a follow-up investigation into the failover mechanisms to optimize execution speeds and align configuration settings across redundant nodes, ensuring secondary systems can handle traffic seamlessly in future events. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Aug 13, 2026, 04:16 PM UTC· resolved Aug 13, 2026, 05:54 PM UTC

1. investigating Aug 13, 2026, 04:16 PM UTC

   Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). We will share additional updates as we have more information.

2. monitoring Aug 13, 2026, 04:30 PM UTC

   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.

3. resolved Aug 13, 2026, 05:54 PM UTC

   We haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

4. postmortem Aug 17, 2026, 09:30 PM UTC

   Beginning at approximately 14:50 UTC on August 13, 2026, customers who attempted to provision Linode Kubernetes Engine Enterprise \(LKE-E\) clusters in the IAD2 data center were unable to. We identified that the issue was due to the exclusion of two components in IAD2 in a recent software version upgrade which resulted in an API mismatch. We updated the identified components to bring them in sync with the expected state. This mitigated the issue at approximately 16:00 UTC on August 13, 2026. To prevent this issue from occurring in the future, we are reviewing LKE software update processes to ensure that all included components complete version upgrades before being reintroduced to service during platform software updates. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Aug 13, 2026, 02:30 PM UTC· resolved Aug 13, 2026, 02:45 PM UTC

1. resolved Aug 13, 2026, 02:00 PM UTC

   On August 13, 2026, between approximately 14:00-16:30 UTC, we observed intermittent failures and delays when provisioning new LKE-E clusters in the Seattle (SEA1) region. The issue affecting the LKE-E service in Seattle self-corrected at approximately 16:30 UTC, and we have not observed a recurrence since. We are actively investigating the cause. We will continue to monitor the service for stability. If you experience any problems with this service, please open a Support ticket for assistance.

2. postmortem Aug 21, 2026, 01:13 PM UTC

   On August 13, 2026, between approximately 14:30 and 16:30 UTC, Akamai experienced an issue affecting Linode Kubernetes Engine Enterprise \(LKE-E\) cluster provisioning and deployment in the Seattle \(SEA1\) region. During this time, customers attempting to create new clusters encountered failures or delays. In some cases, clusters were created but nodes were not fully provisioned, while in others, the control plane responsible for managing the cluster could not be deployed. Akamai identified the issue through customer reports, which was then validated by reproducing the failures in Seattle-based test clusters. Other regions continued to operate normally, and no existing customer workloads were impacted. By around 16:30 UTC on August 13, 2026, cluster provisioning and deployment in the Seattle region returned to normal, allowing new cluster creations to proceed without issue. After recovery, we monitored the region for several days and began a technical investigation into the service disruption. Initial findings indicate a correlation between the issue and a recent network configuration update that occurred at approximately 14:30 UTC and was rolled back at approximately 14:45 UTC. Our current hypothesis suggests that a timing conflict during the cluster provisioning process may have triggered the failures. We are continuing to investigate the technical details to confirm the root cause. We are continuing to investigate the technical details behind this issue and are working to ensure it does not recur. We will also review the scope of affected data centers and track corrective actions. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started Aug 10, 2026, 05:15 PM UTC· resolved Aug 21, 2026, 06:40 PM UTC

1. investigating Aug 10, 2026, 05:15 PM UTC

   Our team is investigating an upstream issue impacting Ubuntu deployments. This may impact the ability to install package and security updates on all Ubuntu systems.

2. investigating Aug 11, 2026, 11:35 PM UTC

   We are continuing to investigate this issue. The appropriate subject matter experts are engaged. Subsequent updates around mitigation status will be posted as progress is made.

3. identified Aug 12, 2026, 03:29 AM UTC

   We have identified the cause of the issue, and a fix is being implemented. We will provide an update as soon as the solution is in place.

4. resolved Aug 21, 2026, 06:40 PM UTC

   We can confirm that the issue was mitigated at 06:30 UTC on August 20, 2026 and the service has resumed normal operations.

Read the full incident report →

Started Jul 31, 2026, 05:49 PM UTC· resolved Aug 05, 2026, 01:34 AM UTC

1. investigating Jul 31, 2026, 05:49 PM UTC

   Our team is investigating packet loss on some paths from the in-maa & in-bom-2 data centers into the US region. During this time, users may experience connection timeouts and errors with services traversing between India and United States regions. We will share additional updates as we have more information.

2. identified Jul 31, 2026, 06:25 PM UTC

   Our team has identified the cause of packet loss to our US data centers. We are working with our upstream provider to resolve this issue and we will provide an update as soon as the solution is in place.

3. identified Aug 04, 2026, 06:36 PM UTC

   We are continuing to work with our upstream provider to resolve the packet loss affecting some paths between the in-maa and in-bom-2 data centers and the US region. We will share further updates as progress continues.

4. resolved Aug 05, 2026, 01:34 AM UTC

   At this time the upstream provider has been able to correct the issue causing packet loss on some routes from the in-maa & in-bom-2 data centers into the US region and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

5. postmortem Aug 05, 2026, 05:49 PM UTC

   On July 31, 2026, at approximately 10:00 UTC, Akamai observed intermittent network losses affecting compute users accessing US locations from our India sites \(MAA and BOM\). Customers’ services in North America, particularly the Miami data center region, experienced increased latency, intermittent connectivity issues, slower data transfers, and difficulty reaching certain applications or services. Performance was unstable, with periods of normal operation followed by disruptions. To address the issue, Akamai applied a deny-all policy to the impacted upstream provider transit link, redirecting traffic around the impacted routes. Despite this mitigation, ongoing IPv6 losses occurred due to congestion between two alternative upstream providers, impacting some users. One provider acknowledged a bottleneck in the Asia region, and the alternate provider worked to reroute traffic away from affected links. The initial impacted service provider confirmed that two fiber cuts in Mexico caused congestion on the impacted routes. One of these fiber cuts was resolved at 23:43 UTC on July 31, 2026, and no further issues were observed following this mitigation. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →