- Level
- confirmed
- Worst impact
- Partial outage
- Components
- US-West-1 (Oregon)
- Regions
- us, us-west-1
- Down Index
- 36of 100
What to do
Check whether you use Wasabi US-West-1 (Oregon) in us, us-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 1h 31m it lasted.
Anything that failed between 2024-09-25 13:51 UTC and 2024-09-25 15:22 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 7
- investigating
We are currently investigating system errors occurring in our US-WEST-1 region.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
Our Operations Team has identified the issue and is working to correct the system errors.
provider
- monitoring
Our Operations Team has corrected the issue, and the US-WEST-1 region is back in an operational state. We will continue to monitor the region.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
This incident is now resolved. Please reach out to support@wasabi.com if you continue to see any errors related to this incident.
provider
- postmortem
From 2024-09-25 13:49 UTC to 2024-09-25 13:54 UTC, an incident occurred in the Hillsboro region, resulting in performance degradation for customers and impacting their ability to make S3 API calls against buckets in the region. During an upgrade to the region, the Operations team encountered an issue where a misconfiguration caused a service to falsely report as ready for operation. This resulted in service readiness failures and triggered failures within the region. To address the situation, the Operations Team corrected the misconfiguration and restarted the affected service. By 13:54 UTC, the S3 service in the US-WEST-1 region was fully restored, and normal operations resumed.
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-60b0ced13a
Is Wasabi still down?
No, this incident was resolved 2024-09-25 15:22 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
1h 31m, from 2024-09-25 13:51 UTC to 2024-09-25 15:22 UTC, by the times Wasabi posted.
What was affected?
Wasabi named US-West-1 (Oregon) in us, us-west-1.
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.