- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-ORD (Chicago)
- Regions
- us
- Down Index
- 34of 100
What to do
Check whether you use Akamai Cloud (Linode) US-ORD (Chicago) 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 43m it lasted.
Anything that failed between 2026-10-19 14:49 UTC and 2026-10-19 20:33 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 has identified an issue affecting connectivity in our Chicago (US-ORD) data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.
provider
- monitoring
At this time we have been able to correct the issues affecting connectivity in our Chicago (US-ORD) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
provider
- resolved
We haven’t observed any additional connectivity issues in our Chicago (US-ORD) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
provider
- postmortem
Beginning at approximately 14:23 UTC on October 19, 2026, as part of a planned internal maintenance, we migrated too many of the same routing resources at the same time. This resulted in route instability in certain network segments until the migration completed and routes were adopted and converged at 14:55 UTC on October 19, 2026. To prevent this issue from reoccurring, we are modifying our maintenance planning process to ensure that critical components are taken offline in a phased manner that doesn’t introduce customer impact. 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-6eac578388
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-10-19 20:33 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
5h 43m, from 2026-10-19 14:49 UTC to 2026-10-19 20:33 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-ORD (Chicago) 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.