Temporal Outage History

Temporal is up right now

Temporal had 84 outages in the last 2 years totaling 280h 34m of downtime — averaging 3.5 incidents per month.

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

Source: https://status.temporal.io

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 →

Minor July 20, 2026

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

Detected by Pingoru
Jul 20, 2026, 01:47 PM UTC
Resolved
Jul 20, 2026, 08:50 PM UTC
Duration
7h 2m
Affected: eu-west-1
Timeline · 5 updates
  1. investigating Jul 20, 2026, 02:17 PM UTC

    Some customers in AWS eu-west-1 may experience elevated latencies starting 13:47 UTC time.

  2. investigating Jul 20, 2026, 02:18 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 20, 2026, 07:11 PM UTC

    As of 17:53 UTC our engineering team has identified the issue and is actively working to restore normal service. We will provide another update as more information becomes available.

  4. monitoring Jul 20, 2026, 07:50 PM UTC

    Our engineering has implemented a fix and we are seeing normal service return to this region. We are continuing to monitor.

  5. resolved Jul 20, 2026, 08:50 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 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 →

Minor July 8, 2026

Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies

Detected by Pingoru
Jul 08, 2026, 02:26 PM UTC
Resolved
Jul 08, 2026, 09:47 PM UTC
Duration
7h 21m
Affected: us-east-1
Timeline · 7 updates
  1. investigating Jul 08, 2026, 03:25 PM UTC

    Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.

  2. monitoring Jul 08, 2026, 03:36 PM UTC

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

  3. identified Jul 08, 2026, 04:19 PM UTC

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

  4. monitoring Jul 08, 2026, 04:19 PM UTC

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

  5. investigating Jul 08, 2026, 04:46 PM UTC

    We are currently investigating the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are working to mitigate any recurring impact.

  6. monitoring Jul 08, 2026, 07:07 PM UTC

    The service has remained stable since 15:00 UTC. We continue to investigate the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are monitoring for any further occurrences.

  7. resolved Jul 08, 2026, 09:47 PM UTC

    A set of fixes have been implemented and no further latency or failures have been observed in AWS us-east-1 since 17:00 UTC.

Read the full incident report →

Minor July 8, 2026

Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies

Detected by Pingoru
Jul 08, 2026, 02:40 AM UTC
Resolved
Jul 08, 2026, 10:14 AM UTC
Duration
7h 33m
Affected: us-east-1
Timeline · 3 updates
  1. investigating Jul 08, 2026, 03:26 AM UTC

    Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.

  2. monitoring Jul 08, 2026, 03:27 AM UTC

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

  3. resolved Jul 08, 2026, 10:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026

Some customers in AWS us-east-1 may experience elevated rate of transient API errors

Detected by Pingoru
Jul 07, 2026, 11:25 PM UTC
Resolved
Jul 08, 2026, 10:04 AM UTC
Duration
10h 39m
Affected: us-east-1
Timeline · 3 updates
  1. investigating Jul 08, 2026, 12:03 AM UTC

    Some customers in AWS us-east-1 may experience elevated rate of transient API errors.

  2. monitoring Jul 08, 2026, 12:59 AM UTC

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

  3. resolved Jul 08, 2026, 10:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026

Customers in GCP us-east4 may experience elevated API latencies

Detected by Pingoru
Jul 07, 2026, 01:00 PM UTC
Resolved
Jul 14, 2026, 12:42 AM UTC
Duration
6d 11h
Affected: us-east4
Timeline · 8 updates
  1. investigating Jul 07, 2026, 05:48 PM UTC

    Customers in GCP us-east4 may experience elevated API latencies.

  2. investigating Jul 07, 2026, 06:21 PM UTC

    We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available.

  3. identified Jul 07, 2026, 07:14 PM UTC

    We are currently working to remediate the elevated API latencies that were observed in GCP us-east4.

  4. identified Jul 07, 2026, 10:20 PM UTC

    We are continuing to work on the investigation and remediation of the elevated API latencies in GCP us-east4. We will provide further updates within one hour.

  5. monitoring Jul 07, 2026, 11:53 PM UTC

    We have paused further investigation overnight pending validation under daytime traffic.

  6. monitoring Jul 08, 2026, 12:05 AM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Jul 09, 2026, 06:56 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Jul 14, 2026, 12:42 AM UTC

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

Read the full incident report →

Minor July 7, 2026

Some customers in GCP europe-west3 may experience elevated API latencies

Detected by Pingoru
Jul 07, 2026, 05:54 AM UTC
Resolved
Jul 07, 2026, 07:29 AM UTC
Duration
1h 34m
Affected: europe-west3
Timeline · 3 updates
  1. identified Jul 07, 2026, 06:17 AM UTC

    Some customers in GCP europe-west3 may experience elevated API latencies.

  2. monitoring Jul 07, 2026, 06:18 AM UTC

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

  3. resolved Jul 07, 2026, 07:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 1, 2026

Errors on GetSystemInfo and healthcheck endpoints for latest SDK versions

Detected by Pingoru
Jul 01, 2026, 06:02 PM UTC
Resolved
Jul 02, 2026, 04:26 PM UTC
Duration
22h 24m
Timeline · 4 updates
  1. identified Jul 01, 2026, 06:02 PM UTC

    Customers on the latest SDK versions may see decompression errors when calling the GetSystemInfo and gRPC health check endpoints. A fix for this is rolling out. Affected versions - Java 1.36.0 Go 1.45.0 TypeScript 1.19.0 Rust 0.5.0 Python 1.29.0 Workaround - Disable gzip compression in the SDK client (set gRPC compression to none)

  2. identified Jul 01, 2026, 10:12 PM UTC

    Fix is being rolled out across all regions, current impact is limited to us-west-2 and us-east-1 regions. All systems stable and we're actively monitoring this. Next update will be posted once rollouts completed.

  3. monitoring Jul 02, 2026, 01:55 PM UTC

    The fix has been rolled out across all regions, and we are actively monitoring.

  4. resolved Jul 02, 2026, 04:26 PM UTC

    The fix has been rolled out across all regions, and the issue is now resolved.

Read the full incident report →

Minor June 17, 2026

GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls

Detected by Pingoru
Jun 17, 2026, 09:18 PM UTC
Resolved
Jun 17, 2026, 10:04 PM UTC
Duration
46m
Timeline · 3 updates
  1. investigating Jun 17, 2026, 09:18 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 17, 2026, 09:34 PM UTC

    A fix has been implemented. The visibility is coming back and we are monitoring.

  3. resolved Jun 17, 2026, 10:04 PM UTC

    The region has recovered — visibility calls are succeeding without errors. The incident is resolved.

Read the full incident report →

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 →