- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1, us-west-2
- Down Index
- 35of 100
What to do
Check whether you use Temporal Cloud in us, us-east-1, 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 22h 24m it lasted.
Anything that failed between 2026-07-01 18:02 UTC and 2026-07-02 16:26 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
- identified
Customers on the latest SDK versions may see decompression errors when calling the GetSystemInfo and gRPC health check endpoints, and in rare cases, some workflows may hit a non-determinism error (NDE) during replay. A fix for this is rolling out. Affected versions - Java 1.36.0 Go 1.45.0 TypeScript 1.19.0 Rust 0.5.0 Python 1.29.0 Workaround - Disable gzip compression in the SDK client (set gRPC compression to none)
provider
- identified
Fix is being rolled out across all regions, current impact is limited to us-west-2 and us-east-1 regions. All systems stable and we're actively monitoring this. Next update will be posted once rollouts completed.
provider
- monitoring
The fix has been rolled out across all regions, and we are actively monitoring.
provider
- resolved
The rollout is complete and resolves the compression issues. All listed affected versions should no longer experience any compression-related errors.
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-596eb3b791
Is Temporal Cloud still down?
No, this incident was resolved 2026-07-02 16:26 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
22h 24m, from 2026-07-01 18:02 UTC to 2026-07-02 16:26 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named in us, us-east-1, 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.