- Level
- confirmed
- Worst impact
- Degraded
- Components
- Cloud Manager and API
- Regions
- us
- Down Index
- 34of 100
What to do
Check whether you use Akamai Cloud (Linode) Cloud Manager and API 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 5h 40m it lasted.
Anything that failed between 2026-08-13 18:46 UTC and 2026-08-14 00:26 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) 5
- investigating
Our team is investigating an emerging service issue affecting the API in all regions. We will share additional updates as we have more information.
provider
- monitoring
As of 19:30 UTC have been able to correct the issue affecting API in all regions. 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.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On August 13th, 2026, at approximately 18:15 UTC, Akamai observed a brief service outage affecting [_api.linode.com_](http://api.linode.com). The total service interruption lasted for approximately 3 minutes, concluding at 18:18 UTC. Following the restoration of initial connectivity, elevated API response latency persisted through 19:06 UTC, causing slower response times and intermittent delays for customers interacting with API services. To address the performance impact, Akamai engineering teams identified a configuration discrepancy on the secondary caching infrastructure node that prevented it from absorbing the full traffic load after the failover. Engineers completed a controlled migration and moved request caching traffic back over to the primary host. Following this change, API latency rapidly decreased to normal operational levels. The initial condition was triggered by an unexpected reboot of the primary caching node's physical host. While redundant infrastructure was active, the secondary node was unable to process the failover traffic seamlessly, causing the extended performance degradation. Our engineering teams are conducting a follow-up investigation into the failover mechanisms to optimize execution speeds and align configuration settings across redundant nodes, ensuring secondary systems can handle traffic seamlessly in future events. 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-9862f6fd31
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-08-14 00:26 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
5h 40m, from 2026-08-13 18:46 UTC to 2026-08-14 00:26 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named Cloud Manager and API 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.