Linode experienced a minor incident on December 16, 2025 affecting US-Southeast (Atlanta), lasting 3h 33m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 16, 2025, 01:44 AM UTC
Our team is investigating an issue in the US-Southeast (Atlanta) data center. During this time, users may experience interruption of service or will be unable to access their Linodes. The impact is limited to some hosts in this data center. We will share additional updates as we have more information.
- investigating Dec 16, 2025, 02:42 AM UTC
We are continuing to investigate this issue. We will share additional updates as we have more information.
- investigating Dec 16, 2025, 03:08 AM UTC
Our team has identified the issue in the US-Southeast (Atlanta) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
- monitoring Dec 16, 2025, 04:31 AM UTC
At this time, we have been able to correct the issues affecting connectivity in our US-Southeast (Atlanta) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
- resolved Dec 16, 2025, 05:17 AM UTC
We haven’t observed any additional issues, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
- postmortem Dec 16, 2025, 06:25 AM UTC
Starting around 23:15 UTC on December 15, 2025, Akamai received several internal alerts indicating issues with some hosts in the US-Southeast \(Atlanta\) data center \(ATL1 DC\). The investigation revealed that the issue was caused by a power supply failure in one of the racks in this data center. Customers with Linodes on these hosts would have experienced an interruption in the service. As part of the mitigation effort, Akamai manually turned down these hosts at around 02:00 UTC on December 16, 2025, and started the drive transplant activity, which was to migrate the customers to another rack. Drive transplant was believed to be the fastest mitigation action, without knowing the root cause of the outage. Further investigation indicated that the loss of power supply was due to a planned maintenance activity at the data center. The planned maintenance was communicated to Akamai, but the internal teams missed migrating the customers to another rack \(before the maintenance\) due to an internal communication gap. The power supply was restored around 03:10 UTC on December 16, 2025. However, the drive transplant action was in progress at that time, and customer impact continued until the completion of the drive transplant activity at around 04:20 UTC on December 16, 2025. We will continue to investigate the root cause of the communication gap and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. 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.