Skip to content
OutageDeck

Incident detail

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

Resolved incidentMajor1 affected service1 region: us-west-2

Timeline window

to

Get alerted the next time Temporal Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Temporal Cloud alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are currently investigating the issue.

  2. Investigating

    This is still in investigation

  3. Identified

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

  4. Identified

    We continue working to mitigate the issue.

  5. Monitoring

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

  6. Monitoring

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

  7. Monitoring

    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.

  8. Monitoring

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

  9. Resolved

    This incident has been resolved.

Keep exploring

More from Temporal Cloud

Neighboring incidents on Temporal Cloud's timeline and the rest of their record on OutageDeck.

← Older incident

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

Newer incident →

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

All Temporal Cloud incidentsTemporal Cloud live status