Linode Status

Postmortem: On Aug 13, 2025, at ~06:00 UTC, Akamai identified an issue with Cloud Manager where cloud.linode.com was inaccessible. The issue also impacted Application Programming Interface (API), internal tooling, admin, login, etc.

As a result, our end users might have seen 5xx login errors while accessing cloud.linode.com and were unable to use the cloud interface. 

Our investigation found that the internal system enabled a new feature globally which resulted in more complex queries blocking the database. This feature was enabled gradually in several phases, unfortunately no previous phase manifested any problem. Disabling the new feature resolved the problem, stability restored after rolling back the recent change.

To address the problem, we reverted the problematic configuration change. Throughout this process, we conducted extensive testing and validation operations. The issue was mitigated at 06:34 UTC on August 13, 2025.

To prevent a recurrence of this problem, we are conducting a detailed review of queries for a similar pattern as the one which caused this problem. We are also reviewing our internal architecture to identify long term improvements to prevent this type of issue. 

‌

‌

‌

‌

‌

‌

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.

Resolved: Our team investigated a service issue that affected the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users might have experienced issues when attempting to access these systems. At this time we have been able to correct the issue affecting the Cloud Manager and API. We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Resolved: This incident has been resolved.

Identified: Between approximately 19:02 – 19:07 UTC, and then again between 19:20 – 20:04 UTC, we observed a period of connectivity issues in MAD2. The issue subsided after we took a border router out of service. No further network issues have been observed since the loss subsided around 20:04 UTC. We identified the issue and a fix is being implemented.

Investigating: Our team is investigating an issue affecting connectivity in our ES-MAD (Madrid) 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.