Is Temporal Cloud down?
Temporal Cloud status · Data & Backend · checked (17s ago)
Also searched as Temporal.
Partly — Temporal Cloud is up but running slower than usual (Partially Degraded Service).
According to Temporal Cloud's official status page, Temporal Cloud was reporting “Partially Degraded Service” when isuptime last checked at . Over the last 30 days, Temporal Cloud's feed reported no outage in 100.00% of our checks.
What to do while Temporal Cloud is down
isuptime cannot fix Temporal Cloud, and neither can you. These are the things that are actually worth doing until it comes back.
- Read what Temporal Cloud has actually published. Their incident notes say which components are affected and usually carry an estimate, which is more than any third party can tell you. Temporal Cloud's status page
- Stop retrying in a loop. If your code calls Temporal Cloud, back off exponentially and cap the retries. A retry storm from every client at once is a large part of why outages take as long to clear as they do, and it will exhaust your own quota before the service returns.
- Get told when it clears, instead of refreshing. The bell in the header sets up a browser notification, or a Discord, Slack or Telegram webhook, for the moment Temporal Cloud's status changes.
Is Temporal Cloud down for you right now?
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.
What Temporal Cloud is
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.
What Temporal Cloud's status feed covers
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.
Temporal Cloud uptime, last 30 days
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.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 17s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
GrafanaMinor Service Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
Temporal Cloud response time trend
Each point is one check of Temporal Cloud's status endpoint.
Which Temporal Cloud features are affected?
- Capacity — degraded_performance
- Google Cloud Platform (GCP) — degraded_performance
Temporal Cloud outage history
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.
- Intermittent request failures for some namespaces in GCP us-east4
resolved · Oct 31, 01:31 PM (3d ago)
- Elevated connection resets for some GCP namespaces
resolved · Oct 19, 10:13 PM (15d ago)
- New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3
monitoring · Oct 15, 05:12 PM (19d ago)
- Elevated latency and errors in GCP us-west1
resolved · Oct 14, 01:20 PM (20d ago)
- Elevated latency and errors in AWS us-east-1
resolved · Oct 9, 10:33 PM (25d ago)
- Elevated error rates for cross-region traffic between US AWS regions
resolved · Oct 9, 10:25 PM (25d ago)
- Elevated GCP storage latency in us-central1 – precautionary namespace failover
resolved · Oct 8, 09:53 PM (26d ago)
- Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI
resolved · Oct 5, 08:23 PM (29d ago)
- UI Disruptions in GCP us-central1
resolved · Oct 1, 09:06 PM (33d ago)
- Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors
resolved · Oct 1, 02:00 PM (33d ago)
- Increased latency in region us-west-2
resolved · Sep 27, 01:01 AM (38d ago)
- Some customers may have incorrectly received a "credit expiry notification"
resolved · Sep 18, 03:54 PM (46d ago)
- Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)
resolved · Sep 11, 10:10 AM (54d ago)
- Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
resolved · Sep 10, 08:51 PM (54d ago)
- Elevated Errors in us-west-2 Region
resolved · Sep 3, 09:12 PM (61d ago)
- Low Rate of Namespace Create/Update Failures Across All Regions
resolved · Sep 2, 03:26 PM (62d ago)
- Elevated error rates in GCP us-central1
resolved · Sep 1, 03:47 PM (63d ago)
- Self-Signup Onboarding Access Restriction
resolved · Aug 21, 01:30 PM (74d ago)
- Customers in (GCP) us-west1 may experience elevated API latencies
resolved · Aug 20, 03:20 PM (75d ago)
- Cloud Ops API — Elevated Error Rates and Latencies
resolved · Aug 13, 12:00 PM (83d ago)
Temporal Cloud status — frequently asked
- Is Temporal Cloud down right now?
- Partly — Temporal Cloud is up but running slower than usual (Partially Degraded Service). Checked (17s ago).
- What is Temporal Cloud's status right now?
- Temporal Cloud is reporting “Partially Degraded Service” on its official status page — Degraded — as of . That status feed answered our last check in 1.06 s. isuptime reads this from Temporal Cloud's own published feed and does not test Temporal Cloud independently.
- When did Temporal Cloud last go down?
- The most recent incident Temporal Cloud published was “Intermittent request failures for some namespaces in GCP us-east4”, opened Oct 31, 01:31 PM UTC (3d ago) and marked resolved Oct 31, 02:16 PM UTC. That is the latest entry in Temporal Cloud's own incident feed, not every problem users experienced.
- What is Temporal Cloud's uptime?
- isuptime does not measure Temporal Cloud's uptime directly — it reads Temporal Cloud's own published status feed. Over the last 30 days, Temporal Cloud's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is Temporal Cloud down for everyone?
- Temporal Cloud is reporting a problem on its own status page, so this is affecting other users too, not just you.
Temporal Cloud says operational but it is not working for me
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.