Temporal Outage History
Temporal is up right nowPingoru has recorded 98 incidents for Temporal: 94 in the last 12 months and 22 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 10 of 720 (1%) |
| May 2026 | 11 | 46 of 744 (6%) |
| June 2026 | 7 | 8 of 720 (1%) |
| July 2026 | 21 | 175 of 744 (24%) |
| August 2026 | 5 | 59 of 744 (8%) |
| September 2026 | 7 | 32 of 720 (5%) |
| October 2026 | 10 | 4 of 744 (1%) |
| November 2026 | 0 | 0 of 1 (0%) |
Incidents, newest first
Minor October 31, 2026 Intermittent request failures for some namespaces in GCP us-east4 44m us-east4, us-west1
Started Oct 31, 2026, 01:31 PM UTC· resolved Oct 31, 2026, 02:16 PM UTC
- investigating Oct 31, 2026, 01:31 PM UTC
We are investigating intermittent request failures affecting a subset of namespaces in GCP. Affected users may see elevated latency and error rates on API calls, including worker polling (workflow, activity, and Nexus tasks), which can result in reduced task throughput.
- monitoring Oct 31, 2026, 01:48 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Oct 31, 2026, 01:54 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 31, 2026, 02:16 PM UTC
This incident has been resolved.
Notice October 19, 2026 Elevated connection resets for some GCP namespaces – us-east4, us-central1
Started Oct 19, 2026, 10:13 PM UTC· resolved Oct 19, 2026, 10:13 PM UTC
- resolved Oct 19, 2026, 10:13 PM UTC
Between October 6 and October 15, 2026, some clients connected to GCP-hosted namespaces may have seen intermittent TCP connection resets. SDK retries limited the impact and there is no ongoing impact.
Notice October 14, 2026 Elevated latency and errors in GCP us-west1 16m us-west1
Started Oct 14, 2026, 01:20 PM UTC· resolved Oct 14, 2026, 01:36 PM UTC
- monitoring Oct 14, 2026, 01:20 PM UTC
Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once monitoring confirms the region is stable.
- resolved Oct 14, 2026, 01:36 PM UTC
This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.
Minor October 9, 2026 Elevated latency and errors in AWS us-east-1 2h 17m us-east-1
Started Oct 09, 2026, 10:33 PM UTC· resolved Oct 10, 2026, 12:51 AM UTC
- investigating Oct 09, 2026, 10:33 PM UTC
We are investigating elevated latency and increased ResourceExhausted errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.
- investigating Oct 09, 2026, 10:38 PM UTC
We are continuing to investigate this issue.
- investigating Oct 09, 2026, 10:50 PM UTC
We have identified the cause of elevated latency affecting a subset of namespaces in AWS us-east-1. Namespaces with Multi-Region Replication enabled are being failed over to their replica region to restore service. We will provide another update within 30 minutes.
- monitoring Oct 09, 2026, 11:11 PM UTC
Latency and error rates in AWS us-east-1 have returned to normal levels and affected namespaces have recovered. We are continuing to monitor the region. We will provide another update once failback is complete.
- resolved Oct 10, 2026, 12:51 AM UTC
This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.
Notice October 9, 2026 Elevated error rates for cross-region traffic between US AWS regions 13m
Started Oct 09, 2026, 06:41 PM UTC· resolved Oct 09, 2026, 06:54 PM UTC
- resolved Oct 09, 2026, 10:25 PM UTC
Between 18:41 and 18:54 UTC on October 9, 2026, cross-region traffic to and from AWS us-east-1, us-east-2, and us-west-2 may have seen increased error rates. The issue has been resolved.
Notice October 8, 2026 Elevated GCP storage latency in us-central1 – precautionary namespace failover 4h 24m
Started Oct 08, 2026, 09:53 PM UTC· resolved Oct 09, 2026, 02:17 AM UTC
- investigating Oct 08, 2026, 09:53 PM UTC
We are monitoring elevated Cloud Storage latency from GCP in us-central1. As a precaution, multi-region namespaces in this region have been failed over to their replica regions. No impact to workflow execution has been observed. We will fail back once GCP confirms recovery.
- monitoring Oct 09, 2026, 01:04 AM UTC
Cloud Storage latency in GCP us-central1 has returned to normal levels. We are continuing to monitor the region and will begin failing multi-region namespaces back to us-central1 shortly.
- resolved Oct 09, 2026, 02:17 AM UTC
This incident is now resolved.
Critical October 5, 2026 Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI 28m
Started Oct 05, 2026, 08:23 PM UTC· resolved Oct 05, 2026, 08:52 PM UTC
- investigating Oct 05, 2026, 08:23 PM UTC
We are investigating increased errors and timeouts affecting the Temporal Cloud control plane, Cloud Ops API, and Temporal UI. Next update in 30 minutes.
- monitoring Oct 05, 2026, 08:39 PM UTC
A fix has been implemented and we are seeing recovery for the Temporal Cloud control plane, Cloud Ops API, and Temporal UI. We are continuing to monitor.
- resolved Oct 05, 2026, 08:52 PM UTC
This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally.
Minor October 1, 2026 UI Disruptions in GCP us-central1 41m Web UI
Started Oct 01, 2026, 09:06 PM UTC· resolved Oct 01, 2026, 09:47 PM UTC
- investigating Oct 01, 2026, 09:06 PM UTC
We are currently investigating an issue where some users in us-central1 GCP are experiencing UI service disruptions.
- investigating Oct 01, 2026, 09:07 PM UTC
There are no current workflow disruptions, only UI components affected for impacted namespaces within the region.
- monitoring Oct 01, 2026, 09:21 PM UTC
Identified cause and resolved regional UI issue, monitoring for any continued impact.
- resolved Oct 01, 2026, 09:47 PM UTC
We have continued to see normal activity in this region, with no reports of UI disruptions. This incident is now resolved.
Notice October 1, 2026 Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors 30m
Started Oct 01, 2026, 01:26 PM UTC· resolved Oct 01, 2026, 01:56 PM UTC
- resolved Oct 01, 2026, 02:00 PM UTC
Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors between 13:26 and 13:56 UTC
Minor September 27, 2026 Increased latency in region us-west-2 52m us-west-2
Started Sep 27, 2026, 01:01 AM UTC· resolved Sep 27, 2026, 01:53 AM UTC
- investigating Sep 27, 2026, 01:01 AM UTC
We are investigating increased latency and errors for namespaces in AWS us-west-2. We will share another update within 30 minutes.
- monitoring Sep 27, 2026, 01:22 AM UTC
Between 00:32 and 01:03 UTC, some namespaces in AWS us-west-2 saw increased API latency and errors. This has now recovered and we are monitoring.
- resolved Sep 27, 2026, 01:53 AM UTC
The issue is resolved and service is operating normally.
Minor September 18, 2026 Some customers may have incorrectly received a "credit expiry notification" 6h 29m Billing
Started Sep 18, 2026, 03:54 PM UTC· resolved Sep 18, 2026, 10:23 PM UTC
- investigating Sep 18, 2026, 03:54 PM UTC
We are currently investigating this issue.
- identified Sep 18, 2026, 04:00 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 18, 2026, 05:21 PM UTC
A fix has been implemented and we are currently working on sending out correction emails to affected customers.
- resolved Sep 18, 2026, 10:23 PM UTC
This incident has been resolved.
Notice September 11, 2026 Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics) 4h 18m Metrics
Started Sep 11, 2026, 10:10 AM UTC· resolved Sep 11, 2026, 02:29 PM UTC
- investigating Sep 11, 2026, 11:24 AM UTC
We are currently investigating a degradation in OpenMetrics endpoint causing incomplete responses for customers in APSE region
- monitoring Sep 11, 2026, 01:31 PM UTC
OpenMetrics incomplete responses have recovered and remain stable. We continue to monitor the situation.
- resolved Sep 11, 2026, 02:29 PM UTC
This incident has been resolved.
Major September 10, 2026 Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress 10h 29m us-central1, asia-southeast2
Started Sep 10, 2026, 08:51 PM UTC· resolved Sep 11, 2026, 07:21 AM UTC
- identified Sep 10, 2026, 08:51 PM UTC
Some customers with namespaces in the us-central1 and asia-southeast2 regions may experience errors and blocked progress on their workflows. We are currently rolling out a fix.
- monitoring Sep 10, 2026, 10:27 PM UTC
The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.
- monitoring Sep 10, 2026, 10:29 PM UTC
We are continuing to monitor for any further issues.
- monitoring Sep 10, 2026, 10:59 PM UTC
While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.
- monitoring Sep 10, 2026, 11:29 PM UTC
We are continuing to monitor for any further issues.
- monitoring Sep 10, 2026, 11:30 PM UTC
We are continuing to monitor for any further issues.
- resolved Sep 11, 2026, 07:21 AM UTC
The environment has been validated and all residual issues have been cleared. This incident is now resolved.
Minor September 3, 2026 Elevated Errors in us-west-2 Region 8h 16m us-west-2
Started Sep 03, 2026, 09:12 PM UTC· resolved Sep 04, 2026, 05:28 AM UTC
- investigating Sep 03, 2026, 09:12 PM UTC
We are investigating connectivity errors affecting some customers with namespaces in the us-west-2 region relating to an AWS outage in this region. Our team is actively assessing impact and working on mitigation. Affected MRN namespaces have been failed over. We will provide updates as more information becomes available. https://health.aws.amazon.com/health/status
- monitoring Sep 03, 2026, 11:25 PM UTC
We are starting to see recovery as of 23:01 UTC.
- monitoring Sep 04, 2026, 02:13 AM UTC
As of 9/4 00:07 UTC, AWS has confirmed the incident impacting us-west-2 is resolved. After a further period of monitoring, we have confirmed service is stable and have begun failing back the affected MRN namespaces.
- resolved Sep 04, 2026, 05:28 AM 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.
Minor September 2, 2026 Low Rate of Namespace Create/Update Failures Across All Regions 22m Namespace Management
Started Sep 02, 2026, 03:26 PM UTC· resolved Sep 02, 2026, 03:49 PM UTC
- identified Sep 02, 2026, 03:26 PM UTC
We have identified an issue where some customers may receive failures when creating or updating namespaces. We are currently rolling back the affected service. Temporal Cloud will ensure failures are manually retried.
- resolved Sep 02, 2026, 03:49 PM UTC
The rollback of the affected service has completed. Namespace configuration changes will resume as expected.
Minor September 1, 2026 Elevated error rates in GCP us-central1 5h 55m us-central1
Started Sep 01, 2026, 03:47 PM UTC· resolved Sep 01, 2026, 09:43 PM UTC
- investigating Sep 01, 2026, 03:47 PM UTC
We are currently investigating elevated error rates in GCP us-central1, and have proactively failed over MRN namespaces in this region as a precaution.
- identified Sep 01, 2026, 04:07 PM UTC
We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
- resolved Sep 01, 2026, 09:43 PM 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.
Notice August 20, 2026 Self-Signup Onboarding Access Restriction 15h 40m
Started Aug 20, 2026, 09:21 PM UTC· resolved Aug 21, 2026, 01:01 PM UTC
- resolved Aug 21, 2026, 01:30 PM 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.
Minor August 20, 2026 Customers in (GCP) us-west1 may experience elevated API latencies 3h 39m us-west1
Started Aug 20, 2026, 03:20 PM UTC· resolved Aug 20, 2026, 07:00 PM UTC
- investigating Aug 20, 2026, 03:20 PM UTC
Customers in (GCP) us-west1 may experience elevated API latencies.
- identified Aug 20, 2026, 04:05 PM UTC
Downstream cloud provider (GCP) is reporting issues. We are working with them to resolve this issue.
- monitoring Aug 20, 2026, 06:10 PM UTC
A fix has been implemented and we are seeing recovery. We will be continuing to monitor the results.
- resolved Aug 20, 2026, 07:00 PM UTC
We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved.
Minor August 13, 2026 Customers in AWS us-west-2 may experience elevated API latencies 39m us-west-2
Started Aug 13, 2026, 11:47 AM UTC· resolved Aug 13, 2026, 12:27 PM UTC
- investigating Aug 13, 2026, 11:47 AM UTC
Customers in AWS us-west-2 may experience elevated API latencies
- monitoring Aug 13, 2026, 12:09 PM UTC
The incident has been mitigated, and we are monitoring
- monitoring Aug 13, 2026, 12:09 PM UTC
We are continuing to monitor for any further issues.
- resolved Aug 13, 2026, 12:27 PM UTC
We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved.
Notice August 13, 2026 Cloud Ops API — Elevated Error Rates and Latencies 5m
Started Aug 13, 2026, 11:41 AM UTC· resolved Aug 13, 2026, 11:46 AM UTC
- resolved Aug 13, 2026, 12:00 PM 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.
Minor August 5, 2026 Some customers in AWS eu-west-1 may experience elevated latencies 2d 5h eu-west-1
Started Aug 05, 2026, 01:17 PM UTC· resolved Aug 07, 2026, 06:26 PM UTC
- investigating Aug 05, 2026, 01:17 PM UTC
Customers in AWS eu-west-1 might have experienced degraded API latencies starting 07:00 UTC.
- identified Aug 05, 2026, 01:24 PM UTC
The issue has been identified and remediation work is ongoing. API latencies might remain elevated while work completes.
- identified Aug 05, 2026, 04:05 PM UTC
The remediation work is still in progress. Next update will be posted once this completes.
- identified Aug 05, 2026, 05:29 PM UTC
Remediation has improved overall latency. We continue to monitor while the remaining work completes.
- monitoring Aug 06, 2026, 02:52 AM UTC
Remediation remains in effect, and latency and error rates continue to improve. We are actively monitoring the system to ensure continued stability.
- resolved Aug 07, 2026, 06:26 PM UTC
No further errors and latencies have been observed and systems remain stable. The issue was with capacity related and caused elevated database latencies. The service was scaled up and closely monitored until all latencies resolved.
Critical July 31, 2026 Usage API and UI are experiencing an outage 1h 13m Billing
Started Jul 31, 2026, 11:46 PM UTC· resolved Aug 01, 2026, 01:00 AM UTC
- investigating Jul 31, 2026, 11:46 PM UTC
We are currently investigating this issue.
- investigating Aug 01, 2026, 12:24 AM UTC
We are continuing to investigate this issue.
- identified Aug 01, 2026, 12:26 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 01, 2026, 12:30 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 01, 2026, 01:00 AM UTC
This incident has been resolved.
Minor July 23, 2026 Some customers in AWS us-west-2 may experience degraded visibility performance 47m us-west-2
Started Jul 23, 2026, 07:11 PM UTC· resolved Jul 23, 2026, 07:59 PM UTC
- investigating Jul 23, 2026, 07:11 PM UTC
We are currently investigating this issue.
- monitoring Jul 23, 2026, 07:32 PM UTC
The issue has been identified and mitigations have been put in place. We are continuing to monitor.
- resolved Jul 23, 2026, 07:59 PM UTC
This incident has been resolved. Visibility performance has been restored.
Minor July 22, 2026 Some customers in GCP us-east4 may experience elevated latencies 28m us-east4
Started Jul 22, 2026, 12:35 PM UTC· resolved Jul 22, 2026, 01:04 PM UTC
- investigating Jul 22, 2026, 12:35 PM UTC
We are currently investigating elevated API latencies in GCP us-east4
- investigating Jul 22, 2026, 12:48 PM UTC
We are investigating short periods of elevated API latency that occurred between 11:58–11:59 UTC and 12:17–12:19 UTC. We will provide an update as soon as it becomes available.
- resolved Jul 22, 2026, 01:04 PM UTC
API latencies have recovered and remained stable since the observed periods of elevated latency.
Minor July 20, 2026 Some customers in AWS us-west-2 may experience degraded visibility performance 44m us-west-2
Started Jul 20, 2026, 06:29 PM UTC· resolved Jul 20, 2026, 07:14 PM UTC
- investigating Jul 20, 2026, 06:29 PM UTC
We are currently investigating this issue.
- monitoring Jul 20, 2026, 06:45 PM UTC
We have identified the issue and implemented mitigation efforts. We are currently monitoring.
- resolved Jul 20, 2026, 07:14 PM UTC
This incident has been resolved.