System Errors in EU-WEST-3

What to do

• Check whether you use Wasabi EU-West-3 (London) in eu, eu-west-3. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 1m it lasted.

  Anything that failed between 2025-07-25 19:31 UTC and 2025-07-25 22:32 UTC may need a replay.

• Subscribe to Wasabi's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=wasabi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Wasabi 5

1. investigatingJul 25, 2025, 7:31 PM UTC

   We are currently experiencing system errors in our EU-WEST-3 region. Customers may experience elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s). We will update this page as we have more information.

   provider

2. identifiedJul 25, 2025, 8:21 PM UTC

   We have identified the problem and our team is currently working to correct it.

   provider

3. monitoringJul 25, 2025, 9:26 PM UTC

   The issue has been corrected by our Operations Team and the EU-WEST-3 region is now fully operational. We will continue to monitor the region

   provider

4. resolvedJul 25, 2025, 10:32 PM UTC

   This incident has been resolved.

   provider

5. postmortemAug 27, 2025, 2:55 PM UTC

   On 25 July 2025 from 19:06 UTC to approximately 21:14 UTC, Wasabi's eu-west-3 \(London\) region experienced a service incident which resulted in elevated HTTP 5XX errors being returned for many request types to the region. The cause for the incident was an internal service failure, which prevented multiple services within the region from being able to successfully communicate across platforms. Due to this failure, our internal proxy service was unable to efficiently direct requests within the region, resulting in a degradation of the service and causing client requests to fail. Wasabi's Engineering and Operations teams worked to systematically restart impacted service hosts beginning at 19:20 UTC through 19:28 UTC. Once the hosts were back online, internal routing issues due to faulty configuration files required the team to manually correct the configurations and apply those to service hosts. By 21:24 UTC, all hosts and services were operating properly, and the region was operational.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.