- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-MIA (Miami)
- Regions
- us
- Down Index
- 33of 100
What to do
Check whether you use Akamai Cloud (Linode) US-MIA (Miami) 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 2h 49m it lasted.
Anything that failed between 2026-06-16 14:29 UTC and 2026-06-16 17:18 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 networking in US-MIA (Miami). We will share additional updates as we have more information.
provider
- resolved
We haven’t observed any additional connectivity issues in our US-MIA (Miami) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
provider
- postmortem
On June 16, 2026 Akamai investigated an instance of performance degradation and connectivity slowness observed affecting applications within the Miami compute environment. This event occurred between around 13:37 UTC and 14:20 UTC on June 16, 2026. The Investigation revealed a configuration change on an Akamai device in Miami triggered an underlying vendor software defect within the routing platform's operating system. Actions were taken to mitigate the impact and restore intended routing paths. To prevent any further recurrence, we have temporarily suspended related configuration changes. Root Cause: During a routine, scheduled configuration update to an aggregated network link, an underlying vendor software defect within the routing platform's operating system was triggered. While the configuration change itself was standard and correct, the software bug caused the router to incorrectly process internal MPLS \(Multiprotocol Label Switching\) routing tables. Instead of applying changes only to the targeted link, the software inadvertently cleared the routing instructions for unrelated network interfaces. This unintended removal of routing paths led to the subsequent traffic disruption. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. 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-26ae55b2c8
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-06-16 17:18 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
2h 49m, from 2026-06-16 14:29 UTC to 2026-06-16 17:18 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-MIA (Miami) 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.