Akamai began a scheduled upgrade of core Compute databases on August 26, 2025. At approximately 14:50 UTC on August 26, Compute customers began to experience a global degradation of service provisioning new Object Storage buckets, autoscaling of LKE resources, attaching Block Storage volumes to Linodes, and any other action which relies upon the Compute API for processing. Akamai was able to restore API functionality at ~16:13 UTC on August 26, 2025, however downstream processing of requests was delayed until a backlog completed processing at ~17:45 UTC.

‌

There was a series of 3 reoccurrences of impact between ~2:02 UTC and ~2:28 UTC on August 27, 2025, which were due to the proxy layer fronting the core database having difficulty maintaining a primary database target. In response, a software configuration regarding database connection settings was updated, restoring service at ~2:28 UTC on August 27, 2025. A hardware configuration was updated during a maintenance window on August 31, 2025 to continue completion of follow-up actions related to this impact.

‌

This database upgrade is intended to ensure continued support and to adopt features that provide higher resilience and better scalability.

‌

At this time, the upgrade of core Compute databases has been completed and systems are operating as expected. A reoccurrence of this issue is unlikely, however we may require additional database maintenances in the near future as follow-up actions to ensure that this remains the case. If required, these maintenances will be communicated and scheduled to minimize customer impact. 

‌

Akamai will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to our systems in an effort to 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.