- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-west-2
- Regions
- us, us-west-2
- Down Index
- 24of 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 40m it lasted.
Anything that failed between 2026-08-13 11:47 UTC and 2026-08-13 12:27 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 4
- investigating
Customers in AWS us-west-2 may experience elevated API latencies
provider
- monitoring
The incident has been mitigated, and we are monitoring
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now 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-dc9ee9fff3
Is Temporal Cloud still down?
No, this incident was resolved 2026-08-13 12:27 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
40m, from 2026-08-13 11:47 UTC to 2026-08-13 12:27 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.