rewindex

CompaniesLinode (Akamai)Incidents

Linode (Akamai): Service Issue - Linode Kubernetes Engine Enterprise (LKE-E) - Seattle (SEA1)

No impact listedStatus: postmortemStarted Resolved (-1547 min)2 updatesstspg.io (opens in new tab)

Timeline of updates

  1. resolved

    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 (opens in new tab) for assistance.

  2. postmortem

    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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Linode (Akamai), started 2026-08-14 15:46 UTC, resolved after -1547 min, 2 update(s).

Title
Service Issue - Linode Kubernetes Engine Enterprise (LKE-E) - Seattle (SEA1)
Vendor
Linode (Akamai)
Date
URL
https://rewindex.com/company/linode-akamai/incidents/1zbc64w8cq1w

Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on August 14, 2026Linode (Akamai) in August 2026MarkdownJSON