Skip to main content
Temporal Cloud

Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures

Degraded Monitoring a fix since · started · Temporal Cloud's page

Updates every minute from the provider's page.

Level
confirmed
Worst impact
Degraded
Components
us-west-2
Regions
us, us-west-2
Down Index
40of 100

Summary

Temporal Cloud says some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures. The provider identified the issue and applied a mitigation, and it is now monitoring the results.

Written by anthropic/claude-haiku-5.5 from Temporal Cloud's own updates.

What to do

  • Check whether you use Temporal Cloud us-west-2 in us, us-west-2. 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.
  • Temporal Cloud says a fix is out: check your own error rates before you undo any failover.

  • Watch Temporal Cloud's own updates; this page re-reads them every minute.

  • 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 3

  1. investigating

    Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures We are investigating

    provider

  2. identified

    We've identified the issue, and mitigation is in progress.

    provider

  3. monitoring

    We applied a mitigation and are monitoring the results.

    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-9912219cfd

Is Temporal Cloud down right now?

Temporal Cloud reports degraded (Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures), open since 2026-11-06 13:40 UTC; it says a fix is out and it is monitoring. Live state for every component: https://down.guide/temporal-cloud.

What was affected?

Temporal Cloud named us-west-2 in us, us-west-2.

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.