- Level
- confirmed
- Worst impact
- Degraded
- Components
- Namespace Management
- Down Index
- 16of 100
What to do
Check whether you use Temporal Cloud Namespace Management. 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 23m it lasted.
Anything that failed between 2026-09-02 15:26 UTC and 2026-09-02 15:49 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 2
- identified
We have identified an issue where some customers may receive failures when creating or updating namespaces. We are currently rolling back the affected service. Temporal Cloud will ensure failures are manually retried.
provider
- resolved
The rollback of the affected service has completed. Namespace configuration changes will resume as expected.
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-43195a77bf
Is Temporal Cloud still down?
No, this incident was resolved 2026-09-02 15:49 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
23m, from 2026-09-02 15:26 UTC to 2026-09-02 15:49 UTC, by the times Temporal Cloud posted.
What was affected?
Temporal Cloud named Namespace Management.
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.