- Level
- confirmed
- Worst impact
- Partial outage
- Components
- US-East (Newark) Object Storage, Cloud Manager and API, US-Southeast (Atlanta) Object Storage, US-IAD (Washington) Object Storage, US-ORD (Chicago) Object Storage, EU-Central (Frankfurt) Object Storage, AP-South (Singapore) Object Storage, FR-PAR (Paris) Object Storage, SE-STO (Stockholm) Object Storage, US-SEA (Seattle) Object Storage, JP-OSA (Osaka) Object Storage, IN-MAA (Chennai) Object Storage, ID-CGK (Jakarta) Object Storage, BR-GRU (Sao Paulo) Object Storage, ES-MAD (Madrid) Object Storage, GB-LON (London 2), AU-MEL (Melbourne), NL-AMS (Amsterdam) Object Storage, IT-MIL (Milan) Object Storage, US-MIA (Miami) Object Storage, US-LAX (Los Angeles) Object Storage, GB-LON (London 2) Object Storage, AU-MEL (Melbourne) Object Storage, IN-BOM-2 (Mumbai 2) Object Storage, DE-FRA-2 (Frankfurt 2) Object Storage, SG-SIN-2 (Singapore 2) Object Storage, JP-TYO-3 (Tokyo 3) Object Storage
- Regions
- apac, au, eu, latam, us
- Down Index
- 61of 100
What to do
Check whether you use Akamai Cloud (Linode) US-East (Newark) Object Storage, Cloud Manager and API, US-Southeast (Atlanta) Object Storage, US-IAD (Washington) Object Storage and 23 more in apac, au, eu, latam. 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 9h 6m it lasted.
Anything that failed between 2026-03-07 12:02 UTC and 2026-03-07 21:08 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) 9
- investigating
This issue is impacting Object Storage access globally. During this time customers may encounter issues with managing buckets, access keys, or Object Storage policies. Our team is continuing to investigate.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are actively investigating an issue affecting the Object Storage service. Users may experience connection timeouts and errors when accessing this service. We will provide updates as we learn more and work toward a resolution.
provider
- investigating
We are continuing to investigate this issue. Thank you for your patience as we work toward a resolution.
provider
- investigating
Our team is continuing to investigate the Object Storage API issue, which affects all Object Storage regions. This issue is limited to interacting with the Object Storage service, such as managing buckets, access keys, or Object Storage policies. The underlying Object Storage service itself remains operational. We appreciate your patience and will provide further updates as soon as possible.
provider
- identified
Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
provider
- identified
We are still working to implement the fix for the Object Storage service issue. We will share another update as soon as progress is made.
provider
- monitoring
At this time we have been able to correct the issues affecting the Object Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
provider
- resolved
We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
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-fb0729d659
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-03-07 21:08 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
9h 6m, from 2026-03-07 12:02 UTC to 2026-03-07 21:08 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-East (Newark) Object Storage, Cloud Manager and API, US-Southeast (Atlanta) Object Storage, US-IAD (Washington) Object Storage and 23 more in apac, au, eu, latam.
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.