Temporal Outage History

Temporal is up right now

There were 20 Temporal outages since February 7, 2026 totaling 50h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.temporal.io

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 →

Minor March 11, 2026

Some customers using cloud ops API may experience higher latency and elevated rate of API errors

Detected by Pingoru
Mar 11, 2026, 11:23 PM UTC
Resolved
Mar 11, 2026, 11:53 PM UTC
Duration
30m
Affected: Cloud Ops API
Timeline · 3 updates
  1. identified Mar 11, 2026, 11:23 PM UTC

    Some customers using cloud ops API may experience higher latency and elevated rate of API errors

  2. monitoring Mar 11, 2026, 11:27 PM UTC

    A fix has been deployed and we will continue to monitor

  3. resolved Mar 11, 2026, 11:53 PM UTC

    This incident is resolved

Read the full incident report →

Minor March 9, 2026

Customers using external observability may experience elevated rate of API errors

Detected by Pingoru
Mar 09, 2026, 12:11 PM UTC
Resolved
Mar 09, 2026, 05:23 PM UTC
Duration
5h 12m
Affected: Metrics
Timeline · 3 updates
  1. identified Mar 09, 2026, 12:11 PM UTC

    Customers using external observability may experience elevated rate of API errors

  2. monitoring Mar 09, 2026, 12:29 PM UTC

    Errors have subsided for last 20 minutes and we will continue to monitor

  3. resolved Mar 09, 2026, 05:23 PM UTC

    This incident is resolved

Read the full incident report →

Minor March 2, 2026

Delay in modifications of Authorization settings

Detected by Pingoru
Mar 02, 2026, 05:53 AM UTC
Resolved
Mar 02, 2026, 06:39 AM UTC
Duration
45m
Affected: Auth(n)/Auth(z)
Timeline · 2 updates
  1. identified Mar 02, 2026, 05:53 AM UTC

    Some users may experience delays in updates to their authorization settings. Authorization continues to work normally, however propagation of changes is being delayed.

  2. resolved Mar 02, 2026, 06:39 AM UTC

    A fix has been deployed

Read the full incident report →

Notice February 27, 2026

Error fetching Schedules count

Detected by Pingoru
Feb 27, 2026, 04:18 AM UTC
Resolved
Feb 27, 2026, 10:40 PM UTC
Duration
18h 21m
Timeline · 5 updates
  1. investigating Feb 27, 2026, 04:18 AM UTC

    Some customers may experience unauthorized errors in fetching the count of Schedules, which causes the "Create Schedule" button to be hidden. Visit https://cloud.temporal.io/namespaces/\.\/schedules/create if you need to create a Schedule via the UI

  2. investigating Feb 27, 2026, 04:19 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 27, 2026, 04:20 AM UTC

    Error fetching Schedules count Some customers may experience unauthorized errors in fetching the count of Schedules, which also causes the "Create Schedule" button to be hidden in Cloud UI. Visit https://cloud.temporal.io/namespaces/namespace.account/schedules/create if you need to create a Schedule via the UI

  4. identified Feb 27, 2026, 07:40 PM UTC

    We've deployed a fix that makes the 'Create Schedule' button visible again. Users will still see 'Unauthorized' errors when fetching the schedule count, and we're actively working on that as well.

  5. resolved Feb 27, 2026, 10:40 PM UTC

    The UI is working as expected now. We've deployed a fix, and the schedules count API is working as expected.

Read the full incident report →

Major February 20, 2026

Cloud OPS Read-only APIs are experiencing errors

Detected by Pingoru
Feb 20, 2026, 09:05 PM UTC
Resolved
Feb 20, 2026, 09:24 PM UTC
Duration
18m
Affected: Cloud Ops API
Timeline · 2 updates
  1. investigating Feb 20, 2026, 09:20 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 20, 2026, 09:29 PM UTC

    A fix has been implemented and calls to the Cloud OPS Read-only API call success rate has recovered

Read the full incident report →

Minor February 10, 2026

Some customers in GCP us-central1 may experience elevated API latencies

Detected by Pingoru
Feb 10, 2026, 09:51 PM UTC
Resolved
Feb 11, 2026, 01:01 AM UTC
Duration
3h 10m
Affected: us-central1
Timeline · 4 updates
  1. investigating Feb 10, 2026, 09:51 PM UTC

    Some customers in GCP us-central1 may experience elevated API latencies.

  2. identified Feb 10, 2026, 10:34 PM UTC

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

  3. monitoring Feb 11, 2026, 12:28 AM UTC

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

  4. resolved Feb 11, 2026, 01:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 7, 2026

Some customers in AWS sa-east-1 are experiencing elevated latencies

Detected by Pingoru
Feb 07, 2026, 03:05 PM UTC
Resolved
Feb 07, 2026, 03:54 PM UTC
Duration
49m
Affected: sa-east-1
Timeline · 3 updates
  1. investigating Feb 07, 2026, 03:05 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 07, 2026, 03:15 PM UTC

    Underlying network issues have resolved and latencies have returned to normal levels

  3. resolved Feb 07, 2026, 03:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Temporal downtime and outages?

Pingoru polls Temporal's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Temporal reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Temporal alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Temporal for free

5 free monitors · No credit card required