Loading status…
Temporal Cloud status · Data & Backend · checked (2s ago)
Also searched as Temporal.
No — Temporal Cloud is not down. All Temporal Cloud systems are reported operational.
According to Temporal Cloud's official status page, Temporal Cloud was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Temporal Cloud's feed reported no outage in 100.00% of our checks.
Everything above is read from Temporal Cloud's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Temporal Cloud in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Temporal Cloud is the managed version of the Temporal workflow engine — durable execution for long-running, multi-step processes that must survive crashes and restarts. Your workers run in your own infrastructure and connect out to Temporal Cloud, which holds the event history.
The status page reports per region and separates the service from the web UI. The architecture is what makes this readable: your workers are yours, so a Temporal Cloud incident stops workflows progressing rather than losing them — durable execution means they resume where they stopped. The UI being down affects visibility only.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Temporal Cloud's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Temporal Cloud was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Temporal Cloud's status endpoint.
Temporal Cloud has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Temporal Cloud posted itself — not every problem users hit.
resolved · Sep 18, 03:54 PM (1d ago)
resolved · Sep 11, 10:10 AM (8d ago)
resolved · Sep 10, 08:51 PM (9d ago)
resolved · Sep 3, 09:12 PM (16d ago)
resolved · Sep 2, 03:26 PM (17d ago)
resolved · Sep 1, 03:47 PM (18d ago)
resolved · Aug 21, 01:30 PM (29d ago)
resolved · Aug 20, 03:20 PM (30d ago)
resolved · Aug 13, 12:00 PM (37d ago)
resolved · Aug 13, 11:47 AM (37d ago)
resolved · Aug 5, 01:17 PM (45d ago)
resolved · Jul 31, 10:46 PM (50d ago)
resolved · Jul 23, 07:11 PM (58d ago)
resolved · Jul 22, 12:35 PM (59d ago)
resolved · Jul 20, 06:29 PM (61d ago)
resolved · Jul 20, 05:44 PM (61d ago)
resolved · Jul 20, 01:55 PM (61d ago)
resolved · Jul 20, 01:47 PM (61d ago)
resolved · Jul 17, 02:30 PM (64d ago)
resolved · Jul 16, 10:26 PM (65d ago)
A workflow that is not progressing is usually a worker problem — check that your workers are running, polling the right task queue and on a compatible version. Non-deterministic changes to workflow code fail replay with errors that look like platform faults. Namespace-level rate limits and retention settings also produce failures that no incident explains.
