Intermittent Network Error - Wasabi Console

What to do

• Check whether you use Wasabi US-Central-1 (Texas), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-1 (London) and 1 more in eu, eu-central-1, eu-central-2, eu-west-1. 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 7h it lasted.

  Anything that failed between 2026-05-27 06:39 UTC and 2026-05-27 13:39 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 6

1. investigatingMay 27, 2026, 6:39 AM UTC

   We are currently investigating intermittent Network Errors when creating or accessing buckets via Wasabi Console in some regions.

   provider

2. investigatingMay 27, 2026, 9:12 AM UTC

   We are continuing to investigate this issue.

   provider

3. monitoringMay 27, 2026, 10:46 AM UTC

   The issue was identified and a fix implement by our team. We are currently monitoring our systems.

   provider

4. monitoringMay 27, 2026, 1:38 PM UTC

   We are continuing to monitor for any further issues.

   provider

5. resolvedMay 27, 2026, 1:39 PM UTC

   This incident has been resolved.

   provider

6. postmortemJun 3, 2026, 1:31 PM UTC

   Between 2026-05-26 13:40 UTC and 2026-05-27 09:20 UTC, some customers experienced intermittent difficulties accessing buckets through the Wasabi Console in the us-central-1, eu-central-1, eu-central-2, and eu-west-1 regions. The incident was caused by a deployment inconsistency introduced during a backend system update. As a result, a subset of backend services was running a different software version than expected, leading to intermittent failures when customers accessed bucket information through the Console. Following identification of the issue, Wasabi strengthened its deployment validation process to ensure software version consistency across production environments before feature activation. Additional release verification controls have been implemented to better align tested and deployed software, and we are evaluating improvements to version reporting and monitoring to increase deployment visibility and help identify potential discrepancies earlier.

   provider

Corrections

None so far.

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