Temporal Outage History
Temporal degraded · 1 active incident View live status →Pingoru has recorded 97 incidents for Temporal: 93 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 | 188 of 744 (25%) |
| June 2026 | 7 | 333 of 720 (46%) |
| July 2026 | 21 | 202 of 744 (27%) |
| August 2026 | 5 | 82 of 744 (11%) |
| September 2026 | 7 | 37 of 720 (5%) |
| October 2026 | 9 | 226 of 571 (40%) |
Incidents, newest first
Minor July 16, 2026 Some customers may experience a loss in metrics (v0 and v1) starting 19:00 UTC 3h 48m us-east4
Started Jul 16, 2026, 10:26 PM UTC· resolved Jul 17, 2026, 02:14 AM UTC
- investigating Jul 16, 2026, 10:26 PM UTC
We are currently investigating, additional details to come shortly.
- investigating Jul 16, 2026, 10:42 PM UTC
Impact is across some regions but limited to metrics.
- 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.
- identified Jul 17, 2026, 12:00 AM UTC
Mitigation is still in progress and metrics are slowly being restored across namespaces.
- monitoring Jul 17, 2026, 12:24 AM UTC
Mitigation is complete and global metrics are restored. We are currently monitoring.
- 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.
Major July 15, 2026 Customers in us-east-2 may experience some visibility related errors 4h 19m us-east-2
Started Jul 15, 2026, 04:55 PM UTC· resolved Jul 15, 2026, 09:15 PM UTC
- 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.
- 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.
- 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.
- identified Jul 15, 2026, 07:12 PM UTC
Mitigation is still in progress. We are scaling up service to help with mitigation efforts.
- 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.
- monitoring Jul 15, 2026, 08:29 PM UTC
We are seeing full recovery on our end, we are continuing to monitor.
- 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.
Minor July 14, 2026 Elevated latencies in us-east-1 1h 10m us-east-1
Started Jul 14, 2026, 06:47 PM UTC· resolved Jul 14, 2026, 07:57 PM UTC
- investigating Jul 14, 2026, 06:47 PM UTC
Some customers in AWS us-east-1 may experience elevated latencies and errors on their namespaces
- resolved Jul 14, 2026, 07:57 PM UTC
Errors and latencies have recovered, incident has been resolved.
Notice July 14, 2026 Broken Temporal skipping test server link 16m
Started Jul 14, 2026, 12:03 AM UTC· resolved Jul 14, 2026, 12:20 AM UTC
- investigating Jul 14, 2026, 12:03 AM UTC
We are investigating a broken link for the latest version of the Temporal skipping test server
- monitoring Jul 14, 2026, 12:05 AM UTC
A fix has been implemented and we are monitoring the results.
- 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.
Notice July 9, 2026 Some customers in AWS us-west-2 may experience unjustified throttling errors 17m us-west-2
Started Jul 09, 2026, 04:08 PM UTC· resolved Jul 09, 2026, 04:25 PM UTC
- investigating Jul 09, 2026, 06:50 PM UTC
Some customers in AWS us-east-2 may experience unjustified throttling errors.
- resolved Jul 09, 2026, 06:50 PM UTC
This incident has been resolved.
Minor July 8, 2026 Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies 7h 21m us-east-1
Started Jul 08, 2026, 02:26 PM UTC· resolved Jul 08, 2026, 09:47 PM UTC
- 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.
- monitoring Jul 08, 2026, 03:36 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Jul 08, 2026, 04:19 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 08, 2026, 04:19 PM UTC
A fix has been implemented and we are monitoring the results.
- 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.
- 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.
- 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.
Minor July 8, 2026 Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies 7h 33m us-east-1
Started Jul 08, 2026, 02:40 AM UTC· resolved Jul 08, 2026, 10:14 AM UTC
- investigating Jul 08, 2026, 03:26 AM UTC
Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.
- monitoring Jul 08, 2026, 03:27 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 08, 2026, 10:14 AM UTC
This incident has been resolved.
Minor July 7, 2026 Some customers in AWS us-east-1 may experience elevated rate of transient API errors 10h 39m us-east-1
Started Jul 07, 2026, 11:25 PM UTC· resolved Jul 08, 2026, 10:04 AM UTC
- investigating Jul 08, 2026, 12:03 AM UTC
Some customers in AWS us-east-1 may experience elevated rate of transient API errors.
- monitoring Jul 08, 2026, 12:59 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 08, 2026, 10:04 AM UTC
This incident has been resolved.
Minor July 7, 2026 Customers in GCP us-east4 may experience elevated API latencies 6d 11h us-east4
Started Jul 07, 2026, 01:00 PM UTC· resolved Jul 14, 2026, 12:42 AM UTC
- investigating Jul 07, 2026, 05:48 PM UTC
Customers in GCP us-east4 may experience elevated API latencies.
- 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.
- 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.
- 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.
- monitoring Jul 07, 2026, 11:53 PM UTC
We have paused further investigation overnight pending validation under daytime traffic.
- monitoring Jul 08, 2026, 12:05 AM UTC
We are continuing to monitor for any further issues.
- monitoring Jul 09, 2026, 06:56 PM UTC
We are continuing to monitor for any further issues.
- 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.
Minor July 7, 2026 Some customers in GCP europe-west3 may experience elevated API latencies 1h 34m europe-west3
Started Jul 07, 2026, 05:54 AM UTC· resolved Jul 07, 2026, 07:29 AM UTC
- identified Jul 07, 2026, 06:17 AM UTC
Some customers in GCP europe-west3 may experience elevated API latencies.
- monitoring Jul 07, 2026, 06:18 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 07, 2026, 07:29 AM UTC
This incident has been resolved.
Notice July 5, 2026 Some customers in AWS us-east-2 may have experienced elevated API latencies and errors 56m us-east-2
Started Jul 05, 2026, 06:41 PM UTC· resolved Jul 05, 2026, 07:38 PM UTC
- monitoring Jul 05, 2026, 06:41 PM UTC
Some customers in AWS us-east-2 may have experienced elevated API latencies and errors between 17:57 and 18:16 UTC
- resolved Jul 05, 2026, 07:38 PM UTC
This incident has been resolved.
Notice July 5, 2026 Some customers in GCP us-west1 may have experienced elevated API latencies 7m us-west1
Started Jul 05, 2026, 05:50 PM UTC· resolved Jul 05, 2026, 05:57 PM UTC
- resolved Jul 05, 2026, 06:31 PM UTC
Some customers in GCP us-west1 may have experienced elevated API latencies between 17:50 and 17:57 UTC.
Notice July 1, 2026 Errors on GetSystemInfo and healthcheck endpoints for latest SDK versions 22h 24m
Started Jul 01, 2026, 06:02 PM UTC· resolved Jul 02, 2026, 04:26 PM UTC
- 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)
- 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.
- monitoring Jul 02, 2026, 01:55 PM UTC
The fix has been rolled out across all regions, and we are actively monitoring.
- resolved Jul 02, 2026, 04:26 PM UTC
The fix has been rolled out across all regions, and the issue is now resolved.
Minor June 17, 2026 GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls 46m
Started Jun 17, 2026, 09:18 PM UTC· resolved Jun 17, 2026, 10:04 PM UTC
- investigating Jun 17, 2026, 09:18 PM UTC
We are currently investigating this issue.
- investigating Jun 17, 2026, 09:34 PM UTC
A fix has been implemented. The visibility is coming back and we are monitoring.
- resolved Jun 17, 2026, 10:04 PM UTC
The region has recovered — visibility calls are succeeding without errors. The incident is resolved.
Notice June 12, 2026 Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses. 1d 20h us-east-1
Started Jun 12, 2026, 07:09 PM UTC· resolved Jun 14, 2026, 04:06 PM UTC
- 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.
- 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.
- 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.
- resolved Jun 14, 2026, 04:06 PM UTC
Incident Resolved.
Minor June 11, 2026 Audit logs temporarily delayed for a few hours — no data loss. 46m Audit Logging
Started Jun 11, 2026, 07:58 PM UTC· resolved Jun 11, 2026, 08:45 PM UTC
- 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.
- resolved Jun 11, 2026, 08:45 PM UTC
This has been fixed, and the audit logs have been backfilled.
Minor June 11, 2026 Customers might observe Usage API returning missing or delayed data 58m Billing
Started Jun 11, 2026, 02:34 PM UTC· resolved Jun 11, 2026, 03:32 PM UTC
- 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.
- resolved Jun 11, 2026, 03:32 PM UTC
We have identified the root cause and confirmed that no customer impact occurred.
Minor June 8, 2026 GCP customers in us-east4 are experiencing elevated errors for Visibility API calls 2h 52m us-east4
Started Jun 08, 2026, 10:06 PM UTC· resolved Jun 09, 2026, 12:59 AM UTC
- investigating Jun 08, 2026, 10:06 PM UTC
We are currently investigating this issue.
- monitoring Jun 08, 2026, 10:38 PM UTC
A fix has been implemented and we are monitoring
- monitoring Jun 08, 2026, 10:42 PM UTC
Multi Region Namespaces were failed over at 10:23 PM UTC
- monitoring Jun 08, 2026, 11:18 PM UTC
The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in.
- resolved Jun 09, 2026, 12:59 AM UTC
Namespaces have been failed back to their primary region. This incident has been resolved
Minor June 6, 2026 Some customers in AWS sa-east-1 may experience elevated API latencies 2h 11m sa-east-1
Started Jun 06, 2026, 02:15 AM UTC· resolved Jun 06, 2026, 04:26 AM UTC
- 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.
- 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.
- resolved Jun 06, 2026, 04:26 AM UTC
This incident has been resolved.
Notice June 3, 2026 Some customers may be experiencing stuck workflows or activities 13d 20h
Started Jun 03, 2026, 12:45 AM UTC· resolved Jun 16, 2026, 09:08 PM UTC
- investigating Jun 03, 2026, 05:55 PM UTC
We are investigating a few reports where a workflow or activity is becoming stuck and not making progress when it should. Please report any such issues you see to support.
- investigating Jun 03, 2026, 06:30 PM UTC
We are continuing to investigate this issue.
- investigating Jun 03, 2026, 07:51 PM UTC
We are investigating a recent update that could have caused intermittent missed task dispatches, resulting in some tasks being stuck. Impact identified as of now is limited to a handful of workflows that were caught in a rare edge case. We will continue to share more updates as investigation progresses.
- investigating Jun 03, 2026, 08:41 PM UTC
We're rolling back the recent update as a possible mitigation to avoid any further occurrences of this issue. We are however still in the process of investigating root cause and will post updates as we have them.
- identified Jun 03, 2026, 09:35 PM UTC
A bug in the recent update in History pagination caused a rare edge case where an extra task could be added before the response was returned. This incorrectly advanced the read level, causing some tasks to be skipped. We’ve identified the issue, and are currently rolling back the update to stop this from happening again. We will be refreshing all executions in cells where the update was deployed and will monitor these closely. This will progress any stuck workflows, but will not impact any of the closed ones.
- identified Jun 03, 2026, 11:36 PM UTC
Rollback is still in progress and we are continuing to monitor the situation.
- identified Jun 04, 2026, 01:40 AM UTC
The rollback is making progress across impacted cells, and we are continuing to monitor the situation.
- identified Jun 04, 2026, 04:27 AM UTC
Rollbacks are still in progress; refresh of open workflows is underway and will unblock impacted workflows.
- identified Jun 04, 2026, 06:14 AM UTC
Refreshes are still in progress and we are monitoring the situation.
- identified Jun 04, 2026, 06:45 AM UTC
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
- monitoring Jun 04, 2026, 07:08 AM UTC
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
- monitoring Jun 04, 2026, 05:40 PM UTC
We are continuing to monitor the ongoing refresh process for all open workflows. We are also considering options for refreshing closed workflows. We will continue to share more updates as this progresses.
- monitoring Jun 04, 2026, 10:35 PM UTC
As refresh of closed workflows progresses, some users may see unblocked stuck parent workflows from closed child workflows; this is happening because the missed task for closed child workflows is refreshed and delivered to parent. It could also happen on other stuck workflows that are waiting for task updates which were missed due to this incident.
- monitoring Jun 05, 2026, 10:02 PM UTC
Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete.
- monitoring Jun 08, 2026, 07:02 PM UTC
Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved.
- monitoring Jun 11, 2026, 08:25 PM UTC
Refresh operations across both open and closed workflows are complete in most regions; we continue to make steady progress across the remaining few namespaces in the us-east-1, us-west-2, us-east4, us-west1, us-central1, asia-south1, europe-west3. No additional impact has been observed since mitigation was implemented, and we continue to closely monitor the environment. The next update will be provided once the refresh process has completed.
- monitoring Jun 16, 2026, 03:56 PM UTC
The last few namespaces are still refreshing. We are starting to patch the code, and are monitoring the situation.
- monitoring Jun 16, 2026, 09:00 PM UTC
Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
- monitoring Jun 16, 2026, 09:07 PM UTC
Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
- resolved Jun 16, 2026, 09:08 PM UTC
This incident has been resolved.
Minor May 29, 2026 Some customers in us-west-2 may experience elevated rate of API errors & higher latencies 2h 18m us-west-2
Started May 29, 2026, 01:31 PM UTC· resolved May 29, 2026, 03:49 PM UTC
- identified May 29, 2026, 01:31 PM UTC
Some customers in us-west-2 may experience elevated rate of API errors & higher latencies
- identified May 29, 2026, 01:43 PM UTC
Failover was initiated for the affected HA namespaces while we keep investigating the root cause.
- identified May 29, 2026, 02:03 PM UTC
We continue to investigate the root cause while implementing remediation measures. Error rates have recovered.
- identified May 29, 2026, 02:50 PM UTC
Error rates remain stable, and we continue to implement remediation measures while monitoring service performance closely.
- monitoring May 29, 2026, 03:15 PM UTC
Latencies and error rates are stable after remediation and we are continuing to monitoring it.
- 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.
Notice May 28, 2026 Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors 1d 1h us-east-1
Started May 28, 2026, 08:22 PM UTC· resolved May 29, 2026, 10:14 PM UTC
- 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.
- 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.
- 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.
- 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.
- 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.
- monitoring May 29, 2026, 10:48 AM UTC
The service continues to operate normally. We will provide additional updates as they become available.
- 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.
Notice May 27, 2026 Some customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors –
Started May 27, 2026, 03:00 PM UTC· resolved May 27, 2026, 03:00 PM UTC
- 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.
Minor May 22, 2026 Namespace creation and modification availablity degraded 2m Namespace Management
Started May 22, 2026, 11:40 PM UTC· resolved May 22, 2026, 11:43 PM UTC
- 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
- resolved May 22, 2026, 11:43 PM UTC
This incident has been resolved.
Notice May 22, 2026 Customers using OpenMetric for external observability may see gaps in some metrics 4d 21h Metrics
Started May 22, 2026, 01:30 AM UTC· resolved May 26, 2026, 11:15 PM UTC
- 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)
- resolved May 26, 2026, 11:15 PM UTC
This incident has been resolved.