Linode incident: Service Issue - Linode Kubernetes Engine (IAD2)

Affected components

• US-IAD (Washington) Linode Kubernetes Engine

1. postmortemAug 17, 2026, 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 recent software version upgrade which resulted in an API mismatch. We updated the identified components to bring them in sync with the expected state. This mitigated the issue at approximately 16:00 UTC on August 13, 2026. To prevent this issue from occurring in the future, we are reviewing LKE software update processes to ensure that all included components complete version upgrades before being reintroduced to service during platform software updates. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

2. resolvedAug 13, 2026, 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

3. monitoringAug 13, 2026, 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

4. investigatingAug 13, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Linode's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Grafana Cloud: K6 Test OutageCritical · Aug 13, 2026, 15:25 UTC
• Elasticsearch: Increased error rates for microsoft-multilingual-e5-largeMajor · Aug 13, 2026, 08:32 UTC
• Cursor: Investigating service degradation — Automations, Cloud Agents, and IDEMajor · Aug 13, 2026, 14:46 UTC
• Sentry: Span & Transaction ingestion delayed in DEMajor · Aug 13, 2026, 17:47 UTC
• Akamai: Certificate Provisioning System (CPS) IssuesMinor · Aug 11, 2026, 10:11 UTC
• GitHub: Disruption with GHEC Team SyncMinor · Aug 13, 2026, 16:21 UTC
• Cloudinary: Media Library / asset visibilityMinor · Aug 13, 2026, 17:04 UTC
• HashiCorp Vault: Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resourcesMinor · Aug 13, 2026, 17:50 UTC

How often does Linode have incidents?

Linode reported 10 incidents in the last 90 days. A typical incident lasted 2h 15m. See Linode's uptime and incident history