Temporal Cloud status history
77 incidents over the last year, newest first; 99.99% uptime (90 days), 99.99% uptime (12 months). History from before down.guide started reading the page is imported from Temporal Cloud's own archive.
Month
2026-11
1 incident
- Temporal CloudDegradedSome customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures
Temporal Cloud says some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures. The provider identified the issue and applied a mitigation, and it is now monitoring the results.
Month
2026-10
10 incidents
- Temporal CloudDegradedIntermittent request failures for some namespaces in GCP us-east4
- Temporal CloudDegradedElevated connection resets for some GCP namespaces
- Temporal CloudDegradedNew namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3
- Temporal CloudDegradedElevated latency and errors in GCP us-west1
- Temporal CloudDegradedElevated latency and errors in AWS us-east-1
- Temporal CloudDegradedElevated error rates for cross-region traffic between US AWS regions
- Temporal CloudDegradedElevated GCP storage latency in us-central1 – precautionary namespace failover
- Temporal CloudMajor outageIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI
- Temporal CloudDegradedUI Disruptions in GCP us-central1
- Temporal CloudDegradedCustomers in us-east4 may have experienced elevated API latencies and resource exhausted errors
Month
2026-09
7 incidents
- Temporal CloudDegradedIncreased latency in region us-west-2
- Temporal CloudDegradedSome customers may have incorrectly received a "credit expiry notification"
- Temporal CloudDegradedSome customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)
- Temporal CloudPartial outageCustomers in us-central1 and asia-southeast2 may experience a delay in workflow progress
- Temporal CloudDegradedElevated Errors in us-west-2 Region
- Temporal CloudDegradedLow Rate of Namespace Create/Update Failures Across All Regions
- Temporal CloudDegradedElevated error rates in GCP us-central1
Month
2026-08
5 incidents
- Temporal CloudDegradedSelf-Signup Onboarding Access Restriction
- Temporal CloudDegradedCustomers in (GCP) us-west1 may experience elevated API latencies
- Temporal CloudDegradedCloud Ops API — Elevated Error Rates and Latencies
- Temporal CloudDegradedCustomers in AWS us-west-2 may experience elevated API latencies
- Temporal CloudDegradedSome customers in AWS eu-west-1 may experience elevated latencies
Month
2026-07
21 incidents
- Temporal CloudMajor outageUsage API and UI are experiencing an outage
- Temporal CloudDegradedSome customers in AWS us-west-2 may experience degraded visibility performance
- Temporal CloudDegradedSome customers in GCP us-east4 may experience elevated latencies
- Temporal CloudDegradedSome customers in AWS us-west-2 may experience degraded visibility performance
- Temporal CloudDegradedSome customers in GCP us-east4 may experience elevated latencies
- Temporal CloudDegradedSome customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1) from 12:45 to 13:25 UTC
- Temporal CloudDegradedSome customers in AWS eu-west-1 may experience elevated latencies
- Temporal CloudDegradedCustomers in AWS eu-west-1 may experience elevated API latencies
- Temporal CloudDegradedSome customers may experience a loss in metrics (v0 and v1) starting 19:00 UTC
- Temporal CloudPartial outageCustomers in us-east-2 may experience some visibility related errors
- Temporal CloudDegradedElevated latencies in us-east-1
- Temporal CloudDegradedBroken Temporal skipping test server link
- Temporal CloudDegradedSome customers in AWS us-west-2 may experience unjustified throttling errors
- Temporal CloudDegradedSome customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies
- Temporal CloudDegradedCustomers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies
- Temporal CloudDegradedSome customers in AWS us-east-1 may experience elevated rate of transient API errors
- Temporal CloudDegradedCustomers in GCP us-east4 may experience elevated API latencies
- Temporal CloudDegradedSome customers in GCP europe-west3 may experience elevated API latencies
- Temporal CloudDegradedSome customers in AWS us-east-2 may have experienced elevated API latencies and errors
- Temporal CloudDegradedSome customers in GCP us-west1 may have experienced elevated API latencies
- Temporal CloudDegradedErrors on GetSystemInfo and healthcheck endpoints for latest SDK versions
Month
2026-06
7 incidents
- Temporal CloudDegradedGCP customers in europe-west3 are experiencing elevated errors for Visibility API calls
- Temporal CloudDegradedSome customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.
- Temporal CloudDegradedAudit logs temporarily delayed for a few hours — no data loss.
- Temporal CloudDegradedCustomers might observe Usage API returning missing or delayed data
- Temporal CloudDegradedGCP customers in us-east4 are experiencing elevated errors for Visibility API calls
- Temporal CloudDegradedSome customers in AWS sa-east-1 may experience elevated API latencies
- Temporal CloudDegradedSome customers may be experiencing stuck workflows or activities
Month
2026-05
11 incidents
- Temporal CloudDegradedSome customers in us-west-2 may experience elevated rate of API errors & higher latencies
- Temporal CloudDegradedSome customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors
- Temporal CloudDegradedSome customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors
- Temporal CloudDegradedNamespace creation and modification availablity degraded
- Temporal CloudDegradedCustomers using OpenMetric for external observability may see gaps in some metrics
- Temporal CloudDegradedTemporal UI was unable to display human readable execution details
- Temporal CloudDegradedSome customers in GCP us-east4 experienced elevated API latencies
- Temporal CloudDegradedSome customers in GCP us-east4 experienced elevated API latencies
- Temporal CloudDegradedSome customers in AWS us-east-1 may experience elevated API latencies
- Temporal CloudPartial outageSome customers in us-west-2 may experience elevated rate of API errors and high latency
- Temporal CloudPartial outageSome customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errors
Month
2026-04
5 incidents
- Temporal CloudDegradedDegraded Child Workflow Execution
- Temporal CloudDegradedSome customers in us-west-2 experiencing increased visibility API latencies
- Temporal CloudDegradedBilling API Data Freshness Delay
- Temporal CloudDegradedSome customers briefly experienced elevated errors for Web UI and Cloud Ops API
- Temporal CloudDegradedSome customers connecting over PrivateServiceConnect in uscentral1 experienced elevated errors
Month
2026-03
10 incidents
- Temporal CloudDegradedSmall number of customers in AWS us-west-2 may experience delayed execution of schedules
- Temporal CloudDegradedSmall number of customers in GCP europe-west3 may experience delayed firing of timers
- Temporal CloudDegradedElevated latencies and errors in certain namespaces in AWS us-east-1 region
- Temporal CloudDegradedA small number of customers in AWS experienced API timeouts.
- Temporal CloudDegradedSome customers in GCP us-east4 experienced elevated API latencies.
- Temporal CloudDegradedA small number of customers in AWS us-east-1 experienced elevated latencies.
- Temporal CloudDegradedSome customers using cloud ops API may experience higher latency and elevated rate of API errors
- Temporal CloudDegradedCustomers using external observability may experience elevated rate of API errors
- Temporal CloudDegradedSome customers in us-west-2 may have experienced elevated API latencies & error
- Temporal CloudDegradedDelay in modifications of Authorization settings