Skip to main content
Orb

Elevated usage fetch latencies via API

Degraded Lasted 55m · started · Orb's page

Level
confirmed
Worst impact
Degraded
Down Index
17of 100

What to do

  • Check whether your product depends on Orb. 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 55m it lasted.

    Anything that failed between 2026-04-03 21:52 UTC and 2026-04-03 22:48 UTC may need a replay.
  • Subscribe to Orb's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=orb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Orb 2

  1. monitoring

    We identified elevated latencies for fetching usage (and potentially some associated actions that required invoicing via manual action). The vast majority of the impact was from April 3 21:22 to 21:26 UTC. Impact was fully mitigated for a remaining small (<1%) of errors by 21:39.

    provider

  2. resolved

    This is now 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-65f2a63810

Is Orb still down?

No, this incident was resolved 2026-04-03 22:48 UTC. For Orb's live state, see https://down.guide/orb.

How long did it last?

55m, from 2026-04-03 21:52 UTC to 2026-04-03 22:48 UTC, by the times Orb posted.

What caused it?

Orb hasn't published a root cause. If it does, it shows here.

Where does this come from?

Orb's official status page, https://status.withorb.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.