Emerging Service Issue - Object Storage and LKE - US-MIA

Incident Report for Linode

Postmortem

Starting at 09:33 UTC on July 1, 2025, alerts fired indicating that Object Storage services were unavailable in our US-MIA region. Impacted customers would have experienced issues (in the form of 500 errors) when trying to access, modify, or create Object Storage buckets, LKE clusters and Compute Images. Akamai's investigation revealed that the issue was caused by a misconfigured and improperly managed deployment plan (DP) that led to unintended network changes, ultimately severing connectivity to the entire Object Storage, LKE, and Compute Image services in the US-MIA data center.
To mitigate the impact, we rolled back changes introduced by the problematic DP, and the impacted services were resumed at approximately 14:30 UTC on July 1, 2025. After a period of monitoring, there were no recurrences, and the issue was considered resolved.
To prevent recurrence, Akamai will review the actions taken as well as the relevant procedures and implement the necessary changes.
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.

Posted Jul 07, 2025 - 08:17 UTC

Resolved

We haven’t observed any additional issues with the Object Storage and Linode Kubernetes Engine services in our US-MIA region, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Posted Jul 01, 2025 - 16:08 UTC

Update

Our team has implemented a fix for the issue that was impacting Object Storage and LKE services in our US-MIA region. These services should now be accessible and functional at this time. If you are still seeing issues for these services within this region, please open a Support ticket from your Cloud Manager.
Posted Jul 01, 2025 - 15:21 UTC

Monitoring

At this time we have been able to correct the issues affecting the Object Storage and Linode Kubernetes Engine services. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Posted Jul 01, 2025 - 14:56 UTC

Identified

Our team has identified the issue affecting the Object Storage and Linode Kubernetes Engine services in our US-MIA data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Impacted customers would be unable to access, manage, and create Object Storage buckets and Linode Kubernetes Engine clusters.
Posted Jul 01, 2025 - 13:58 UTC

Update

We are continuing to investigate this issue with Object Storage and Linode Kubernetes Engine in the US-MIA region.
Posted Jul 01, 2025 - 12:22 UTC

Update

We are continuing to investigate this issue with Object Storage in the US-MIA region.

Linode Kubernetes Engine in US-MIA is affected as well.
Posted Jul 01, 2025 - 11:12 UTC

Investigating

Our team is investigating an emerging service issue affecting Object Storage in US-MIA. We will share additional updates as we have more information.
Posted Jul 01, 2025 - 10:26 UTC
This incident affected: Object Storage (US-MIA (Miami) Object Storage) and Linode Kubernetes Engine (US-MIA (Miami) Linode Kubernetes Engine).