- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-IAD (Washington) Linode Kubernetes Engine
- Regions
- us
- Down Index
- 32of 100
What to do
Check whether you use Akamai Cloud (Linode) US-IAD (Washington) Linode Kubernetes Engine in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 12m it lasted.
Anything that failed between 2026-08-13 21:13 UTC and 2026-08-13 23:24 UTC may need a replay.Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Akamai Cloud (Linode) 4
- investigating
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.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- postmortem
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 of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f4d0ca0699
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-08-13 23:24 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
2h 12m, from 2026-08-13 21:13 UTC to 2026-08-13 23:24 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-IAD (Washington) Linode Kubernetes Engine in us.
What caused it?
Akamai Cloud (Linode) hasn't published a root cause. If it does, it shows here.
Where does this come from?
Akamai Cloud (Linode)'s official status page, https://status.linode.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.