Temporal Outage History

84 incidents recorded over the last 365 days, 83 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Temporal status95.71% uptime history

Every Recorded Temporal Incident

Temporal incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 21, 2026Self-Signup Onboarding Access RestrictionSelf-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…-13 minResolved
Aug 20, 2026Customers in (GCP) us-west1 may experience elevated API latenciesWe have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved.3h 39mResolved
Aug 13, 2026Cloud Ops API — Elevated Error Rates and LatenciesWe 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…-37 minResolved
Aug 13, 2026Customers in AWS us-west-2 may experience elevated API latenciesWe have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved.39 minResolved
Aug 5, 2026Some customers in AWS eu-west-1 may experience elevated latenciesNo further errors and latencies have been observed and systems remain stable. The issue was capacity related and caused elevated database latencies. The service was scaled up and closely monitored until all latencies…53h 8mResolved
Jul 31, 2026Usage API and UI are experiencing an outageThis incident has been resolved.2h 13mResolved
Jul 23, 2026Some customers in AWS us-west-2 may experience degraded visibility performanceThis incident has been resolved. Visibility performance has been restored.47 minResolved
Jul 22, 2026Some customers in GCP us-east4 may experience elevated latenciesAPI latencies have recovered and remained stable since the observed periods of elevated latency.28 minResolved
Jul 21, 2026Audit Log MaintenanceThe scheduled maintenance has been completed.30 minScheduled
Jul 20, 2026Some customers in AWS us-west-2 may experience degraded visibility performanceWe're seeing recovery on our end and errors and latencies on Visibility APIs have dropped. We will continue to monitor this but the incident is mitigated and resolved.44 minResolved
Jul 20, 2026Some customers in GCP us-east4 may experience elevated latenciesThis incident has been resolved.2h 10mResolved
Jul 20, 2026Some customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1) from 12:45 to 13:25 UTCSome customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1), starting from 12:45 UTC to 13:25 UTC. Metrics lag have since recovered back to nominal.0 minResolved
Jul 20, 2026Some customers in AWS eu-west-1 may experience elevated latenciesWe have continued to see normal activity in this region with latencies holding at pre-incident levels. This incident is now resolved.7h 2mResolved
Jul 17, 2026Customers in AWS eu-west-1 may experience elevated API latenciesA spike in workload caused resource contention in the underlying infrastructure, resulting in elevated latency for critical APIs. We scaled up the underlying resources to handle the increased load, and latencies have…1h 26mResolved
Jul 16, 2026Some customers may experience a loss in metrics (v0 and v1) starting 19:00 UTCA configuration error caused a partial loss of metrics (v0 and v1) for some customers between 2026-07-16 19:00 UTC and 2026-07-17 02:12 UTC. We have updated the config and mitigated impact across impacted regions. All…3h 47mResolved
Jul 15, 2026Customers in us-east-2 may experience some visibility related errorsAll MRN-enabled namespaces failed over by Temporal have been failed back. This incident has been fully mitigated and is now resolved.4h 19mResolved
Jul 14, 2026Elevated latencies in us-east-1Errors and latencies have recovered, incident has been resolved.1h 10mResolved
Jul 14, 2026Broken Temporal skipping test server linkA Java SDK release was incorrectly tagged, preventing the time-skipping test server from being published. After correcting the tag, rerunning the release workflow, and clearing the temporal.download cache, downloads…16 minResolved
Jul 9, 2026Some customers in AWS us-west-2 may experience unjustified throttling errorsThis incident has been resolved.17 minResolved
Jul 8, 2026Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latenciesA set of fixes have been implemented and no further latency or failures have been observed in AWS us-east-1 since 17:00 UTC.7h 21mResolved
Jul 8, 2026Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latenciesThis incident has been resolved.7h 33mResolved
Jul 7, 2026Some customers in AWS us-east-1 may experience elevated rate of transient API errorsThis incident has been resolved.10h 39mResolved
Jul 7, 2026Customers in GCP us-east4 may experience elevated API latenciesThe latencies were caused by issues with a downstream service which resolved after we scaled up. We've been monitoring for errors and latencies and have not seen any further issues. This issue is now considered resolved.151h 31mResolved
Jul 7, 2026Some customers in GCP europe-west3 may experience elevated API latenciesThis incident has been resolved.1h 34mResolved
Jul 5, 2026Some customers in AWS us-east-2 may have experienced elevated API latencies and errorsThis incident has been resolved.56 minResolved
Jul 5, 2026Some customers in GCP us-west1 may have experienced elevated API latenciesSome customers in GCP us-west1 may have experienced elevated API latencies between 17:50 and 17:57 UTC.0 minResolved
Jul 1, 2026Errors on GetSystemInfo and healthcheck endpoints for latest SDK versionsThe rollout is complete and resolves the compression issues. All listed affected versions should no longer experience any compression-related errors.22h 24mResolved
Jun 17, 2026GCP customers in europe-west3 are experiencing elevated errors for Visibility API callsThe region has recovered — visibility calls are succeeding without errors. The incident is resolved.46 minResolved
Jun 12, 2026Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.Incident Resolved.44h 56mResolved
Jun 11, 2026Audit logs temporarily delayed for a few hours — no data loss.This has been fixed, and the audit logs have been backfilled.46 minResolved
Jun 11, 2026Customers might observe Usage API returning missing or delayed dataWe have identified the root cause and confirmed that no customer impact occurred.58 minResolved
Jun 8, 2026GCP customers in us-east4 are experiencing elevated errors for Visibility API callsNamespaces have been failed back to their primary region. This incident has been resolved2h 52mResolved
Jun 6, 2026Some customers in AWS sa-east-1 may experience elevated API latenciesThis incident has been resolved.2h 11mResolved
Jun 3, 2026Some customers may be experiencing stuck workflows or activitiesThis incident has been resolved.315h 12mResolved
May 29, 2026Some customers in us-west-2 may experience elevated rate of API errors & higher latenciesRemediation has been completed at this time and we have confirmed the recovery of all affected namespaces.2h 18mResolved
May 28, 2026Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errorsThe service has remained stable since the initial behavior was observed 5/28 19:40 to 20:05 UTC. A permanent fix for the region is now in-progress.25h 51mResolved
May 27, 2026Some customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errorsSome customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors returned during the time period 15:00-15:30:00 UTC. This issue was investigated and identified as being related to a deployment in…0 minResolved
May 22, 2026Namespace creation and modification availablity degradedThis incident has been resolved. Analysis shows the error was from our domain management vendor.2 minResolved
May 22, 2026Customers using OpenMetric for external observability may see gaps in some metricsThis incident has been resolved.117h 45mResolved
May 15, 2026Temporal UI was unable to display human readable execution detailsA change to the Cloud UI caused a breaking change to the codec server endpoint. This impacted the UI for some customers for roughly 1.5 hours between May 15, 2026, 11:42:57 AM PDT and May 15, 2026 1:14:53 PM PDT. The…0 minResolved
May 13, 2026Some customers in GCP us-east4 experienced elevated API latenciesSome customers in GCP us-east4 experienced elevated API latencies for two minutes between 13:03:30 and 13:05:30 UTC. The issue is currently resolved with latencies back to baseline.-1 minResolved
May 12, 2026Some customers in GCP us-east4 experienced elevated API latenciesSome customers in GCP us-east4 experienced elevated API latencies for two minutes between 12:38 and 12:40 UTC. The issue is currently resolved with latencies back to baseline.0 minResolved
May 8, 2026Some customers in AWS us-east-1 may experience elevated API latenciesAWS has resolved the underlying infrastructure issues in us-east-1. We have marked the region as healthy and are failing our AWS us-east-1 primary multi-region replication customers back into this region.26h 5mResolved
May 5, 2026Some customers in us-west-2 may experience elevated rate of API errors and high latencyThis incident has been resolved.16h 2mResolved
May 4, 2026Some customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errorsThis incident has been resolved.1h 45mResolved
Apr 21, 2026Degraded Child Workflow ExecutionWe identified and resolved an issue that caused some Child Workflows to fail to start under certain conditions. Affected Workflows have been reprocessed and are now operating normally as of 23:26 UTC.21 minResolved
Apr 15, 2026Some customers in us-west-2 experiencing increased visibility API latenciesVisibility system and APIs have recovered.2h 17mResolved
Apr 10, 2026Billing API Data Freshness DelayBilling data freshness in the Billing API was delayed between 2026-04-09 08:00 UTC and 2026-04-10 14:00 UTC. During this period, recently generated billing data was not immediately reflected in API responses. This…0 minResolved
Apr 9, 2026Some customers briefly experienced elevated errors for Web UI and Cloud Ops APIBetween 23:52:49 and 00:13:52 UTC on Apr 8–9, some customers saw intermittent 500 errors in parts of the Temporal Cloud Control Plane, affecting access to certain web pages and APIs. We identified the issue as shared…0 minResolved
Apr 9, 2026Some customers connecting over PrivateServiceConnect in uscentral1 experienced elevated errorsFrom 2026-04-09 00:23:00 UTC to 2026-04-09 00:47:15 UTC, some customers using GCP private service connect in us-central1 may have had client connection issues or UNAVAILABLE responses17 minResolved
Mar 31, 2026Small number of customers in AWS us-west-2 may experience delayed execution of schedulesThis incident has been resolved.11h 27mResolved
Mar 30, 2026Small number of customers in GCP europe-west3 may experience delayed firing of timersThis incident has been resolved.2h 58mResolved
Mar 27, 2026Elevated latencies and errors in certain namespaces in AWS us-east-1 regionThis incident has been resolved.3h 31mResolved
Mar 19, 2026A small number of customers in AWS experienced API timeouts.This incident has been resolved.42 minResolved
Mar 18, 2026Some customers in GCP us-east4 experienced elevated API latencies.Some customers in GCP us-east4 experienced elevated API latencies from approximately 2026-03-18 16:00 to 2026-03-18 18:00 UTC.0 minResolved
Mar 17, 2026A small number of customers in AWS us-east-1 experienced elevated latencies.From approximately 2026-03-17 00:24:00 to 2026-03-17 00:41:00 UTC, a small number of customers in AWS us-east-1 experienced elevated latencies.0 minResolved
Mar 11, 2026Some customers using cloud ops API may experience higher latency and elevated rate of API errorsThis incident is resolved30 minResolved
Mar 9, 2026Customers using external observability may experience elevated rate of API errorsThis incident is resolved5h 12mResolved
Mar 6, 2026Some customers in us-west-2 may have experienced elevated API latencies & errorSome customers in us-west-2 may have experienced elevated API latencies & error from 7:15 - 7:40 UTC on March 6th.-734 minResolved
Mar 2, 2026Delay in modifications of Authorization settingsA fix has been deployed45 minResolved
Feb 27, 2026Error fetching Schedules countThe UI is working as expected now. We've deployed a fix, and the schedules count API is working as expected.18h 21mResolved
Feb 26, 2026Customers in us-east4 may experience elevated API latenciesCustomers in us-east4 may have experienced elevated API latencies between 13:34:00 and 13:49:00 UTC0 minResolved
Feb 20, 2026Cloud OPS Read-only APIs are experiencing errorsA fix has been implemented and calls to the Cloud OPS Read-only API call success rate has recovered18 minResolved
Feb 10, 2026Some customers in GCP us-central1 may experience elevated API latenciesThis incident has been resolved.3h 10mResolved
Feb 7, 2026Some customers in AWS sa-east-1 are experiencing elevated latenciesThis incident has been resolved.49 minResolved
Feb 2, 2026OpenMetrics missing metricsThis incident has been resolved.1h 25mResolved
Jan 31, 2026OpenMetrics missing metricsThis incident has been resolved.2h 54mResolved
Jan 26, 2026Small number of customers in us-west-2 may experience elevated API latenciesRetroactive update: Latencies in us-west-2 returned to normal levels after the fix was applied, and the incident was considered resolved at 23:30 UTC on Jan 26. No additional customer impact was observed.17h 10mResolved
Jan 16, 2026Search attribute queries are degraded for some customersThis incident has been resolved.2h 1mResolved
Jan 14, 2026Customers may experience unavailability of namespace admin services.This incident has been resolved.29 minResolved
Jan 13, 2026Customers may experience unavailability of namespace admin services.This incident has been resolved.1h 41mResolved
Dec 18, 2025High latencies for some customers in GCP us-east4 regionThis incident is resolved; the region has recovered. This occurred due to a significant accumulation of timer tasks in the system, which required processing to clear. The backlog has since been resolved, and normal…2h 0mResolved
Dec 18, 2025Some customers in us-west-2 may experience elevated rate of errorsSome customers in us-west-2 may have seen resource exhausted errors on poll RPCs and increased schedule-to-start latency, task backlogs for a short period 20:35 UTC Investigating 21:05 UTC Resolved A small number of…0 minResolved
Dec 16, 2025Drop in sync match rates for Activity/Workflow Processing for some customersThis incident has been resolved.33h 35mResolved
Dec 10, 2025OpenMetrics data updates are delayedThis incident has been resolved.35 minResolved
Nov 18, 2025Customers in us-west-2 may experience unavailability of serviceCustomers in us-west-2 may have experienced service unavailability for approximately 8 minutes between 06:10:15 UTC to 06:18:00 UTC. We’ve identified and resolved the issue caused by a spike in activity affecting one…0 minResolved
Nov 16, 2025Customers are not able to log in to cloud.temporal.io.This incident has been resolved.30 minResolved
Nov 4, 2025Task processing delay for certain customers in AWS ap-southeast-1 regionThis incident has been resolved.31h 29mResolved
Oct 23, 2025Increased latencies for schedules, batches and versioning APIs in us-east-1This incident has been resolved.1h 29mResolved
Oct 22, 2025Namespaces in aws us-west-2 experiencing increased latenciesLatencies appear to have recovered24 minResolved
Oct 21, 2025Intermittent failures attempting to add us-east-2 replicas to existing namespacesAt around 2025-10-20 UTC 23:00, some customer requests to add an aws us-east-2 replica to an existing namespace failed. We successfully retried these failed requests around 2025-10-21 UTC 05:00-1154 minResolved
Oct 20, 2025Service disruptions in AWS us-east-1Update: Our systems are showing full recovery across all previously impacted namespaces. Namespaces that failed over during the incident have not yet been failed back. We are working directly with a small number of…11h 18mResolved
Oct 7, 2025Some customers in AWS us-west-2 experienced elevated error rates for <1% of workflowsThis incident has been resolved0 minResolved
Oct 6, 2025Customers in GCP us-east4 are experiencing elevated latency for Visibility API callsThis incident has been resolved.25h 15mResolved

How to Read This Temporal Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Temporal acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Temporal outage in this window ran 13d 3h, against a mean recovery of 12h 58m. If you depend on Temporal in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.