Linode incident
Service Issue - Cloud Manager, Linode DB and API
Linode experienced a minor incident on November 22, 2025 affecting US-East (Newark) and Linode Manager and API and 1 more component, lasting 26d 10h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 22, 2025, 11:37 AM UTC
Our team is investigating an emerging service issue affecting Cloud Manager and API in all regions. We will share additional updates as we have more information.
- investigating Nov 22, 2025, 12:25 PM UTC
We are continuing to investigate this issue. We will share additional updates as we have more information.
- investigating Nov 22, 2025, 02:02 PM UTC
Our team is continuing to investigate the root cause of a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. We applied mitigation steps and systems began recovering at approximately 13:35 UTC on Saturday November 22, 2025. We will share additional updates as we have more information.
- investigating Nov 22, 2025, 02:07 PM UTC
We are continuing to investigate this issue.
- monitoring Nov 22, 2025, 03:14 PM UTC
At this time we have been able to correct the issue affecting the Cloud Manager and API. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
- monitoring Dec 03, 2025, 10:56 PM UTC
We are continuing to monitor to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
- resolved Dec 18, 2025, 10:32 PM UTC
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.
- postmortem Dec 23, 2025, 01:45 AM UTC
On November 22, 2025, between approximately 10:40 UTC and 13:35 UTC, Akamai experienced query congestion due to lock contention on a database backing Compute infrastructure. During this time, customers would have experienced issues creating, autoscaling, or otherwise managing Linodes. Customer support was also impacted by an inability to update customer cases during this timeframe. To mitigate this issue, Akamai identified multiple long-running queries at the core of the contention and manually stopped them to allow the standard flow of read/write operations to resume, restoring service. To prevent this issue from occurring again, Akamai will implement additional monitoring and automated remediation processes based on findings from this incident. 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.