Temporal Outage History

Temporal is up right now

Temporal had 64 outages in the last 2 years totaling 595h 36m of downtime — averaging 2.6 incidents per month.

There were 64 Temporal outages since August 16, 2025 totaling 595h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.temporal.io

Notice June 12, 2026

Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.

Detected by Pingoru
Jun 12, 2026, 07:09 PM UTC
Resolved
Jun 14, 2026, 04:06 PM UTC
Duration
1d 20h
Affected: us-east-1
Timeline · 4 updates
  1. monitoring Jun 12, 2026, 07:09 PM UTC

    Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved. We failed namespaces with MRN out of the cell. We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.

  2. monitoring Jun 12, 2026, 08:44 PM UTC

    This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.

  3. monitoring Jun 12, 2026, 11:16 PM UTC

    This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.

  4. resolved Jun 14, 2026, 04:06 PM UTC

    Incident Resolved.

Read the full incident report →

Minor June 11, 2026

Audit logs temporarily delayed for a few hours — no data loss.

Detected by Pingoru
Jun 11, 2026, 07:58 PM UTC
Resolved
Jun 11, 2026, 08:45 PM UTC
Duration
46m
Affected: Audit Logging
Timeline · 2 updates
  1. identified Jun 11, 2026, 07:58 PM UTC

    We have identified that audit logs have been temporarily delayed since approximately 2026-06-11 18:00:00 UTC. We are implementing a fix, and we expect no data loss and a completed backfill within hours.

  2. resolved Jun 11, 2026, 08:45 PM UTC

    This has been fixed, and the audit logs have been backfilled.

Read the full incident report →

Minor June 11, 2026

Customers might observe Usage API returning missing or delayed data

Detected by Pingoru
Jun 11, 2026, 02:34 PM UTC
Resolved
Jun 11, 2026, 03:32 PM UTC
Duration
58m
Affected: Billing
Timeline · 2 updates
  1. investigating Jun 11, 2026, 02:34 PM UTC

    We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.

  2. resolved Jun 11, 2026, 03:32 PM UTC

    We have identified the root cause and confirmed that no customer impact occurred.

Read the full incident report →

Minor June 8, 2026

GCP customers in us-east4 are experiencing elevated errors for Visibility API calls

Detected by Pingoru
Jun 08, 2026, 10:06 PM UTC
Resolved
Jun 09, 2026, 12:59 AM UTC
Duration
2h 52m
Affected: us-east4
Timeline · 5 updates
  1. investigating Jun 08, 2026, 10:06 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 08, 2026, 10:38 PM UTC

    A fix has been implemented and we are monitoring

  3. monitoring Jun 08, 2026, 10:42 PM UTC

    Multi Region Namespaces were failed over at 10:23 PM UTC

  4. monitoring Jun 08, 2026, 11:18 PM UTC

    The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in.

  5. resolved Jun 09, 2026, 12:59 AM UTC

    Namespaces have been failed back to their primary region. This incident has been resolved

Read the full incident report →

Minor June 6, 2026

Some customers in AWS sa-east-1 may experience elevated API latencies

Detected by Pingoru
Jun 06, 2026, 02:15 AM UTC
Resolved
Jun 06, 2026, 04:26 AM UTC
Duration
2h 11m
Affected: sa-east-1
Timeline · 3 updates
  1. investigating Jun 06, 2026, 02:15 AM UTC

    Some customers in AWS sa-east-1 may experience elevated API latencies. We are currently investigating the issue.

  2. monitoring Jun 06, 2026, 02:29 AM UTC

    The issue appears to have been transient network latency that has resolved. We are monitoring the situation.

  3. resolved Jun 06, 2026, 04:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026

Some customers in us-west-2 may experience elevated rate of API errors & higher latencies

Detected by Pingoru
May 29, 2026, 01:31 PM UTC
Resolved
May 29, 2026, 03:49 PM UTC
Duration
2h 18m
Affected: us-west-2
Timeline · 6 updates
  1. identified May 29, 2026, 01:31 PM UTC

    Some customers in us-west-2 may experience elevated rate of API errors & higher latencies

  2. identified May 29, 2026, 01:43 PM UTC

    Failover was initiated for the affected HA namespaces while we keep investigating the root cause.

  3. identified May 29, 2026, 02:03 PM UTC

    We continue to investigate the root cause while implementing remediation measures. Error rates have recovered.

  4. identified May 29, 2026, 02:50 PM UTC

    Error rates remain stable, and we continue to implement remediation measures while monitoring service performance closely.

  5. monitoring May 29, 2026, 03:15 PM UTC

    Latencies and error rates are stable after remediation and we are continuing to monitoring it.

  6. resolved May 29, 2026, 03:49 PM UTC

    Remediation has been completed at this time and we have confirmed the recovery of all affected namespaces.

Read the full incident report →

Notice May 28, 2026

Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors

Detected by Pingoru
May 28, 2026, 08:22 PM UTC
Resolved
May 29, 2026, 10:14 PM UTC
Duration
1d 1h
Affected: us-east-1
Timeline · 7 updates
  1. identified May 28, 2026, 08:22 PM UTC

    Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors today from 19:40 to 20:05 UTC. We have currently mitigated the issue and are working on a permanent fix at this time.

  2. monitoring May 28, 2026, 09:00 PM UTC

    The gRPC UNIMPLEMENTED errors previously observed have been mitigated. We are continuing to monitor the situation and are working towards a permanent fix at this time.

  3. monitoring May 28, 2026, 10:14 PM UTC

    Service has remained stable and we are continuing to monitor the situation. We will continue to provide updates as they become available.

  4. monitoring May 28, 2026, 11:17 PM UTC

    We have confirmed the service is now stable and are now working to ensure a permanent fix is in place to prevent any recurrence.

  5. monitoring May 29, 2026, 02:11 AM UTC

    The service remains stable. We are continuing to monitor closely while work progresses on a permanent fix to prevent recurrence.

  6. monitoring May 29, 2026, 10:48 AM UTC

    The service continues to operate normally. We will provide additional updates as they become available.

  7. resolved May 29, 2026, 10:14 PM UTC

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

Read the full incident report →

Notice May 27, 2026

Some customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors

Detected by Pingoru
May 27, 2026, 03:00 PM UTC
Resolved
May 27, 2026, 03:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 27, 2026, 04:55 PM UTC

    Some customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors returned during the time period 15:30-16:30:00 UTC. This issue was investigated and identified as being related to a deployment in the affected region that has been rolled back - no further impact is expected.

Read the full incident report →

Minor May 22, 2026

Namespace creation and modification availablity degraded

Detected by Pingoru
May 22, 2026, 11:40 PM UTC
Resolved
May 22, 2026, 11:43 PM UTC
Duration
2m
Affected: Namespace Management
Timeline · 2 updates
  1. investigating May 22, 2026, 11:40 PM UTC

    Namespace creation, modification and deletion were unable to be completed from 23:10 to 23:35 UTC. There is no impact to workflow operations

  2. resolved May 22, 2026, 11:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 22, 2026

Customers using OpenMetric for external observability may see gaps in some metrics

Detected by Pingoru
May 22, 2026, 01:30 AM UTC
Resolved
May 26, 2026, 11:15 PM UTC
Duration
4d 21h
Affected: Metrics
Timeline · 2 updates
  1. monitoring May 26, 2026, 09:47 PM UTC

    Customers using OpenMetric for external observability may see gaps in metrics ending with _limit, as mentioned here (https://docs.temporal.io/cloud/metrics/openmetrics/metrics-reference#limit-metrics)

  2. resolved May 26, 2026, 11:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 15, 2026

Temporal UI was unable to display human readable execution details

Detected by Pingoru
May 15, 2026, 06:30 PM UTC
Resolved
May 15, 2026, 06:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 15, 2026, 09:00 PM UTC

    A change to the Cloud UI caused a breaking change to the codec server endpoint. This impacted the UI for roughly 1.5 hours between May 15, 2026, 11:42:57 AM PDT and May 15, 2026 1:14:53 PM PDT. The change was rolled back and the UI is back to normal operating conditions.

Read the full incident report →

Major May 4, 2026

Some customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errors

Detected by Pingoru
May 04, 2026, 10:50 PM UTC
Resolved
May 05, 2026, 12:36 AM UTC
Duration
1h 45m
Affected: us-east-1
Timeline · 3 updates
  1. investigating May 04, 2026, 10:50 PM UTC

    We are currently investigating a small number of gRPC UNIMPLEMENTED errors being returned in the AWS us-east-1 region.

  2. monitoring May 04, 2026, 11:23 PM UTC

    The issue has been identified as being related to a proxy node replacement rollout which has been halted. We are currently monitoring the region but do not anticipate any new errors at this point.

  3. resolved May 05, 2026, 12:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026

Degraded Child Workflow Execution

Detected by Pingoru
Apr 21, 2026, 11:15 PM UTC
Resolved
Apr 21, 2026, 11:37 PM UTC
Duration
21m
Affected: europe-west3
Timeline · 2 updates
  1. investigating Apr 21, 2026, 11:15 PM UTC

    We are investigating an issue where child workflows started with the TerminateIfRunning conflict policy may fail to start. The issue began approximately 2026-04-21 19:39 UTC.A fix is in progress and we will provide updates shortly.

  2. resolved Apr 21, 2026, 11:37 PM UTC

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

Read the full incident report →

Minor April 15, 2026

Some customers in us-west-2 experiencing increased visibility API latencies

Detected by Pingoru
Apr 15, 2026, 08:58 AM UTC
Resolved
Apr 15, 2026, 11:15 AM UTC
Duration
2h 17m
Affected: us-west-2
Timeline · 5 updates
  1. investigating Apr 15, 2026, 08:58 AM UTC

    Workspace operations are functioning normally. Some customers experiencing increased visibility api latency.

  2. investigating Apr 15, 2026, 09:12 AM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 15, 2026, 09:41 AM UTC

    We are continuing to investigate the increased visibility API latencies.

  4. monitoring Apr 15, 2026, 10:36 AM UTC

    Remediation has been applied and the visibility system is recovering. We are continuing to monitor.

  5. resolved Apr 15, 2026, 11:15 AM UTC

    Visibility system and APIs have recovered.

Read the full incident report →

Notice April 10, 2026

Billing API Data Freshness Delay

Detected by Pingoru
Apr 10, 2026, 02:00 PM UTC
Resolved
Apr 10, 2026, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 10, 2026, 02:39 PM UTC

    Billing 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 issue did not affect API availability. The delay has been resolved, and billing data is now updating within normal freshness expectations.

Read the full incident report →

Minor April 9, 2026

Some customers briefly experienced elevated errors for Web UI and Cloud Ops API

Detected by Pingoru
Apr 09, 2026, 12:41 AM UTC
Resolved
Apr 09, 2026, 12:41 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 09, 2026, 12:41 AM UTC

    Between 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 rate limiting that caused temporary impact to other requests. The issue is resolved, and we are making targeted improvements for better isolation and resilience.

Read the full incident report →

Minor March 31, 2026

Small number of customers in AWS us-west-2 may experience delayed execution of schedules

Detected by Pingoru
Mar 31, 2026, 08:00 PM UTC
Resolved
Apr 01, 2026, 07:27 AM UTC
Duration
11h 27m
Affected: us-west-2
Timeline · 4 updates
  1. identified Apr 01, 2026, 05:47 AM UTC

    Small number of customers in AWS us-west-2 may experience delayed execution of schedules

  2. identified Apr 01, 2026, 06:38 AM UTC

    We have identified a backlog of workflow tasks and are currently refreshing Workflows to unblock the stuck schedules.

  3. monitoring Apr 01, 2026, 07:11 AM UTC

    Impacted Schedules have been refreshed and backlogs have been cleared. Resources have been scaled out to mitigate.

  4. resolved Apr 01, 2026, 07:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 30, 2026

Small number of customers in GCP europe-west3 may experience delayed firing of timers

Detected by Pingoru
Mar 30, 2026, 10:10 PM UTC
Resolved
Mar 31, 2026, 01:09 AM UTC
Duration
2h 58m
Affected: europe-west3
Timeline · 3 updates
  1. identified Mar 31, 2026, 01:07 AM UTC

    Small number of customers in GCP europe-west3 may experience delayed firing of timers.

  2. monitoring Mar 31, 2026, 01:08 AM UTC

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

  3. resolved Mar 31, 2026, 01:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 27, 2026

Elevated latencies and errors in certain namespaces in AWS us-east-1 region

Detected by Pingoru
Mar 27, 2026, 06:37 PM UTC
Resolved
Mar 27, 2026, 10:08 PM UTC
Duration
3h 31m
Affected: us-east-1
Timeline · 3 updates
  1. investigating Mar 27, 2026, 06:50 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 27, 2026, 07:30 PM UTC

    A fix has been implemented and we are monitoring results.

  3. resolved Mar 27, 2026, 10:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2026

A small number of customers in AWS experienced API timeouts.

Detected by Pingoru
Mar 19, 2026, 12:47 AM UTC
Resolved
Mar 19, 2026, 01:30 AM UTC
Duration
42m
Affected: ap-northeast-1ap-northeast-2ap-south-1ap-south-2ap-southeast-1ap-southeast-2ca-central-1eu-central-1eu-west-1eu-west-2sa-east-1us-east-1us-east-2us-west-2
Timeline · 2 updates
  1. monitoring Mar 19, 2026, 12:47 AM UTC

    A small number of customers in AWS experienced API timeouts. We are monitoring the issue.

  2. resolved Mar 19, 2026, 01:30 AM UTC

    This incident has been resolved.

Read the full incident report →