Skip to main content
Temporal Cloud

A small number of customers in AWS experienced API timeouts.

Degraded Lasted 43m · started · Temporal Cloud's page

Level
confirmed
Worst impact
Degraded
Components
ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-2, ap-southeast-1, ap-southeast-2, ca-central-1, eu-central-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2
Regions
ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-2, ap-southeast-1, ap-southeast-2, ca-central-1, eu, eu-central-1, eu-west-1, eu-west-2, sa-east-1, us, us-east-1, us-east-2, us-west-2

What to do

  • Check whether you use Temporal Cloud ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-2 and 10 more in ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-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.
  • Confirm your retries, queues and scheduled jobs caught up after the 43m it lasted.

    Anything that failed between 2026-03-19 00:47 UTC and 2026-03-19 01:30 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 2

  1. monitoring

    A small number of customers in AWS experienced API timeouts. We are monitoring the issue.

    provider

  2. resolved

    This 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-a4ad12ec45

Is Temporal Cloud still down?

No, this incident was resolved 2026-03-19 01:30 UTC. For Temporal Cloud's live state, see https://down.guide/temporal-cloud.

How long did it last?

43m, from 2026-03-19 00:47 UTC to 2026-03-19 01:30 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-2 and 10 more in ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-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.