Linode

Names an upstream provider: Akamai.

Started during Akamai: Customer Security Advisory: PHP Remote Code Execution Vulnerabilities.

Started during Akamai: NetStorage issues in Los Angeles.

1. investigating 2026-10-21 14:44 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...

2. identified 2026-10-21 17:41 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine, US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR (Paris) Linode Kubernetes Engine, AP-South (Singapore) Linode Kubernetes Engine, AP-Northeast (Tokyo 2) Linode Kubernetes Engine, AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney) Linode Kubernetes Engine, SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle) Linode Kubernetes Engine, JP-OSA (Osaka) Linode Kubernetes Engine, IN-MAA (Chennai) Linode Kubernetes Engine, ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo) Linode Kubernetes Engine, NL-AMS (Amsterdam) Linode Kubernetes Engine, ES-MAD (Madrid) Linode Kubernetes Engine, IT-MIL (Milan) Linode Kubernetes Engine, US-MIA (Miami) Linode Kubernetes Engine, US-LAX (Los Angeles) Linode Kubernetes Engine, GB-LON (London 2) Linode Kubernetes Engine, AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. identified 2026-10-20 12:29 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...

2. identified 2026-10-20 12:33 UTC

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

3. identified 2026-10-20 12:34 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...

4. identified 2026-10-20 14:06 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 2026-10-20 21:42 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 2026-10-21 15:49 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-ORD (Chicago)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 14:49 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...

2. monitoring 2026-10-19 15:29 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 2026-10-19 20:33 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.

Excerpts are shortened. Read the full incident on Linode's status page.

Names an upstream provider: Akamai.

1. identified 2026-10-15 17:27 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...

2. identified 2026-10-16 08:53 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 2026-10-17 05:07 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-10-15 17:15 UTC

   We are performing maintenance on the Akamai Cloud Login service. During this maintenance, new customer signup and account creation are temporarily disabled. Existing customers accounts are not affected and will be able to log in normally.

2. resolved 2026-10-16 12:20 UTC

   The maintenance has been completed. New customer signup and account creation are fully restored.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-09 03:43 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 2026-10-09 05:23 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...

3. resolved 2026-10-13 08:03 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-Southeast (Atlanta) Object Storage

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 16:01 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 2026-10-02 16:59 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 2026-10-02 20:17 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.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 15:09 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 2026-09-25 16:21 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 support@linode.com for assistance.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), Cloud Manager and API, US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-IAD (Washington), US-ORD (Chicago), CA-Central (Toronto), EU-West (London), EU-Central (Frankfurt), FR-PAR (Paris), AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-Southeast (Sydney), SE-STO (Stockholm), US-SEA (Seattle), IT-MIL (Milan), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta), BR-GRU (São Paulo), NL-AMS (Amsterdam), US-MIA (Miami), US-LAX (Los Angeles), ES-MAD (Madrid), AU-MEL (Melbourne), GB-LON (London 2), IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2), JP-TYO-3 (Tokyo 3), ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 17:13 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 2026-09-23 03:26 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 support@linode.com for assistance.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Hosted DNS Service

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-09-21 16:50 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 2026-09-21 18:41 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 2026-09-21 20:07 UTC

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

4. identified 2026-09-21 21:15 UTC

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

5. monitoring 2026-09-21 22:06 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...

6. resolved 2026-09-22 00:04 UTC

   This incident has been resolved.

7. postmortem 2026-09-24 17:45 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-07 10:38 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 2026-09-07 11:39 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-07 12:12 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-09-07 13:27 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...

5. resolved 2026-09-07 13:31 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 support@linode.com for assistance.

6. postmortem 2026-09-08 09:26 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Linode.com, US-SEA (Seattle)

Failure mode: A zone, region or data center became unavailable. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-08-28 10:26 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 2026-08-28 11:39 UTC

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

3. investigating 2026-08-28 12:15 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...

4. monitoring 2026-08-28 12:45 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 2026-08-28 12:48 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-08-28 17:44 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 2026-08-28 20:36 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-SEA (Seattle) Object Storage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-24 21:52 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 2026-08-24 23:11 UTC

   We are continuing to investigate this issue.

3. investigating 2026-08-25 00:31 UTC

   We are continuing to investigate this issue.

4. identified 2026-08-25 00:55 UTC

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

5. resolved 2026-08-25 01:11 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.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-SEA (Seattle)

Failure mode: A zone, region or data center became unavailable. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-08-21 17:23 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 2026-08-21 21:59 UTC

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

3. postmortem 2026-09-07 18:36 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: IT-MIL (Milan)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-08-14 20:13 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...

2. investigating 2026-08-14 21:18 UTC

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

3. resolved 2026-08-14 21:30 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 2026-08-18 19:02 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-IAD (Washington) Linode Kubernetes Engine

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

Started during Akamai: Connection drops and increased latency in Miami.

1. investigating 2026-08-13 21:13 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 2026-08-13 23:02 UTC

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

3. resolved 2026-08-13 23:24 UTC

   This incident has been resolved.

4. postmortem 2026-08-18 20:32 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-08-13 18:46 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 2026-08-13 19:58 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...

3. monitoring 2026-08-13 19:59 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-08-14 00:26 UTC

   This incident has been resolved.

5. postmortem 2026-08-17 17:38 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-IAD (Washington) Linode Kubernetes Engine

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 16:16 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 2026-08-13 16:30 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 2026-08-13 17:54 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 2026-08-17 21:30 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. resolved 2026-08-13 14:00 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...

2. postmortem 2026-08-21 13:13 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-10 17:15 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 2026-08-11 23:35 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 2026-08-12 03:29 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 2026-08-21 18:40 UTC

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

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-IAD (Washington), US-ORD (Chicago), US-SEA (Seattle), IN-MAA (Chennai), US-MIA (Miami), US-LAX (Los Angeles), IN-BOM-2 (Mumbai 2), US-DEN (Denver), US-HOU (Houston), US-IAD-2 (Washington 2)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-07-31 17:49 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...

2. identified 2026-07-31 18:25 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 2026-08-04 18:36 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 2026-08-05 01:34 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...

5. postmortem 2026-08-05 17:49 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...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark) Block Storage, US-Central (Dallas) Block Storage, US-West (Fremont) Block Storage, US-Southeast (Atlanta) Block Storage, US-IAD (Washington) Block Storage, US-ORD (Chicago) Block Storage, CA-Central (Toronto) Block Storage, EU-West (London) Block Storage, EU-Central (Frankfurt) Block Storage, FR-PAR (Paris) Block Storage, AP-South (Singapore) Block Storage, AP-Northeast-2 (Tokyo 2) Block Storage, AP-West (Mumbai) Block Storage, AP-Southeast (Sydney) Block Storage, SE-STO (Stockholm) Block Storage, US-SEA (Seattle) Block Storage, JP-OSA (Osaka) Block Storage, IN-MAA (Chennai) Block Storage, BR-GRU (São Paulo) Block Storage, NL-AMS (Amsterdam) Block Storage, ES-MAD (Madrid) Block Storage, IT-MIL (Milan) Block Storage, US-MIA (Miami) Block Storage, ID-CGK (Jakarta) Block Storage, US-LAX (Los Angeles) Block Storage, GB-LON (London 2) Block Storage, AU-MEL (Melbourne) Block Storage, IN-BOM-2 (Mumbai 2) Block Storage, DE-FRA-2 (Frankfurt 2) Block Storage, SG-SIN-2 (Singapore 2) Block Storage, JP-TYO-3 (Tokyo 3) Block Storage

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-07-28 18:14 UTC

   Our team is investigating an issue affecting the Block Storage service in several data center regions. This issue largely impacts attaching and detaching Block Storage volumes. During this time, users may experience volume attach/detach hangs, timeouts and errors with this...

2. identified 2026-07-28 19:27 UTC

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

3. identified 2026-07-28 20:17 UTC

   We would like to update that after additional investigation, the impact would manifest in delayed and sometimes failed host jobs, which could include many different actions on Linodes and not only impacting attaching and detaching Block Storage volumes as we mentioned in our...

4. monitoring 2026-07-28 22:51 UTC

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

5. resolved 2026-07-29 12:27 UTC

   We haven’t observed any additional host jobs performance degradation issues, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

6. postmortem 2026-07-31 18:57 UTC

   On 27 July 2026 at 3:30 UTC, Akamai observed an increase in errors when connecting to the Linode hosting database, primarily affecting Block Storage volume attachments. This resulted in host job failures and limited customer impact, with some users experiencing error messages...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: IT-MIL (Milan)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-20 01:52 UTC

   Our team is currently investigating a connectivity issue affecting Linodes in the Italy (Milan) region. During this time, existing Linodes in this location may be unreachable. Please note that creating new Linodes is functioning normally and remains unaffected.

2. investigating 2026-07-20 02:56 UTC

   We are continuing to investigate this issue. We will provide the next update as we make progress.

3. investigating 2026-07-20 03:12 UTC

   Our team has identified the issue affecting connectivity in our Milan (Italy) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

4. monitoring 2026-07-20 03:20 UTC

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

5. resolved 2026-07-20 04:10 UTC

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

6. postmortem 2026-07-20 05:45 UTC

   Starting around 00:33 UTC on July 20, 2026, some hosts in the Milan, Italy data center became unavailable, impacting customer access to Linodes. The investigation identified that this issue occurred during scheduled router firmware updates. While we follow a phased upgrade...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-IAD (Washington) Object Storage, US-ORD (Chicago) Object Storage, FR-PAR (Paris) Object Storage, US-SEA (Seattle) Object Storage, US-LAX (Los Angeles) Object Storage

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-18 03:34 UTC

   Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.

2. identified 2026-07-18 03:54 UTC

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

3. resolved 2026-07-18 04:36 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.

4. postmortem 2026-07-21 15:26 UTC

   On July 18, 2026, between approximately 00:30 UTC and 04:00 UTC, users might have experienced 5xx errors while trying to create a new bucket in the Object Storage for the following endpoints. * [us-ord-1.linodeobjects.com](http://us-ord-1.linodeobjects.com) *...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-MIA (Miami)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-16 01:24 UTC

   Our team investigated an issue that affected connectivity in our US-MIA (Miami) data center between 21:20 UTC and approximately 23:28 UTC on July 15, 2026. During this window, users may have experienced degraded networking performance and packet loss for Compute services...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-07-14 12:21 UTC

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

2. identified 2026-07-14 12:58 UTC

   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.

3. monitoring 2026-07-14 13:11 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...

4. monitoring 2026-07-14 16:06 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-07-14 18:36 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-07-14 19:26 UTC

   We haven't observed any additional issues with the Cloud Manager, API, or CLI, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.

7. postmortem 2026-07-16 18:13 UTC

   On July 14, 2026, at 10:57 UTC, Akamai identified an increase in 502 errors and latency affecting customers using the Linode API, CLI, and Cloud Manager. This disruption resulted in moderate service impact, with customers reporting elevated error rates. Our initial investigation...

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-13 18:29 UTC

   Our team has identified an emerging service issue affecting host jobs for some hosts across all regions. Linode connectivity is *not impacted*, but some host-level jobs, such as backups or attempts to power on or off your services may be delayed. We will share additional updates...

2. resolved 2026-07-13 19:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-07-09 16:57 UTC

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

2. investigating 2026-07-09 17:24 UTC

   We are continuing to investigate this issue. We will provide an update within the next 30 minutes.

3. monitoring 2026-07-09 17:49 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 open a Support ticket , please call us at 855-454-6633...

4. resolved 2026-07-09 18:21 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, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.

5. postmortem 2026-07-10 12:30 UTC

   On July 9, 2026, at 15:43 UTC, customers were unable to login to [cloud.linode.com](http://cloud.linode.com) using username and password. Customers were getting "wrong password" error message. Investigation revealed that the issue was due to an internal certificate issue. To...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), Managed Databases, US-IAD (Washington), US-ORD (Chicago), CA-Central (Toronto), EU-West (London), EU-Central (Frankfurt), FR-PAR (Paris), AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-Southeast (Sydney), SE-STO (Stockholm), US-SEA (Seattle), IT-MIL (Milan), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta), BR-GRU (São Paulo), NL-AMS (Amsterdam), US-MIA (Miami), US-LAX (Los Angeles), ES-MAD (Madrid), AU-MEL (Melbourne), GB-LON (London 2), IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2), JP-TYO-3 (Tokyo 3), ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-06 18:04 UTC

   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...

2. resolved 2026-07-07 15:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Cloud Manager and API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-01 17:21 UTC

   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...

2. monitoring 2026-07-01 18:09 UTC

   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.

3. resolved 2026-07-01 18:28 UTC

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

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: SG-SIN-2 (Singapore 2) Block Storage

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-30 18:54 UTC

   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...

2. investigating 2026-06-30 19:55 UTC

   We are continuing to investigate this issue.

3. identified 2026-06-30 20:36 UTC

   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.

4. identified 2026-06-30 21:36 UTC

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

5. monitoring 2026-06-30 22:10 UTC

   At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

6. resolved 2026-06-30 23:22 UTC

   We haven’t observed any additional issues with the Block Storage service in Singapore Expansion, SP (sg-sin-2), and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

7. postmortem 2026-07-02 16:29 UTC

   On June 30, 2026, between approximately 17:30 UTC and 21:45 UTC, users may have experienced connection timeouts and errors related to the Block Storage service in Singapore Expansion, SP \(sg-sin-2\). The issue began when one host in the cluster was taken down for maintenance...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Akamai Cloud Pulse (ACLP) - Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-26 17:35 UTC

   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.

2. investigating 2026-06-26 18:19 UTC

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

3. investigating 2026-06-26 19:08 UTC

   We are continuing to investigate this issue. We will provide further updates as we have more information.

4. investigating 2026-06-26 20:04 UTC

   We are continuing to investigate this issue.

5. monitoring 2026-06-26 21:13 UTC

   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 open a Support...

6. monitoring 2026-06-30 00:02 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-07-08 12:26 UTC

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

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-IAD (Washington)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-26 17:14 UTC

   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.

2. resolved 2026-06-26 19:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-IAD (Washington), US-ORD (Chicago), CA-Central (Toronto), EU-West (London), EU-Central (Frankfurt), FR-PAR (Paris), AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-Southeast (Sydney), SE-STO (Stockholm), US-SEA (Seattle), IT-MIL (Milan), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta), BR-GRU (São Paulo), NL-AMS (Amsterdam), US-MIA (Miami), US-LAX (Los Angeles), ES-MAD (Madrid), AU-MEL (Melbourne), GB-LON (London 2), IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2), JP-TYO-3 (Tokyo 3), ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 14:33 UTC

   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.

2. monitoring 2026-06-25 14:50 UTC

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

3. resolved 2026-06-25 18:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), US-IAD (Washington), US-ORD (Chicago), CA-Central (Toronto), EU-West (London), EU-Central (Frankfurt), FR-PAR (Paris), AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-Southeast (Sydney), SE-STO (Stockholm), US-SEA (Seattle), IT-MIL (Milan), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta), BR-GRU (São Paulo), NL-AMS (Amsterdam), US-MIA (Miami), US-LAX (Los Angeles), ES-MAD (Madrid), AU-MEL (Melbourne), GB-LON (London 2), IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2), JP-TYO-3 (Tokyo 3), ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-24 18:53 UTC

   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.

2. investigating 2026-06-24 20:00 UTC

   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.

3. monitoring 2026-06-24 21:12 UTC

   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 open a Support ticket...

4. resolved 2026-06-25 19:29 UTC

   We haven’t observed any additional boot failures on GPU Instances in all regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

5. postmortem 2026-06-26 18:14 UTC

   On June 23, 2026, following a global software deployment, we identified an issue causing intermittent boot failures specifically for GPU Linodes. The impact was limited to instances where multiple GPU Linodes attempted to boot simultaneously. During the impact window customers...

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-24 16:27 UTC

   Between approximately 08:12 UTC and 12:35 UTC on June 24, 2026, attempting to create/autoscale Linodes using a Debian distribution may have failed due to a stale InRelease file in an upstream repository. We have mitigated the issue by updating our mirror endpoint to a healthy...

2. postmortem 2026-06-24 17:39 UTC

   Our upstream third-party Debian repo failed to sync with their own upstream repo chain for an unknown reason. The InRelease files for Debian packages were left to expire starting at approximately 08:12 UTC on June 24, 2026, preventing any Debian packages from getting installed....

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-MIA (Miami)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-06-16 14:29 UTC

   Our team is investigating an emerging service issue affecting networking in US-MIA (Miami). We will share additional updates as we have more information.

2. resolved 2026-06-16 17:18 UTC

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

3. postmortem 2026-06-22 18:54 UTC

   On June 16, 2026 Akamai investigated an instance of performance degradation and connectivity slowness observed affecting applications within the Miami compute environment. This event occurred between around 13:37 UTC and 14:20 UTC on June 16, 2026. The Investigation revealed a...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Longview

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-16 08:56 UTC

   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.

2. identified 2026-06-16 09:46 UTC

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

3. monitoring 2026-06-16 09:48 UTC

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

4. resolved 2026-06-16 13:13 UTC

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

5. postmortem 2026-06-16 16:48 UTC

   Starting around 23:15 UTC on June 15, 2026, some customers were unable to access the Longview graph dashboard. The investigation revealed that Linodes were unable to reach the Longview endpoint and were failing to report data. The impact was limited to reading the existing...

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-16 03:44 UTC

   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.

2. monitoring 2026-06-16 05:14 UTC

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

3. resolved 2026-06-16 06:06 UTC

   The issue affecting Linode Migrations has been resolved. Resize and Migration operations should be operating as normal now.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine, US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR (Paris) Linode Kubernetes Engine, AP-South (Singapore) Linode Kubernetes Engine, AP-Northeast (Tokyo 2) Linode Kubernetes Engine, AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney) Linode Kubernetes Engine, SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle) Linode Kubernetes Engine, JP-OSA (Osaka) Linode Kubernetes Engine, IN-MAA (Chennai) Linode Kubernetes Engine, ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo) Linode Kubernetes Engine, NL-AMS (Amsterdam) Linode Kubernetes Engine, ES-MAD (Madrid) Linode Kubernetes Engine, IT-MIL (Milan) Linode Kubernetes Engine, US-MIA (Miami) Linode Kubernetes Engine, US-LAX (Los Angeles) Linode Kubernetes Engine, GB-LON (London 2) Linode Kubernetes Engine, AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-05 14:23 UTC

   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...

2. resolved 2026-06-05 14:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-03 14:22 UTC

   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...

2. investigating 2026-06-03 18:33 UTC

   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...

3. resolved 2026-06-04 15:51 UTC

   The upstream issue has been resolved, and our Support phone line should now be fully functional again.

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark) Block Storage

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-06-03 08:58 UTC

   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.

2. investigating 2026-06-03 10:53 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-03 11:25 UTC

   At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

4. investigating 2026-06-03 12:55 UTC

   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.

5. monitoring 2026-06-03 15:44 UTC

   At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

6. resolved 2026-06-04 09:11 UTC

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

7. postmortem 2026-06-04 12:55 UTC

   Between 22:50 UTC on June 2, 2026 and 19:00 UTC on June 3, 2026, some customers experienced intermittent performance degradation and long access times when interacting with the Compute Block Storage cluster in Newark, US. During this period, intermittent component instability...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: Linode.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-02 01:26 UTC

   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.

2. identified 2026-06-02 01:33 UTC

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

3. monitoring 2026-06-08 17:59 UTC

   At this time we have been able to correct the issue affecting connectivity to the Community Site. We will be monitoring this to ensure that connectivity remains stable. If you continue to experience problems, please open a Support ticket for assistance.

4. resolved 2026-06-08 19:35 UTC

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

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: GB-LON (London 2) Object Storage

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. resolved 2026-05-29 18:23 UTC

   Starting at around 10:07 UTC on May 29, 2026, Object Storage in London became unavailable. Affected customers were unable to access Object Storage during this time, and may have seen 500 or similar errors. This occurred as the result of an issue with a planned router upgrade....

2. postmortem 2026-06-08 09:13 UTC

   Between 10:13 UTC and 10:22 UTC on May 29, 2026, customers using Object Storage \(OBJ\) in London experienced 5xx errors when trying to access content stored in that location. While attempting to isolate a separate packet loss issue, Akamai sequentially upgraded 2 pairs of...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: FR-PAR (Paris)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-22 11:22 UTC

   We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.

2. investigating 2026-05-22 12:24 UTC

   We are continuing to investigate the issue

3. monitoring 2026-05-22 13:14 UTC

   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 open a Support ticket for assistance.

4. resolved 2026-05-26 06:15 UTC

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

5. postmortem 2026-06-05 11:01 UTC

   On May 22, 2026 between approximately 09:10 and 11:30 UTC, connectivity issues were experienced in Paris \(FR-PAR3\) datacenter. During the impact window, customers may have experienced intermittent connection timeouts and errors for services deployed in the Paris datacenter....

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-19 19:48 UTC

   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.

2. identified 2026-05-19 21:06 UTC

   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.

3. monitoring 2026-05-19 21:58 UTC

   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 open a Support ticket for assistance.

4. resolved 2026-05-20 00:27 UTC

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

5. postmortem 2026-05-25 17:35 UTC

   On May 19, 2026, at 18:26 UTC, we identified an issue impacting the creation and re-provisioning of Linode instances using any of the four RTX PRO 6000 Blackwell \(g3-gpu-rtxpro6000-blackwell\) plans, resulting in API errors. These failures caused a denial of service for...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas), US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont), US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta), US-Southeast (Atlanta) Linode Kubernetes Engine, US-IAD (Washington), US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago), US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto), CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London), EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt), EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR (Paris), FR-PAR (Paris) Linode Kubernetes Engine, AP-South (Singapore), AP-South (Singapore) Linode Kubernetes Engine, AP-Northeast-2 (Tokyo 2), AP-Northeast (Tokyo 2) Linode Kubernetes Engine, AP-West (Mumbai), AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney), AP-Southeast (Sydney) Linode Kubernetes Engine, SE-STO (Stockholm), SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle), US-SEA (Seattle) Linode Kubernetes Engine, IT-MIL (Milan), JP-OSA (Osaka) Linode Kubernetes Engine, JP-OSA (Osaka), IN-MAA (Chennai) Linode Kubernetes Engine, IN-MAA (Chennai), ID-CGK (Jakarta) Linode Kubernetes Engine, ID-CGK (Jakarta), BR-GRU (São Paulo) Linode Kubernetes Engine, BR-GRU (São Paulo), NL-AMS (Amsterdam) Linode Kubernetes Engine, NL-AMS (Amsterdam), ES-MAD (Madrid) Linode Kubernetes Engine, US-MIA (Miami), IT-MIL (Milan) Linode Kubernetes Engine, US-LAX (Los Angeles), US-MIA (Miami) Linode Kubernetes Engine, ES-MAD (Madrid), US-LAX (Los Angeles) Linode Kubernetes Engine, AU-MEL (Melbourne), GB-LON (London 2) Linode Kubernetes Engine, GB-LON (London 2), AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2), IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2), SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3), JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine, ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-16 00:42 UTC

   Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.

2. investigating 2026-05-16 01:06 UTC

   We are continuing to investigate this issue.

3. identified 2026-05-16 01:27 UTC

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

4. resolved 2026-05-16 01:43 UTC

   This incident has been resolved.

5. postmortem 2026-05-20 19:15 UTC

   On May 15, 2026, at 18:18 UTC, we identified an issue impacting the deployment of Linodes that relied on StackScripts \(including all newly created Linode Kubernetes Engine \(LKE\) and \(LKE-E\) nodes\), resulting in deployment failures. These deployment failures resulted in...

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-05-15 02:24 UTC

   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...

2. resolved 2026-05-15 03:51 UTC

   We have identified the root cause of the migration delays affecting all regions. An unexpected reboot of several internal infrastructure components at approximately 22:10 UTC on May 14 resulted in incomplete reinitialization, causing the migration queue to stall.The affected...

3. postmortem 2026-05-15 06:32 UTC

   Starting around 04:00 UTC on May 14, 2026, Akamai identified an issue affecting Linode migration operations, including live, cold, and scheduled migrations. As a result, some customers experienced delays in migration processing, and customers undergoing certain migrations were...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), US-East (Newark) Block Storage, US-East (Newark) NodeBalancers, US-East (Newark) Backups, US-East (Newark) Object Storage, US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas), US-Central (Dallas) Block Storage, US-Central (Dallas) NodeBalancers, US-Central (Dallas) Backups, US-Central (Dallas) Linode Kubernetes Engine, US-Southeast (Atlanta) Object Storage, US-West (Fremont), US-West (Fremont) Block Storage, US-West (Fremont) NodeBalancers, US-West (Fremont) Backups, US-West (Fremont) Linode Kubernetes Engine, US-IAD (Washington) Object Storage, US-Southeast (Atlanta), US-Southeast (Atlanta) NodeBalancers, US-Southeast (Atlanta) Backups, US-Southeast (Atlanta) Block Storage, US-Southeast (Atlanta) Linode Kubernetes Engine, US-ORD (Chicago) Object Storage, EU-Central (Frankfurt) Object Storage, US-IAD (Washington), US-IAD (Washington) Backups, US-IAD (Washington) Block Storage, US-IAD (Washington) NodeBalancers, US-IAD (Washington) Linode Kubernetes Engine, AP-South (Singapore) Object Storage, US-ORD (Chicago), US-ORD (Chicago) Backups, US-ORD (Chicago) Block Storage, US-ORD (Chicago) NodeBalancers, US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto), CA-Central (Toronto) Block Storage, CA-Central (Toronto) NodeBalancers, CA-Central (Toronto) Backups, CA-Central (Toronto) Linode Kubernetes Engine, FR-PAR (Paris) Object Storage, EU-West (London), EU-West (London) Block Storage, EU-West (London) NodeBalancers, EU-West (London) Backups, EU-West (London) Linode Kubernetes Engine, SE-STO (Stockholm) Object Storage, EU-Central (Frankfurt), EU-Central (Frankfurt) Block Storage, EU-Central (Frankfurt) NodeBalancers, EU-Central (Frankfurt) Backups, EU-Central (Frankfurt) Linode Kubernetes Engine, US-SEA (Seattle) Object Storage, FR-PAR (Paris), FR-PAR (Paris) Backups, FR-PAR (Paris) Block Storage, FR-PAR (Paris) NodeBalancers, FR-PAR (Paris) Linode Kubernetes Engine, JP-OSA (Osaka) Object Storage, AP-South (Singapore), AP-South (Singapore) Block Storage, AP-South (Singapore) NodeBalancers, AP-South (Singapore) Backups, AP-South (Singapore) Linode Kubernetes Engine, IN-MAA (Chennai) Object Storage, AP-Northeast-2 (Tokyo 2), AP-Northeast-2 (Tokyo 2) NodeBalancers, AP-Northeast-2 (Tokyo 2) Backups, AP-Northeast-2 (Tokyo 2) Block Storage, AP-Northeast (Tokyo 2) Linode Kubernetes Engine, ID-CGK (Jakarta) Object Storage, AP-West (Mumbai), AP-West (Mumbai) Block Storage, AP-West (Mumbai) NodeBalancers, AP-West (Mumbai) Backups, AP-West (Mumbai) Linode Kubernetes Engine, BR-GRU (Sao Paulo) Object Storage, AP-Southeast (Sydney), AP-Southeast (Sydney) NodeBalancers, AP-Southeast (Sydney) Backups, AP-Southeast (Sydney) Linode Kubernetes Engine, AP-Southeast (Sydney) Block Storage, ES-MAD (Madrid) Object Storage, SE-STO (Stockholm), SE-STO (Stockholm) Backups, SE-STO (Stockholm) Block Storage, SE-STO (Stockholm) NodeBalancers, SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle), US-SEA (Seattle) Backups, US-SEA (Seattle) Block Storage, US-SEA (Seattle) NodeBalancers, US-SEA (Seattle) Linode Kubernetes Engine, IT-MIL (Milan), JP-OSA (Osaka) Backups, JP-OSA (Osaka) Block Storage, JP-OSA (Osaka) NodeBalancers, JP-OSA (Osaka) Linode Kubernetes Engine, GB-LON (London 2), JP-OSA (Osaka), IN-MAA (Chennai) Backups, IN-MAA (Chennai) Block Storage, IN-MAA (Chennai) NodeBalancers, IN-MAA (Chennai) Linode Kubernetes Engine, AU-MEL (Melbourne), IN-MAA (Chennai), ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo) Backups, BR-GRU (São Paulo) Block Storage, BR-GRU (São Paulo) NodeBalancers, NL-AMS (Amsterdam) Object Storage, ID-CGK (Jakarta), NL-AMS (Amsterdam) Backups, NL-AMS (Amsterdam) Block Storage, NL-AMS (Amsterdam) NodeBalancers, IT-MIL (Milan) Object Storage, BR-GRU (São Paulo) Linode Kubernetes Engine, BR-GRU (São Paulo), ES-MAD (Madrid) Backups, ES-MAD (Madrid) Block Storage, ES-MAD (Madrid) NodeBalancers, US-MIA (Miami) Object Storage, NL-AMS (Amsterdam) Linode Kubernetes Engine, NL-AMS (Amsterdam), IT-MIL (Milan) Backups, IT-MIL (Milan) Block Storage, IT-MIL (Milan) NodeBalancers, US-LAX (Los Angeles) Object Storage, ES-MAD (Madrid) Linode Kubernetes Engine, US-MIA (Miami), US-MIA (Miami) Backups, US-MIA (Miami) Block Storage, US-MIA (Miami) NodeBalancers, GB-LON (London 2) Object Storage, IT-MIL (Milan) Linode Kubernetes Engine, US-LAX (Los Angeles), ID-CGK (Jakarta) Backups, ID-CGK (Jakarta) Block Storage, ID-CGK (Jakarta) NodeBalancers, AU-MEL (Melbourne) Object Storage, US-MIA (Miami) Linode Kubernetes Engine, ES-MAD (Madrid), US-LAX (Los Angeles) Backups, US-LAX (Los Angeles) Block Storage, US-LAX (Los Angeles) NodeBalancers, IN-BOM-2 (Mumbai 2) Object Storage, US-LAX (Los Angeles) Linode Kubernetes Engine, AU-MEL (Melbourne), GB-LON (London 2) Backups, GB-LON (London 2) Block Storage, GB-LON (London 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) Object Storage, GB-LON (London 2) Linode Kubernetes Engine, GB-LON (London 2), AU-MEL (Melbourne) Backups, AU-MEL (Melbourne) Block Storage, AU-MEL (Melbourne) NodeBalancers, SG-SIN-2 (Singapore 2) Object Storage, AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2), IN-BOM-2 (Mumbai 2) Backups, IN-BOM-2 (Mumbai 2) Block Storage, IN-BOM-2 (Mumbai 2) NodeBalancers, JP-TYO-3 (Tokyo 3) Object Storage, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2) Backups, DE-FRA-2 (Frankfurt 2) Block Storage, DE-FRA-2 (Frankfurt 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2), SG-SIN-2 (Singapore 2) Backups, SG-SIN-2 (Singapore 2) Block Storage, SG-SIN-2 (Singapore 2) NodeBalancers, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3), JP-TYO-3 (Tokyo) Backups, JP-TYO-3 (Tokyo 3) Block Storage, JP-TYO-3 (Tokyo 3) NodeBalancers, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine, ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)

Failure mode: Security incident or emergency response to a vulnerability. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-05-13 21:02 UTC

   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...

2. investigating 2026-05-15 17:30 UTC

   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...

3. investigating 2026-06-05 20:24 UTC

   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...

4. resolved 2026-07-06 14:42 UTC

   We have completed our investigation and response to the "DirtyFrag" (CVE-2026-43500, CVE-2026-43284) and "Fragnesia" (CVE-2026-46300) vulnerabilities. We have published documentation articles with detailed guidance on available mitigations and recommended actions for affected...

Excerpts are shortened. Read the full incident on Linode's status page.

Affected: US-East (Newark), Linode.com, US-East (Newark) Block Storage, US-East (Newark) NodeBalancers, US-East (Newark) Backups, US-East (Newark) Object Storage, US-East (Newark) Linode Kubernetes Engine, US-East (Newark), Cloud Manager and API, US-Central (Dallas), US-Central (Dallas) Block Storage, US-Central (Dallas) NodeBalancers, US-Central (Dallas) Backups, US-Central (Dallas) Linode Kubernetes Engine, US-Southeast (Atlanta) Object Storage, US-Central (Dallas), Akamai Cloud Pulse (ACLP) - Logs, US-West (Fremont), Hosted DNS Service, US-West (Fremont) Block Storage, US-West (Fremont) NodeBalancers, US-West (Fremont) Backups, US-West (Fremont) Linode Kubernetes Engine, US-IAD (Washington) Object Storage, US-West (Fremont), US-Southeast (Atlanta), US-Southeast (Atlanta) NodeBalancers, US-Southeast (Atlanta) Backups, Longview, US-Southeast (Atlanta) Block Storage, US-Southeast (Atlanta) Linode Kubernetes Engine, US-ORD (Chicago) Object Storage, US-Southeast (Atlanta), EU-Central (Frankfurt) Object Storage, Managed Databases, US-IAD (Washington), US-IAD (Washington) Backups, US-IAD (Washington) Block Storage, US-IAD (Washington) NodeBalancers, US-IAD (Washington) Linode Kubernetes Engine, US-IAD (Washington), AP-South (Singapore) Object Storage, US-ORD (Chicago), US-ORD (Chicago) Backups, US-ORD (Chicago) Block Storage, US-ORD (Chicago) NodeBalancers, US-ORD (Chicago) Linode Kubernetes Engine, US-ORD (Chicago), CA-Central (Toronto), CA-Central (Toronto) Block Storage, CA-Central (Toronto) NodeBalancers, CA-Central (Toronto) Backups, CA-Central (Toronto) Linode Kubernetes Engine, FR-PAR (Paris) Object Storage, CA-Central (Toronto), EU-West (London), EU-West (London) Block Storage, EU-West (London) NodeBalancers, EU-West (London) Backups, EU-West (London) Linode Kubernetes Engine, SE-STO (Stockholm) Object Storage, EU-West (London), EU-Central (Frankfurt), EU-Central (Frankfurt) Block Storage, EU-Central (Frankfurt) NodeBalancers, EU-Central (Frankfurt) Backups, EU-Central (Frankfurt) Linode Kubernetes Engine, US-SEA (Seattle) Object Storage, EU-Central (Frankfurt), FR-PAR (Paris), FR-PAR (Paris) Backups, FR-PAR (Paris) Block Storage, FR-PAR (Paris) NodeBalancers, FR-PAR (Paris) Linode Kubernetes Engine, JP-OSA (Osaka) Object Storage, FR-PAR (Paris), AP-South (Singapore), AP-South (Singapore) Block Storage, AP-South (Singapore) NodeBalancers, AP-South (Singapore) Backups, AP-South (Singapore) Linode Kubernetes Engine, IN-MAA (Chennai) Object Storage, AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-Northeast-2 (Tokyo 2) NodeBalancers, AP-Northeast-2 (Tokyo 2) Backups, AP-Northeast-2 (Tokyo 2) Block Storage, AP-Northeast (Tokyo 2) Linode Kubernetes Engine, ID-CGK (Jakarta) Object Storage, AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-West (Mumbai) Block Storage, AP-West (Mumbai) NodeBalancers, AP-West (Mumbai) Backups, AP-West (Mumbai) Linode Kubernetes Engine, BR-GRU (Sao Paulo) Object Storage, AP-West (Mumbai), AP-Southeast (Sydney), AP-Southeast (Sydney) NodeBalancers, AP-Southeast (Sydney) Backups, AP-Southeast (Sydney) Linode Kubernetes Engine, AP-Southeast (Sydney) Block Storage, ES-MAD (Madrid) Object Storage, AP-Southeast (Sydney), SE-STO (Stockholm), SE-STO (Stockholm) Backups, SE-STO (Stockholm) Block Storage, SE-STO (Stockholm) NodeBalancers, SE-STO (Stockholm) Linode Kubernetes Engine, SE-STO (Stockholm), US-SEA (Seattle), US-SEA (Seattle) Backups, US-SEA (Seattle) Block Storage, US-SEA (Seattle) NodeBalancers, US-SEA (Seattle) Linode Kubernetes Engine, US-SEA (Seattle), IT-MIL (Milan), JP-OSA (Osaka) Backups, JP-OSA (Osaka) Block Storage, JP-OSA (Osaka) NodeBalancers, JP-OSA (Osaka) Linode Kubernetes Engine, GB-LON (London 2), IT-MIL (Milan), JP-OSA (Osaka), IN-MAA (Chennai) Backups, IN-MAA (Chennai) Block Storage, IN-MAA (Chennai) NodeBalancers, IN-MAA (Chennai) Linode Kubernetes Engine, AU-MEL (Melbourne), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo) Backups, BR-GRU (São Paulo) Block Storage, BR-GRU (São Paulo) NodeBalancers, NL-AMS (Amsterdam) Object Storage, IN-MAA (Chennai), ID-CGK (Jakarta), NL-AMS (Amsterdam) Backups, NL-AMS (Amsterdam) Block Storage, NL-AMS (Amsterdam) NodeBalancers, IT-MIL (Milan) Object Storage, BR-GRU (São Paulo) Linode Kubernetes Engine, ID-CGK (Jakarta), BR-GRU (São Paulo), ES-MAD (Madrid) Backups, ES-MAD (Madrid) Block Storage, ES-MAD (Madrid) NodeBalancers, US-MIA (Miami) Object Storage, NL-AMS (Amsterdam) Linode Kubernetes Engine, BR-GRU (São Paulo), NL-AMS (Amsterdam), IT-MIL (Milan) Backups, IT-MIL (Milan) Block Storage, IT-MIL (Milan) NodeBalancers, US-LAX (Los Angeles) Object Storage, ES-MAD (Madrid) Linode Kubernetes Engine, NL-AMS (Amsterdam), US-MIA (Miami), US-MIA (Miami) Backups, US-MIA (Miami) Block Storage, US-MIA (Miami) NodeBalancers, GB-LON (London 2) Object Storage, IT-MIL (Milan) Linode Kubernetes Engine, US-MIA (Miami), US-LAX (Los Angeles), ID-CGK (Jakarta) Backups, ID-CGK (Jakarta) Block Storage, ID-CGK (Jakarta) NodeBalancers, AU-MEL (Melbourne) Object Storage, US-MIA (Miami) Linode Kubernetes Engine, US-LAX (Los Angeles), ES-MAD (Madrid), US-LAX (Los Angeles) Backups, US-LAX (Los Angeles) Block Storage, US-LAX (Los Angeles) NodeBalancers, IN-BOM-2 (Mumbai 2) Object Storage, US-LAX (Los Angeles) Linode Kubernetes Engine, ES-MAD (Madrid), AU-MEL (Melbourne), GB-LON (London 2) Backups, GB-LON (London 2) Block Storage, GB-LON (London 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) Object Storage, GB-LON (London 2) Linode Kubernetes Engine, AU-MEL (Melbourne), GB-LON (London 2), AU-MEL (Melbourne) Backups, AU-MEL (Melbourne) Block Storage, AU-MEL (Melbourne) NodeBalancers, SG-SIN-2 (Singapore 2) Object Storage, AU-MEL (Melbourne) Linode Kubernetes Engine, GB-LON (London 2), IN-BOM-2 (Mumbai 2), IN-BOM-2 (Mumbai 2) Backups, IN-BOM-2 (Mumbai 2) Block Storage, IN-BOM-2 (Mumbai 2) NodeBalancers, JP-TYO-3 (Tokyo 3) Object Storage, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2) Backups, DE-FRA-2 (Frankfurt 2) Block Storage, DE-FRA-2 (Frankfurt 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2), SG-SIN-2 (Singapore 2) Backups, SG-SIN-2 (Singapore 2) Block Storage, SG-SIN-2 (Singapore 2) NodeBalancers, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2), JP-TYO-3 (Tokyo 3), JP-TYO-3 (Tokyo) Backups, JP-TYO-3 (Tokyo 3) Block Storage, JP-TYO-3 (Tokyo 3) NodeBalancers, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3), ZA-JNB (Johannesburg), ZA-JNB (Johannesburg), NZ-AKL (Auckland), NZ-AKL (Auckland), CO-BOG (Bogota), CO-BOG (Bogota), US-DEN (Denver), US-DEN (Denver), DE-HAM (Hamburg), DE-HAM (Hamburg), US-HOU (Houston), US-HOU (Houston), MY-KUL (Kuala Lumpur), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), FR-MRS (Marseille), MX-QRO (Queretaro), MX-QRO (Queretaro), CL-SCL (Santiago), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)

Failure mode: Security incident or emergency response to a vulnerability. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Akamai.

1. investigating 2026-05-08 13:40 UTC

   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...

2. investigating 2026-05-09 14:40 UTC

   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...

3. investigating 2026-05-15 17:28 UTC

   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...

4. investigating 2026-06-05 20:23 UTC

   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...

5. resolved 2026-07-06 14:41 UTC

   We have completed our investigation and response to the "DirtyFrag" (CVE-2026-43500, CVE-2026-43284) and "Fragnesia" (CVE-2026-46300) vulnerabilities. We have published documentation articles with detailed guidance on available mitigations and recommended actions for affected...

Excerpts are shortened. Read the full incident on Linode's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-03 15:15 UTC

   Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.

2. identified 2025-12-03 16:48 UTC

   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.

3. identified 2025-12-04 20:51 UTC

   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.

4. identified 2025-12-17 13:40 UTC

   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.

5. identified 2026-01-05 17:16 UTC

   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.

6. identified 2026-01-05 19:30 UTC

   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.

7. identified 2026-02-03 15:34 UTC

   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.

8. identified 2026-02-19 16:41 UTC

   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.

9. identified 2026-02-26 15:42 UTC

   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.

10. identified 2026-03-19 20:13 UTC

    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.

11. identified 2026-04-06 13:39 UTC

    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.

12. identified 2026-04-15 15:12 UTC

    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.

13. identified 2026-05-13 20:59 UTC

    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.

14. identified 2026-05-26 21:17 UTC

    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.

15. identified 2026-07-03 13:55 UTC

    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.

16. resolved 2026-10-08 21:26 UTC

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

Excerpts are shortened. Read the full incident on Linode's status page.