Linode Status

Current Status

Service Issue - Object Storage

Incident Report for Linode

Postmortem

Beginning on February 19, 2025, at 23:00 UTC, we observed 403 errors when customers tried to access E2 and E3 endpoint buckets with "Public Read" permissions in Object Storage. The issue was traced to a recent software update that changed the default behavior for "Public Read" access, now requiring explicit bucket policies. Previously, legacy access allowed “Public Read” access without these policies. Customers transitioning from older to newer and enhanced Object Storage infrastructure versions were not expecting this change, causing the errors. We rolled back the enhanced version at 12:42 UTC on February 20, 2025, and confirmed resolution by 13:16 UTC. 

To prevent future issues, we are enhancing communication around default behavior changes, improving testing for public access scenarios, and updating documentation to clarify the need for bucket policies in the enhanced version compared to the legacy version.

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.

Posted Mar 21, 2025 - 20:58 UTC

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.
Posted Feb 20, 2025 - 18:00 UTC

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.
Posted Feb 20, 2025 - 15:00 UTC

Update

We are continuing to investigate this issue. Impacted regions are updated.
Posted Feb 20, 2025 - 02:47 UTC

Update

We are continuing to investigate the issue. The impacted Object Storage regions are limited to US-SEA (Seattle), EU-WEST (London), AU-MEL (Melbourne), EU -Central (Frankfurt), AP-South (Singapore), AP-WEST (Mumbai).
Posted Feb 20, 2025 - 02:37 UTC

Investigating

We are currently investigating an issue impacting the Object Storage service. During this time, customers may experience 403 access errors when attempting to access E2 and E3 endpoint buckets that are configured with "Public Read" permissions.
Posted Feb 20, 2025 - 01:36 UTC
This incident affected: Object Storage (EU-Central (Frankfurt) Object Storage, AP-South (Singapore) Object Storage, US-SEA (Seattle) Object Storage, AP-West (Mumbai), EU-West (London), GB-LON (London 2), AU-MEL (Melbourne)).