- Level
- confirmed
- Worst impact
- Degraded
- Components
- Namespace Management
- Down Index
- 12of 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 2m it lasted.
Anything that failed between 2026-05-22 23:40 UTC and 2026-05-22 23:43 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
- investigating
Namespace creation, modification and deletion had increased latencies from 23:10 to 23:35 UTC. There is no impact to workflow operations
provider
- resolved
This incident has been resolved. Analysis shows the error was from our domain management vendor.
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-8b04d5358e
Is Temporal Cloud still down?
No, this incident was resolved 2026-05-22 23:43 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.
How long did it last?
2m, from 2026-05-22 23:40 UTC to 2026-05-22 23:43 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.