Service Issue - Object Storage (LAX)
Incident
Report for Linode
Postmortem
Starting March 15, 2025, multiple customers started seeing 502 and 503 response codes for object storage from the Los Angeles (“LAX”) datacenter. After investigating the issue, we have established that it was caused by a software defect. To address it, we have installed a new software version and we have monitored the LAX datacenter for storage performance.
After monitoring the LAX datacenter for an extended period of time, we have concluded that the issue has been addressed and normal operations could resume.
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 Object Storage service, 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. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Identified
Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Investigating
Our team is investigating an issue affecting the Object Storage service in the Los Angeles region. During this time, users may experience connection timeouts and errors with this service.
This incident affected: Regions (US-LAX (Los Angeles)).