Skip to main content
Temporal Cloud

Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors

Degraded Lasted 1d 1h · 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 1h it lasted.

    Anything that failed between 2026-05-28 20:22 UTC and 2026-05-29 22:14 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 7

  1. identified

    Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors today from 19:40 to 20:05 UTC. We have identified a root cause and are currently working towards a permanent fix.

    provider

  2. monitoring

    The gRPC UNIMPLEMENTED errors previously observed have been mitigated. We are continuing to monitor the situation and are working towards a permanent fix at this time.

    provider

  3. monitoring

    Service has remained stable and we are continuing to monitor the situation. We will continue to provide updates as they become available.

    provider

  4. monitoring

    We have confirmed the service is now stable and are now working to ensure a permanent fix is in place to prevent any recurrence. We will continue to monitor for errors until the fix is deployed.

    provider

  5. monitoring

    The service remains stable. We are continuing to monitor closely while work progresses on a permanent fix to prevent recurrence.

    provider

  6. monitoring

    The service continues to operate normally. We will provide additional updates as they become available.

    provider

  7. resolved

    The service has remained stable since the initial behavior was observed 5/28 19:40 to 20:05 UTC. A permanent fix for the region is now in-progress.

    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-9fb8aef4f1

Is Temporal Cloud still down?

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

How long did it last?

1d 1h, from 2026-05-28 20:22 UTC to 2026-05-29 22:14 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.