Skip to main content
Temporal Cloud

Customers in AWS eu-west-1 may experience elevated API latencies

Degraded Lasted 1h 26m · started · Temporal Cloud's page

Level
confirmed
Worst impact
Degraded
Components
eu-west-1
Regions
eu, eu-west-1
Down Index
26of 100

What to do

  • Check whether you use Temporal Cloud eu-west-1 in eu, eu-west-1. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 26m it lasted.

    Anything that failed between 2026-07-17 14:30 UTC and 2026-07-17 15:56 UTC may need a replay.
  • Subscribe to Temporal Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=temporal-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Temporal Cloud 5

  1. investigating

    Customers in AWS eu-west-1 may experience elevated API latencies.

    provider

  2. investigating

    We are failing over MRN namespaces

    provider

  3. investigating

    The failover has been completed.

    provider

  4. monitoring

    Latencies are back to normal levels, we’re monitoring.

    provider

  5. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-8a0d3e0a6d

Is Temporal Cloud still down?

No, this incident was resolved 2026-07-17 15:56 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.

How long did it last?

1h 26m, from 2026-07-17 14:30 UTC to 2026-07-17 15:56 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named eu-west-1 in eu, eu-west-1.

What caused it?

Temporal Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Temporal Cloud's official status page, https://status.temporal.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.