Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)
Between 17:25 UTC and 22:50 UTC on August 13, 2026, Linode Kubernetes Engine Enterprise \(LKE-E\) customers attempting to deploy G7 dedicated Linode instances in our Washington \(IAD2\) data center, received 403 provisioning error messages. Active workloads and running instances were not affected by this issue. Our investigation revealed that while total physical hardware capacity in IAD2 was sufficient, the provisioning request triggered an entitlement check failure due to an initial soft host-allocation threshold. Akamai resolved the issue by increasing the Linode-per-host limit from 5 to 20 in IAD2. Full deployment capabilities were restored and stabilized at 22:50 UTC. To prevent recurrence moving forward, we will implement dedicated alerting for entitlement and capacity issues, directly linked to response runbooks for rapid remediation. Additionally, we are building a centralized capacity overview dashboard to proactively track regional headroom. This summary provides an overview
The latest update from Akamai Cloud (Linode).
State
Resolved
Started
79 d ago
2026-08-13 21:13 UTC
Lasted
2 h 12 min
until 2026-08-13 23:24 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 49 min 83%
Monitoring
23 min 17%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
Between 17:25 UTC and 22:50 UTC on August 13, 2026, Linode Kubernetes Engine Enterprise \(LKE-E\) customers attempting to deploy G7 dedicated Linode instances in our Washington \(IAD2\) data center, received 403 provisioning error messages. Active workloads and running instances were not affected by this issue. Our investigation revealed that while total physical hardware capacity in IAD2 was sufficient, the provisioning request triggered an entitlement check failure due to an initial soft host-allocation threshold. Akamai resolved the issue by increasing the Linode-per-host limit from 5 to 20 in IAD2. Full deployment capabilities were restored and stabilized at 22:50 UTC. To prevent recurrence moving forward, we will implement dedicated alerting for entitlement and capacity issues, directly linked to response runbooks for rapid remediation. Additionally, we are building a centralized capacity overview dashboard to proactively track regional headroom. This summary provides an overview
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
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.
Affected components
1Akamai Cloud (Linode) in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
89
Median duration
6 h 29 min
This incident
66% shorter than the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)
A service issue affects US-Southeast (Atlanta). Akamai Cloud (Linode) reports that the region has degraded performance. Akamai Cloud (Linode) is still investigating the issue.
Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432. Akamai states that it is investigating and is deploying mitigations for the known attack vector. Akamai advises customers to apply OS updates from their upstream provider when those updates become available.
Akamai Cloud (Linode)·Service Issue - Block Storage (BR-GRU)
Block Storage does not work in the BR-GRU (São Paulo) region. Akamai Cloud reports that a fix is in place and the state is monitoring.
Akamai Cloud (Linode)·Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Akamai Cloud reports a connectivity problem between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2). The service is degraded in these two regions. Akamai Cloud moved the incident to monitoring and continues to monitor the impact.
Akamai Cloud (Linode)·Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)
This issue is considered resolved.
Follow Akamai Cloud (Linode)
Your coding agent knows when Akamai Cloud (Linode) is down, and tells you when a failure is theirs, not yours. You can also get Akamai Cloud (Linode) incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linode" and tell me if Akamai Cloud (Linode) has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=linode/feed subscribe https://outages.cc/feed.xml?providers=linodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane