GlobalOutageMap
← Live dashboard
Linode logoLinode

Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Aug 13, 2026, 09:13 PM · Resolved Aug 13, 2026, 11:24 PM

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...

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

US-IAD (Washington) Linode Kubernetes Engine

Updates (4)

  1. Aug 18, 2026, 08:32 PM
    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

    Linode ↗
  2. Aug 13, 2026, 11:24 PM
    Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)

    This incident has been resolved.

    Linode ↗
  3. Aug 13, 2026, 11:02 PM
    Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)

    A fix has been implemented and we are monitoring the results.

    Linode ↗
  4. Aug 13, 2026, 09:13 PM
    Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)

    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.

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.