- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-East (Newark) Object Storage
- Regions
- us, us-east-1
- Down Index
- 34of 100
What to do
Check whether you use Akamai Cloud (Linode) US-East (Newark) Object Storage in us, us-east-1. 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 49m it lasted.
Anything that failed between 2026-04-07 00:50 UTC and 2026-04-07 01:39 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) 3
- investigating
Our team is investigating an emerging service issue affecting Object Storage in us-east-1. We will share additional updates as we have more information.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
This incident has been resolved.
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-314feb130e
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-04-07 01:39 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
49m, from 2026-04-07 00:50 UTC to 2026-04-07 01:39 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-East (Newark) Object Storage in us, us-east-1.
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.