Linode incident: Issue in creating new LKE Enterprise cluster across regions.

Affected components

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

1. identifiedOct 20, 2026, 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.

2. identifiedOct 20, 2026, 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 workloads from running.

3. identifiedOct 20, 2026, 12:33 UTC

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

4. identifiedOct 20, 2026, 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 workloads from running.

What APIStatus.watch saw

• Oct 20, 2026, 12:30 UTCoperational → degraded

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snowflake: INC20000294Critical · Oct 20, 2026, 06:34 UTC
• 1Password: High error rate on 1Password.comMajor · Oct 16, 2026, 23:45 UTC
• Elasticsearch: Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)Major · Oct 20, 2026, 06:51 UTC
• Grafana Cloud: Some GCK6 App Project Pages are Failing to LoadMajor · Oct 20, 2026, 14:36 UTC
• Confluent Cloud: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2Major · Oct 20, 2026, 14:46 UTC
• Shopify: Some merchants encountering error messages when trying to login to their adminsMinor · Oct 8, 2026, 14:49 UTC
• Twilio: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• Twilio: SMS Delivery Delays from a Subset of Twilio Short Codes to Brisanet BrazilMinor · Oct 18, 2026, 22:41 UTC
• Twilio: SMS Delivery Receipt Delays from Twilio to Surf Telecom BrazilMinor · Oct 19, 2026, 02:41 UTC

How often does Linode have incidents?

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