Linode incident: Service Issue - Object Storage

Affected components

• FR-PAR (Paris) Object Storage
• US-IAD (Washington) Object Storage
• US-LAX (Los Angeles) Object Storage
• US-ORD (Chicago) Object Storage
• US-SEA (Seattle) Object Storage

1. postmortemJul 21, 2026, 15:26 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 action

2. resolvedJul 18, 2026, 04:36 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

3. identifiedJul 18, 2026, 03:54 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.

4. investigatingJul 18, 2026, 03:34 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Linode's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC

How often does Linode have incidents?

Linode reported 10 incidents in the last 90 days. A typical incident lasted 2h 15m. See Linode's uptime and incident history