- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-IAD (Washington) Object Storage, US-ORD (Chicago) Object Storage, FR-PAR (Paris) Object Storage, US-SEA (Seattle) Object Storage, US-LAX (Los Angeles) Object Storage
- Regions
- eu, us
- Down Index
- 34of 100
What to do
Check whether you use Akamai Cloud (Linode) US-IAD (Washington) Object Storage, US-ORD (Chicago) Object Storage, FR-PAR (Paris) Object Storage, US-SEA (Seattle) Object Storage and 1 more in eu, 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 1h 2m it lasted.
Anything that failed between 2026-07-18 03:34 UTC and 2026-07-18 04:36 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) 4
- 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
- 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
- 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
- postmortem
On July 18, 2026, between approximately 00:30 UTC and 04:00 UTC, users might have experienced 5xx errors while trying to create a new bucket in the Object Storage for the following endpoints. * [us-ord-1.linodeobjects.com](http://us-ord-1.linodeobjects.com) * [us-lax-1.linodeobjects.com](http://us-lax-1.linodeobjects.com) * [us-iad-1.linodeobjects.com](http://us-iad-1.linodeobjects.com) * [us-sea-1.linodeobjects.com](http://us-sea-1.linodeobjects.com) * [fr-par-1.linodeobjects.com](http://fr-par-1.linodeobjects.com) The issue began when the infrastructure supporting Object Storage entered a degraded state across all nodes. This prevented the service from processing requests, resulting in failures during bucket creation operations. To mitigate the impact, we have applied a fix at the backend system responsible for bucket creation. The impact was mitigated following this action. Our subject matter experts are investigating the root cause and will take appropriate preventive actions. We apologize for the impact and appreciate your patience and ongoing support. We are making configuration and operational changes to our systems to help prevent this from happening again, and remain committed to continuous improvement. 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-80351423ab
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-07-18 04:36 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
1h 2m, from 2026-07-18 03:34 UTC to 2026-07-18 04:36 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-IAD (Washington) Object Storage, US-ORD (Chicago) Object Storage, FR-PAR (Paris) Object Storage, US-SEA (Seattle) Object Storage and 1 more in eu, 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.