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

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 0m it lasted.

  Anything that failed between 2026-08-07 18:26 UTC and 2026-08-07 18:26 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 6

1. investigatingAug 5, 2026, 1:17 PM UTC

   Customers in AWS eu-west-1 might have experienced degraded API latencies starting 07:00 UTC.

   provider

2. identifiedAug 5, 2026, 1:24 PM UTC

   The issue has been identified and remediation work is ongoing. API latencies might remain elevated while work completes.

   provider

3. identifiedAug 5, 2026, 4:05 PM UTC

   The remediation work is still in progress. Next update will be posted once this completes.

   provider

4. identifiedAug 5, 2026, 5:29 PM UTC

   Remediation has improved overall latency. We continue to monitor while the remaining work completes.

   provider

5. monitoringAug 6, 2026, 2:52 AM UTC

   Remediation remains in effect, and latency and error rates continue to improve. We are actively monitoring the system to ensure continued stability.

   provider

6. resolvedAug 7, 2026, 6:26 PM UTC

   No further errors and latencies have been observed and systems remain stable. The issue was capacity related and caused elevated database latencies. The service was scaled up and closely monitored until all latencies resolved.

   provider

Corrections

None so far.

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