- Level
- confirmed
- Worst impact
- Partial outage
- Components
- us-west-2
- Regions
- us, us-west-2
- Down Index
- 41of 100
What to do
Check whether you use Temporal Cloud us-west-2 in us, us-west-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 16h 2m it lasted.
Anything that failed between 2026-05-05 05:43 UTC and 2026-05-05 21:46 UTC may need a replay.Subscribe to Temporal Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=temporal-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Temporal Cloud 9
- investigating
We are currently investigating the issue.
provider
- investigating
This is still in investigation
provider
- identified
We are working to mitigate the issue. Error rates are recovering.
provider
- identified
We continue working to mitigate the issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.
provider
- monitoring
We are continuing to monitor the affected cell and have kept our status page in a monitoring state while we validate stability. As a precaution, Multi-region Namespace traffic has been failed over to secondary regions, where it continues to be served normally. While we complete stabilization work, Multi-region Namespaces will continue running from secondary regions. Our current priority is to ensure the affected cell is stable and operating normally. Once confirmed, and the incident is resolved, we will restore Multi-region Namespace traffic to primary regions. For Multi-region Namespaces failed over by Temporal, we will manage fail back. For manually failed over namespaces, customers can initiate fail back once the incident is resolved.
provider
- monitoring
Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.
provider
- resolved
This incident has been resolved.
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-b7b32bd004
Is Temporal Cloud still down?
No, this incident was resolved 2026-05-05 21:46 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
16h 2m, from 2026-05-05 05:43 UTC to 2026-05-05 21:46 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named us-west-2 in us, us-west-2.
What caused it?
Temporal Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Temporal Cloud's official status page, https://status.temporal.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.