Akamai Linode outage, July 2026: Service Issue - Linode API/CLI

Akamai Linode reported and resolved an incident: Service Issue - Linode API/CLI. It lasted 7.1 hours.

Resolved

From Akamai Linode's official status page, in their words.

What happened

Started
Resolved
Duration
7.1 hours
Impact
minor
Affected
Cloud Manager and API
  1. Investigating
  2. Identified
  3. Monitoring
  4. Resolved

Why it happened

Akamai Linode has not given a cause in its updates. We never guess one.

How it was resolved

On July 14, 2026, at 10:57 UTC, Akamai identified an increase in 502 errors and latency affecting customers using the Linode API, CLI, and Cloud Manager. This disruption resulted in moderate service impact, with customers reporting elevated error rates. Our initial investigation traced the issue to latency with IAM services, which was resolved, but elevated errors persisted. Further analysis by relevant subject matter experts determined that the incident was triggered by a manual failback to the Cloud IAM primary load balancer from the secondary load balancer. This action was prompted by a warning alert indicating that the secondary load balancer was acting as the keepalived master. The manual process of starting and stopping services to initiate the failback differed from the automated process and led to a cascade of stale GRPC connections, causing increased latency and API errors. Restarting the API servers cleared the stale connections and restored normal operations. Customer impact was mitigated by approximately 13:10 UTC on July 14, 2026. To prevent recurrence, Akamai is investigating why the manual failback caused this behavior. The team is considering implementing a drain command to clear GRPC connections during failover and setting up alerts to detect stale connections for proactive intervention. However, the immediate focus remains on understanding the root cause, with alerting and automation planned for later phases. Several customers have confirmed resolution acros

Akamai Linode's closing update

This incident on the Akamai Linode status page

Timeline

Oldest first, from the first notice to the resolution. From Akamai Linode's official status page, in their words.

  1. investigating

    Our team is investigating an emerging service issue affecting the API and CLI. We will share additional updates as we have more information.

  2. identified

    Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

  3. monitoring

    At this time we have been able to correct the issue affecting the Cloud Manager and API. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.

  4. monitoring

    We are continuing to monitor for any further issues.

  5. monitoring

    We are continuing to monitor for any further issues.

  6. resolved

    We haven't observed any additional issues with the Cloud Manager, API, or CLI, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.

  7. postmortem

    On July 14, 2026, at 10:57 UTC, Akamai identified an increase in 502 errors and latency affecting customers using the Linode API, CLI, and Cloud Manager. This disruption resulted in moderate service impact, with customers reporting elevated error rates. Our initial investigation traced the issue to latency with IAM services, which was resolved, but elevated errors persisted. Further analysis by relevant subject matter experts determined that the incident was triggered by a manual failback to the Cloud IAM primary load balancer from the secondary load balancer. This action was prompted by a warning alert indicating that the secondary load balancer was acting as the keepalived master. The manual process of starting and stopping services to initiate the failback differed from the automated process and led to a cascade of stale GRPC connections, causing increased latency and API errors. Restarting the API servers cleared the stale connections and restored normal operations. Customer impact was mitigated by approximately 13:10 UTC on July 14, 2026. To prevent recurrence, Akamai is investigating why the manual failback caused this behavior. The team is considering implementing a drain command to clear GRPC connections during failover and setting up alerts to detect stale connections for proactive intervention. However, the immediate focus remains on understanding the root cause, with alerting and automation planned for later phases. Several customers have confirmed resolution acros

What this means for a business (and what to check now)

  • Retry anything that failed during the 7.1 hours.
  • Enter any payments, bookings or jobs you took another way.
  • If a deadline fell inside the window, keep this page as your record of the outage.

The full guide: what to do when a service you rely on is down

Other Akamai Linode incidents

Hear about the next Akamai Linode incident as it starts

Free email alerts when the official status changes, with what to do while it is down.

Watch Akamai Linode