Temporal Outage History

Temporal is up right now

Temporal had 87 outages in the last 2 years totaling 57h 1m of downtime — averaging 3.6 incidents per month.

There were 87 Temporal outages since October 6, 2025 totaling 57h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.temporal.io

Critical October 5, 2026

Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI

Detected by Pingoru
Oct 05, 2026, 08:23 PM UTC
Resolved
Oct 05, 2026, 08:52 PM UTC
Duration
28m
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Minor October 1, 2026

UI Disruptions in GCP us-central1

Detected by Pingoru
Oct 01, 2026, 09:07 PM UTC
Resolved
Oct 01, 2026, 09:47 PM UTC
Duration
40m
Affected: Web UI
Timeline · 4 updates
  1. 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.

  2. investigating Oct 01, 2026, 09:07 PM UTC

    There are no current workflow disruptions, only UI components affected for impacted namespaces within the region.

  3. monitoring Oct 01, 2026, 09:21 PM UTC

    Identified cause and resolved regional UI issue, monitoring for any continued impact.

  4. 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.

Read the full incident report →

Minor September 27, 2026

Increased latency in region us-west-2

Detected by Pingoru
Sep 27, 2026, 01:01 AM UTC
Resolved
Sep 27, 2026, 01:53 AM UTC
Duration
52m
Affected: us-west-2
Timeline · 3 updates
  1. 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.

  2. 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.

  3. resolved Sep 27, 2026, 01:53 AM UTC

    The issue is resolved and service is operating normally.

Read the full incident report →

Minor September 18, 2026

Some customers may have incorrectly received a "credit expiry notification"

Detected by Pingoru
Sep 18, 2026, 03:54 PM UTC
Resolved
Sep 18, 2026, 10:23 PM UTC
Duration
6h 29m
Affected: Billing
Timeline · 4 updates
  1. investigating Sep 18, 2026, 03:54 PM UTC

    We are currently investigating this issue.

  2. identified Sep 18, 2026, 04:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. 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.

  4. resolved Sep 18, 2026, 10:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 11, 2026

Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)

Detected by Pingoru
Sep 11, 2026, 10:10 AM UTC
Resolved
Sep 11, 2026, 02:29 PM UTC
Duration
4h 18m
Affected: Metrics
Timeline · 3 updates
  1. 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

  2. monitoring Sep 11, 2026, 01:31 PM UTC

    OpenMetrics incomplete responses have recovered and remain stable. We continue to monitor the situation.

  3. resolved Sep 11, 2026, 02:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 10, 2026

Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress

Detected by Pingoru
Sep 10, 2026, 08:51 PM UTC
Resolved
Sep 11, 2026, 07:21 AM UTC
Duration
10h 29m
Affected: us-central1asia-southeast2
Timeline · 7 updates
  1. identified Sep 10, 2026, 09: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.

  2. 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.

  3. monitoring Sep 10, 2026, 10:29 PM UTC

    We are continuing to monitor for any further issues.

  4. 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.

  5. monitoring Sep 10, 2026, 11:29 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Sep 10, 2026, 11:30 PM UTC

    We are continuing to monitor for any further issues.

  7. 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.

Read the full incident report →

Minor September 3, 2026

Elevated Errors in us-west-2 Region

Detected by Pingoru
Sep 03, 2026, 09:12 PM UTC
Resolved
Sep 04, 2026, 05:28 AM UTC
Duration
8h 16m
Affected: us-west-2
Timeline · 4 updates
  1. investigating Sep 03, 2026, 11:10 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

  2. monitoring Sep 03, 2026, 11:25 PM UTC

    We are starting to see recovery as of 23:01 UTC.

  3. 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.

  4. 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.

Read the full incident report →

Minor September 2, 2026

Low Rate of Namespace Create/Update Failures Across All Regions

Detected by Pingoru
Sep 02, 2026, 03:26 PM UTC
Resolved
Sep 02, 2026, 03:49 PM UTC
Duration
22m
Affected: Namespace Management
Timeline · 2 updates
  1. 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.

  2. resolved Sep 02, 2026, 03:49 PM UTC

    The rollback of the affected service has completed. Namespace configuration changes will resume as expected.

Read the full incident report →

Minor September 1, 2026

Elevated error rates in GCP us-central1

Detected by Pingoru
Sep 01, 2026, 03:47 PM UTC
Resolved
Sep 01, 2026, 09:43 PM UTC
Duration
5h 55m
Affected: us-central1
Timeline · 3 updates
  1. 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.

  2. 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

  3. 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.

Read the full incident report →

Notice August 21, 2026

Self-Signup Onboarding Access Restriction

Detected by Pingoru
Aug 21, 2026, 01:30 PM UTC
Resolved
Aug 21, 2026, 01:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 21, 2026, 01:43 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.

Read the full incident report →

Minor August 20, 2026

Customers in (GCP) us-west1 may experience elevated API latencies

Detected by Pingoru
Aug 20, 2026, 03:20 PM UTC
Resolved
Aug 20, 2026, 07:00 PM UTC
Duration
3h 39m
Affected: us-west1
Timeline · 4 updates
  1. investigating Aug 20, 2026, 03:20 PM UTC

    Customers in (GCP) us-west1 may experience elevated API latencies.

  2. identified Aug 20, 2026, 04:05 PM UTC

    Downstream cloud provider (GCP) is reporting issues. We are working with them to resolve this issue.

  3. 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.

  4. 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.

Read the full incident report →

Notice August 13, 2026

Cloud Ops API — Elevated Error Rates and Latencies

Detected by Pingoru
Aug 13, 2026, 12:00 PM UTC
Resolved
Aug 13, 2026, 12:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 13, 2026, 12:37 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.

Read the full incident report →

Minor August 13, 2026

Customers in AWS us-west-2 may experience elevated API latencies

Detected by Pingoru
Aug 13, 2026, 11:47 AM UTC
Resolved
Aug 13, 2026, 12:27 PM UTC
Duration
39m
Affected: us-west-2
Timeline · 4 updates
  1. investigating Aug 13, 2026, 11:47 AM UTC

    Customers in AWS us-west-2 may experience elevated API latencies

  2. monitoring Aug 13, 2026, 12:09 PM UTC

    The incident has been mitigated, and we are monitoring

  3. monitoring Aug 13, 2026, 12:09 PM UTC

    We are continuing to monitor for any further issues.

  4. 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.

Read the full incident report →

Minor August 7, 2026

Some customers in AWS eu-west-1 may experience elevated latencies

Detected by Pingoru
Aug 07, 2026, 06:26 PM UTC
Resolved
Aug 07, 2026, 06:26 PM UTC
Duration
—
Affected: eu-west-1
Timeline · 6 updates
  1. investigating Aug 05, 2026, 01:17 PM UTC

    Customers in AWS eu-west-1 might have experienced degraded API latencies starting 07:00 UTC.

  2. 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.

  3. identified Aug 05, 2026, 04:05 PM UTC

    The remediation work is still in progress. Next update will be posted once this completes.

  4. identified Aug 05, 2026, 05:29 PM UTC

    Remediation has improved overall latency. We continue to monitor while the remaining work completes.

  5. 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.

  6. 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.

Read the full incident report →

Critical July 31, 2026

Usage API and UI are experiencing an outage

Detected by Pingoru
Jul 31, 2026, 10:46 PM UTC
Resolved
Aug 01, 2026, 01:00 AM UTC
Duration
2h 13m
Affected: Billing
Timeline · 5 updates
  1. investigating Aug 01, 2026, 12:21 AM UTC

    We are currently investigating this issue.

  2. investigating Aug 01, 2026, 12:24 AM UTC

    We are continuing to investigate this issue.

  3. identified Aug 01, 2026, 12:26 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Aug 01, 2026, 12:30 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 01, 2026, 01:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 23, 2026

Some customers in AWS us-west-2 may experience degraded visibility performance

Detected by Pingoru
Jul 23, 2026, 07:11 PM UTC
Resolved
Jul 23, 2026, 07:59 PM UTC
Duration
47m
Affected: us-west-2
Timeline · 3 updates
  1. investigating Jul 23, 2026, 07:11 PM UTC

    We are currently investigating this issue.

  2. 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.

  3. resolved Jul 23, 2026, 07:59 PM UTC

    This incident has been resolved. Visibility performance has been restored.

Read the full incident report →

Minor July 22, 2026

Some customers in GCP us-east4 may experience elevated latencies

Detected by Pingoru
Jul 22, 2026, 12:35 PM UTC
Resolved
Jul 22, 2026, 01:04 PM UTC
Duration
28m
Affected: us-east4
Timeline · 3 updates
  1. investigating Jul 22, 2026, 12:35 PM UTC

    We are currently investigating elevated API latencies in GCP us-east4

  2. 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.

  3. resolved Jul 22, 2026, 01:04 PM UTC

    API latencies have recovered and remained stable since the observed periods of elevated latency.

Read the full incident report →

Notice July 20, 2026

Some customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1) from 12:45 to 13:25 UTC

Detected by Pingoru
Jul 20, 2026, 01:55 PM UTC
Resolved
Jul 20, 2026, 01:55 PM UTC
Duration
—
Affected: Metrics
Timeline · 1 update
  1. resolved Jul 20, 2026, 01:55 PM UTC

    Some 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.

Read the full incident report →

Notice July 17, 2026

Customers in AWS eu-west-1 may experience elevated API latencies

Detected by Pingoru
Jul 17, 2026, 02:30 PM UTC
Resolved
Jul 17, 2026, 03:56 PM UTC
Duration
1h 26m
Affected: eu-west-1
Timeline · 5 updates
  1. investigating Jul 17, 2026, 02:30 PM UTC

    Customers in AWS eu-west-1 may experience elevated API latencies.

  2. investigating Jul 17, 2026, 02:38 PM UTC

    We are failing over MRN namespaces

  3. investigating Jul 17, 2026, 02:49 PM UTC

    The failover has been completed.

  4. monitoring Jul 17, 2026, 03:22 PM UTC

    Latencies are back to normal levels, we’re monitoring.

  5. resolved Jul 17, 2026, 03:56 PM UTC

    A 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 returned to normal. We will continue to monitor the system, but the mitigation is complete and the incident has been resolved.

Read the full incident report →

Minor July 16, 2026

Some customers may experience a loss in metrics (v0 and v1) starting 19:00 UTC

Detected by Pingoru
Jul 16, 2026, 10:26 PM UTC
Resolved
Jul 17, 2026, 02:14 AM UTC
Duration
3h 48m
Affected: us-east4
Timeline · 6 updates
  1. investigating Jul 16, 2026, 10:26 PM UTC

    We are currently investigating, additional details to come shortly.

  2. investigating Jul 16, 2026, 10:42 PM UTC

    Impact is across some regions but limited to metrics.

  3. identified Jul 16, 2026, 11:21 PM UTC

    We're in the process of mitigating impact and metrics are slowly being restored across some namespaces.

  4. identified Jul 17, 2026, 12:00 AM UTC

    Mitigation is still in progress and metrics are slowly being restored across namespaces.

  5. monitoring Jul 17, 2026, 12:24 AM UTC

    Mitigation is complete and global metrics are restored. We are currently monitoring.

  6. resolved Jul 17, 2026, 02:14 AM UTC

    A 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 global metrics are now restored and the incident is resolved.

Read the full incident report →

Major July 15, 2026

Customers in us-east-2 may experience some visibility related errors

Detected by Pingoru
Jul 15, 2026, 04:55 PM UTC
Resolved
Jul 15, 2026, 09:15 PM UTC
Duration
4h 19m
Affected: us-east-2
Timeline · 7 updates
  1. investigating Jul 15, 2026, 04:55 PM UTC

    Customers with namespaces in us-east-2 may experience errors with visibility queries. We are currently investigating.

  2. identified Jul 15, 2026, 05:52 PM UTC

    We are working on a fix, if your namespace are MRN enabled please fail over to your passive regions for faster recovery.

  3. identified Jul 15, 2026, 06:33 PM UTC

    All MRN-enabled namespaces have been failed over as of 17:53 UTC. Mitigation continues to progress.

  4. identified Jul 15, 2026, 07:12 PM UTC

    Mitigation is still in progress. We are scaling up service to help with mitigation efforts.

  5. monitoring Jul 15, 2026, 07:58 PM UTC

    Mitigation is in effect, we are seeing some recovery. Please submit a support ticket if you are seeing service degradation.

  6. monitoring Jul 15, 2026, 08:29 PM UTC

    We are seeing full recovery on our end, we are continuing to monitor.

  7. resolved Jul 15, 2026, 09:15 PM UTC

    All MRN-enabled namespaces failed over by Temporal have been failed back. This incident has been fully mitigated and is now resolved.

Read the full incident report →

Minor July 14, 2026

Elevated latencies in us-east-1

Detected by Pingoru
Jul 14, 2026, 06:47 PM UTC
Resolved
Jul 14, 2026, 07:57 PM UTC
Duration
1h 10m
Affected: us-east-1
Timeline · 2 updates
  1. investigating Jul 14, 2026, 06:47 PM UTC

    Some customers in AWS us-east-1 may experience elevated latencies and errors on their namespaces

  2. resolved Jul 14, 2026, 07:57 PM UTC

    Errors and latencies have recovered, incident has been resolved.

Read the full incident report →

Notice July 14, 2026

Broken Temporal skipping test server link

Detected by Pingoru
Jul 14, 2026, 12:03 AM UTC
Resolved
Jul 14, 2026, 12:20 AM UTC
Duration
16m
Timeline · 3 updates
  1. investigating Jul 14, 2026, 12:03 AM UTC

    We are investigating a broken link for the latest version of the Temporal skipping test server

  2. monitoring Jul 14, 2026, 12:05 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 14, 2026, 12:20 AM UTC

    A 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 were restored.

Read the full incident report →