We haven’t observed any additional connectivity issues in our Los Angeles data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

This incident has been resolved.

It appears the issue was caused by a temporary network disruption outside our infrastructure. We can confirm that everything is currently stable and functioning normally.

Akamai took action to enable Linode Disk Encryption \(LDE\) in the Osaka, Japan \(OSA1\) region at around 08:28 UTC on July 10, 2025. As part of this action, OSA LKE services were inadvertently removed due to human error, resulting in an inability for customers to use, manage, or create new LKE clusters in the Osaka region. To mitigate the impact, Akamai performed disaster recovery steps to restore the impacted OSA LKE services to a healthy state using the most recent snapshot. The impact was mitigated at around 17:00 UTC on July 10, 2025. To prevent recurrence, Akamai will harden the removal of LKE resources in production, limit the scope of LKE production changes, and improve the disaster recovery process. 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.

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.