- Level
- confirmed
- Worst impact
- Degraded
- Components
- us-west-2
- Regions
- us, us-west-2
- Down Index
- 30of 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 8h 16m it lasted.
Anything that failed between 2026-09-03 21:12 UTC and 2026-09-04 05:28 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
We are investigating connectivity errors affecting some customers with namespaces in the us-west-2 region relating to an AWS outage in this region. Our team is actively assessing impact and working on mitigation. Affected MRN namespaces have been failed over. We will provide updates as more information becomes available. https://health.aws.amazon.com/health/status
provider
- monitoring
We are starting to see recovery as of 23:01 UTC.
provider
- monitoring
As of 9/4 00:07 UTC, AWS has confirmed the incident impacting us-west-2 is resolved. After a further period of monitoring, we have confirmed service is stable and have begun failing back the affected MRN namespaces.
provider
- resolved
As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is 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-f7dfc56ac6
Is Temporal Cloud still down?
No, this incident was resolved 2026-09-04 05:28 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
8h 16m, from 2026-09-03 21:12 UTC to 2026-09-04 05:28 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.