Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Temporal

Some customers in us-west-2 may experience elevated rate of API errors and high latency

Resolved Major
May 05, 2026 - Started 2 days ago - Lasted about 16 hours
Official incident page

Incident Report

Summary AI Generated

Temporal customers in the us-west-2 region experienced elevated API error rates and high latency for 16.1 hours due to issues with the history service. Multi-region Namespace traffic was proactively failed over to secondary regions as a precautionary measure, where services continued operating normally. The incident was resolved after implementing a fix to the history service, with Multi-region Namespaces being failed back to primary regions once stability was confirmed.

We are currently investigating the issue.
Components affected
Temporal us-west-2

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED 1 day ago - at 05/05/2026 09:46PM

This incident has been resolved.

MONITORING 1 day ago - at 05/05/2026 08:09PM

Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.

MONITORING 1 day ago - at 05/05/2026 04:47PM

We are continuing to monitor the affected cell and have kept our status page in a monitoring state while we validate stability.

As a precaution, Multi-region Namespace traffic has been failed over to secondary regions, where it continues to be served normally.

While we complete stabilization work, Multi-region Namespaces will continue running from secondary regions.

Our current priority is to ensure the affected cell is stable and operating normally. Once confirmed, and the incident is resolved, we will restore Multi-region Namespace traffic to primary regions.

For Multi-region Namespaces failed over by Temporal, we will manage fail back. For manually failed over namespaces, customers can initiate fail back once the incident is resolved.

MONITORING 2 days ago - at 05/05/2026 09:24AM

API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.

MONITORING 2 days ago - at 05/05/2026 07:50AM

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

IDENTIFIED 2 days ago - at 05/05/2026 07:39AM

We continue working to mitigate the issue.

IDENTIFIED 2 days ago - at 05/05/2026 07:12AM

We are working to mitigate the issue. Error rates are recovering.

INVESTIGATING 2 days ago - at 05/05/2026 06:22AM

This is still in investigation

INVESTIGATING 2 days ago - at 05/05/2026 05:43AM

We are currently investigating the issue.

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook