Skip to content

Incident detail

Service Issue - Object Storage

Resolved incidentMinor

Timeline window

to

Get alerted the next time Linode breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Linode posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.

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

  3. 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

  4. Resolved

    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.

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

Keep exploring

More from Linode

Neighboring incidents on Linode's timeline and the rest of their record on OutageDeck.