Skip to main content
Temporal Cloud

Customers might observe Usage API returning missing or delayed data

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

Level
confirmed
Worst impact
Degraded
Components
Billing
Down Index
18of 100

What to do

  • Check whether you use Temporal Cloud Billing. 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 59m it lasted.

    Anything that failed between 2026-06-11 14:34 UTC and 2026-06-11 15:32 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. investigating

    We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.

    provider

  2. resolved

    We have identified the root cause and confirmed that no customer impact occurred.

    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-607188dab0

Is Temporal Cloud still down?

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

How long did it last?

59m, from 2026-06-11 14:34 UTC to 2026-06-11 15:32 UTC, by the times Temporal Cloud posted.

What was affected?

Temporal Cloud named Billing.

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.