Linode Status

Postmortem: Beginning approximately mid-September, a risk of serious customer impact to the Linode API and Cloud Manager surfaced due to continued increases in traffic from unoptimized queries to the management database. This resource utilization increase did result in intermittent and brief periods of database connection rejections which resolved automatically. Akamai analyzed and optimized identified queries, moving queries to target read-only resources where possible. We also made firmware changes to database firmware during a scheduled maintenance on October 1, 2025, which was a step towards long-term stability of this system. Due to the efforts and actions taken to optimize load on this system, we have not seen any issues since October 7, 2025. 

To prevent this issue from occurring in the future, we have instituted and will continue to iterate on finer-grained monitoring and alerting to quickly ascertain which applications are causing additional unoptimized load. We have also instituted a more rigorous process to review and optimize traffic on an ongoing basis.

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: 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.

Monitoring: We have implemented a fix for this issue as of October 7, 2025. Based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000cRKGoCAO

We will continue to monitor to ensure that the impact has been fully mitigated.

Monitoring: We have not seen issues since 7 October 2025 and are continuing to monitor further. If you are still experiencing issues, please open a Support ticket for assistance.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A database maintenance was performed and we are currently monitoring the results. If you are still experiencing issues, please open a Support ticket for assistance.

Investigating: We are continuing to investigate this issue.

Investigating: Our team is investigating a service issue that intermittently triggers 5XX responses in the Cloud Manager (https://cloud.linode.com/) and API request failures for brief periods. We will share additional updates as we have more information.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: At 18:41 UTC on October 14th, 2025 we have been able to correct the issues affecting connectivity in our Washington (IAD3) 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.

Investigating: We are continuing to investigate this issue and we will share additional updates as we have more information.

Investigating: Our team is investigating an emerging service issue affecting Networking in IAD3. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional issues with the Object Storage service in any of the impacted regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. The impacted regions and their impact windows are listed below. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Location and time, in UTC, all dated 2025-10-15: Chicago (US-ORD): 10:46-10:52 London (GB-LON): 10:52-10:59 Washington, DC (US-IAD): 12:26-13:54 Seattle (US-SEA): 13:14-13:23 Singapore 2 (SG-SIN-2): 14:00-14:09 Melbourne (AU-MEL): 14:57-15:04 Tokyo 3 (JP-TYO-3): 12:34-12:42

Investigating: We have narrowed down the impacted regions to be E2 and E3 endpoint regions. Our list below has been updated to reflect this.

Investigating: We are continuing to investigate this issue.

Investigating: Our team is investigating an emerging service issue affecting Object Storage in multiple locations. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional issues with the Object Storage service in any of the impacted regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. The impacted regions and their impact windows are listed below. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Location and time, in UTC, all dated 2025-10-15: Chicago (US-ORD): 10:46-10:52 London (GB-LON): 10:52-10:59 Washington, DC (US-IAD): 12:26-13:54 Seattle (US-SEA): 13:14-13:23 Singapore 2 (SG-SIN-2): 14:00-14:09 Melbourne (AU-MEL): 14:57-15:04 Tokyo 3 (JP-TYO-3): 12:34-12:42

Investigating: We have narrowed down the impacted regions to be E2 and E3 endpoint regions. Our list below has been updated to reflect this.

Investigating: We are continuing to investigate this issue.

Investigating: Our team is investigating an emerging service issue affecting Object Storage in multiple locations. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional issues with the Object Storage service in any of the impacted regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. The impacted regions and their impact windows are listed below. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Location and time, in UTC, all dated 2025-10-15: Chicago (US-ORD): 10:46-10:52 London (GB-LON): 10:52-10:59 Washington, DC (US-IAD): 12:26-13:54 Seattle (US-SEA): 13:14-13:23 Singapore 2 (SG-SIN-2): 14:00-14:09 Melbourne (AU-MEL): 14:57-15:04 Tokyo 3 (JP-TYO-3): 12:34-12:42

Investigating: We have narrowed down the impacted regions to be E2 and E3 endpoint regions. Our list below has been updated to reflect this.

Investigating: We are continuing to investigate this issue.

Investigating: Our team is investigating an emerging service issue affecting Object Storage in multiple locations. We will share additional updates as we have more information.