- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-East (Newark) Object Storage, 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
- 52of 100
What to do
Check whether you use Akamai Cloud (Linode) US-East (Newark) Object Storage, US-Southeast (Atlanta) Object Storage, US-IAD (Washington) Object Storage, US-ORD (Chicago) Object Storage and 22 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 58m it lasted.
Anything that failed between 2026-04-29 09:22 UTC and 2026-04-29 19:19 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
We are aware that some customers have been experiencing 403 (InvalidAccessKeyId) errors when attempting to access object storage, beginning yesterday evening. We will share additional updates as we have more information.
provider
- investigating
Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
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-df2eb6fd67
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-04-29 19:19 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
9h 58m, from 2026-04-29 09:22 UTC to 2026-04-29 19:19 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-East (Newark) Object Storage, US-Southeast (Atlanta) Object Storage, US-IAD (Washington) Object Storage, US-ORD (Chicago) Object Storage and 22 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.