GlobalOutageMap
← Live dashboard
Linode logoLinode

Service Issue - Object Storage

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update May 29, 2026, 06:23 PM · Resolved May 29, 2026, 06:23 PM

Between 10:13 UTC and 10:22 UTC on May 29, 2026, customers using Object Storage \(OBJ\) in London experienced 5xx errors when trying to access content stored in that location. While attempting to isolate a separate packet loss issue, Akamai sequentially upgraded 2 pairs of routers. The first pair of routers was upgraded successfully, but due to human error the second router pair's upgrade command was executed before the first pair had completed route convergence. This resulted in a temporary loss of routing paths for OBJ traffic in the London datacenter. The issue was quickly detected via...

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

GB-LON (London 2) Object Storage

Updates (2)

  1. Jun 8, 2026, 09:13 AM
    Service Issue - Object Storage

    Between 10:13 UTC and 10:22 UTC on May 29, 2026, customers using Object Storage \(OBJ\) in London experienced 5xx errors when trying to access content stored in that location. While attempting to isolate a separate packet loss issue, Akamai sequentially upgraded 2 pairs of routers. The first pair of routers was upgraded successfully, but due to human error the second router pair's upgrade command was executed before the first pair had completed route convergence. This resulted in a temporary loss of routing paths for OBJ traffic in the London datacenter. The issue was quickly detected via an

    Linode ↗
  2. May 29, 2026, 06:23 PM
    Service Issue - Object Storage

    Starting at around 10:07 UTC on May 29, 2026, Object Storage in London became unavailable. Affected customers were unable to access Object Storage during this time, and may have seen 500 or similar errors. This occurred as the result of an issue with a planned router upgrade. The router has since been brought back online, and we can confirm that the issue was mitigated at 10:19 UTC on May 29, 2026 and is no longer occurring. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prev

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.