- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-East-1 (N. Virginia), US-East-2 (N. Virginia)
- Regions
- us, us-east-1, us-east-2
- Down Index
- 31of 100
What to do
Check whether you use Wasabi US-East-1 (N. Virginia), US-East-2 (N. Virginia) in us, us-east-1, us-east-2. 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 2h 13m it lasted.
Anything that failed between 2025-06-26 18:01 UTC and 2025-06-26 20:14 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 4
- investigating
We are currently investigating system errors in our US-EAST-1 and US-EAST-2 regions. 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
- monitoring
We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.
provider
- resolved
This incident has been resolved. Please reach out to support@wasabi.com for any further assistance.
provider
- postmortem
On 26 June 2025 from 18:30 UTC to 19:12 UTC, we experienced system errors in our us-east-1 and us-east-2 regions due to an unplanned data center thermal event. Starting at 18:30 UTC, our Operations team was notified of a spike in thermal temperature within several servers within the data centers. Due to the increase in temperature, multiple storage pools shut down power to the enclosed drives to preserve drive health and data integrity. Due to the powering down of these drives, several read & write operations resulted in HTTP 5XX errors. Upon notification of this thermal event, Wasabi’s Operations Team worked with the data center team to diagnose and correct the cooling issue and power cycled each impacted server. Once each server was fully powered up, all services was restored. By 19:12 UTC, all services were fully operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-690b0e97b4
Is Wasabi still down?
No, this incident was resolved 2025-06-26 20:14 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
2h 13m, from 2025-06-26 18:01 UTC to 2025-06-26 20:14 UTC, by the times Wasabi posted.
What was affected?
Wasabi named US-East-1 (N. Virginia), US-East-2 (N. Virginia) in us, us-east-1, us-east-2.
What caused it?
Wasabi hasn't published a root cause. If it does, it shows here.
Where does this come from?
Wasabi's official status page, https://status.wasabi.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.