Skip to main content
Temporal Cloud

Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.

Degraded Lasted 1d 20h · started · Temporal Cloud's page

Level
confirmed
Worst impact
Degraded
Components
us-east-1
Regions
us, us-east-1
Down Index
31of 100

What to do

  • Check whether you use Temporal Cloud us-east-1 in us, us-east-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 1d 20h it lasted.

    Anything that failed between 2026-06-12 19:09 UTC and 2026-06-14 16:06 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 4

  1. monitoring

    Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved. We failed namespaces with MRN out of the cell. We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.

    provider

  2. monitoring

    This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.

    provider

  3. monitoring

    This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.

    provider

  4. resolved

    Incident 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-3f995e83ee

Is Temporal Cloud still down?

No, this incident was resolved 2026-06-14 16:06 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.

How long did it last?

1d 20h, from 2026-06-12 19:09 UTC to 2026-06-14 16:06 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named us-east-1 in us, us-east-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.