Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)
Last updateresolvedSep 11 · 14:29 UTC
This incident has been resolved.
Reported by Temporal on their status page.
checked Sep 11, 2026 4:20 PM UTC · Temporal's official status page
Temporal is up and running.
Temporal is currently operational with all systems functioning normally.
All components operational
Email only. No password. No card.
Be the first to know
Statusfield watches Temporal alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
Temporal incident history
9 reports published by Temporal in the last 30 days
When Temporal breaks, it is typically resolved in 3h 45m — median across 14 resolved incidents over 90 days.
September 11, 2026
September 10, 2026
Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
Last updateresolvedSep 11 · 07:21 UTC
The environment has been validated and all residual issues have been cleared. This incident is now resolved.
Reported by Temporal on their status page.
September 3, 2026
Elevated Errors in us-west-2 Region
Last updateresolvedSep 4 · 05:28 UTC
As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved.
Reported by Temporal on their status page.
September 2, 2026
Low Rate of Namespace Create/Update Failures Across All Regions
Last updateresolvedSep 2 · 15:49 UTC
The rollback of the affected service has completed. Namespace configuration changes will resume as expected.
Reported by Temporal on their status page.
September 1, 2026
Elevated error rates in GCP us-central1
Last updateresolvedSep 1 · 21:43 UTC
GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.
Reported by Temporal on their status page.
August 21, 2026
Self-Signup Onboarding Access Restriction
Last updateresolvedAug 21 · 13:30 UTC
Self-Signup onboarding was inadvertently restricted after a rollout, preventing users from completing Self-Signup onboarding. The configuration change occurred on August 20 at 21:21 UTC, and the issue was noticed at approximately 12:40 UTC on August 21. The issue was mitigated at 13:01 UTC by correcting the onboarding configuration. The onboarding configuration was corrected, and Self-Signup onboarding functionality has returned to normal.
Reported by Temporal on their status page.
August 20, 2026
Customers in (GCP) us-west1 may experience elevated API latencies
Last updateresolvedAug 20 · 19:00 UTC
We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved.
Reported by Temporal on their status page.
August 13, 2026
Cloud Ops API — Elevated Error Rates and Latencies
Last updateresolvedAug 13 · 12:00 UTC
We experienced a brief period of elevated error rates and latency on the Cloud Ops API, lasting approximately 5 minutes (from 11.41 UTC to 11.46 UTC). The incident has been resolved, and the Cloud Ops API is operating normally. We are investigating the cause. We apologize for the disruption.
Reported by Temporal on their status page.
Customers in AWS us-west-2 may experience elevated API latencies
Last updateresolvedAug 13 · 12:27 UTC
We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved.
Reported by Temporal on their status page.