Linode experienced a minor incident on July 18, 2026 affecting US-IAD (Washington) Object Storage and US-ORD (Chicago) Object Storage and 1 more component, lasting 1h 1m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 18, 2026, 03:34 AM UTC
Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.
- identified Jul 18, 2026, 03:54 AM UTC
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.
- resolved Jul 18, 2026, 04:36 AM UTC
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.
- postmortem Jul 21, 2026, 03:26 PM UTC
On July 18, 2026, between approximately 00:30 UTC and 04:00 UTC, users might have experienced 5xx errors while trying to create a new bucket in the Object Storage for the following endpoints. * [us-ord-1.linodeobjects.com](http://us-ord-1.linodeobjects.com) * [us-lax-1.linodeobjects.com](http://us-lax-1.linodeobjects.com) * [us-iad-1.linodeobjects.com](http://us-iad-1.linodeobjects.com) * [us-sea-1.linodeobjects.com](http://us-sea-1.linodeobjects.com) * [fr-par-1.linodeobjects.com](http://fr-par-1.linodeobjects.com) The issue began when the infrastructure supporting Object Storage entered a degraded state across all nodes. This prevented the service from processing requests, resulting in failures during bucket creation operations. To mitigate the impact, we have applied a fix at the backend system responsible for bucket creation. The impact was mitigated following this action. Our subject matter experts are investigating the root cause and will take appropriate preventive actions. We apologize for the impact and appreciate your patience and ongoing support. We are making configuration and operational changes to our systems to help prevent this from happening again, and remain committed to continuous improvement. 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.