Skip to main content
Orb

Elevated API latencies, now resolved

Degraded Lasted 0m · started · Orb's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 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 0m it lasted.

    Anything that failed between 2026-07-23 14:51 UTC and 2026-07-23 08:00 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 1

  1. resolved

    Customers may have experienced elevated API latencies from ~08:00–09:00Z and ~13:05–13:45Z, with some mild degradation in the timeframe in between. We've identified and mitigated the problematic underlying resource contention, and will continue to monitor. Note that this did not affect ingestion, and did not cause server-side timeouts for the vast majority of customers, but may have caused client-side timeouts.

    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-4aee5a1aae

Is Orb still down?

No, this incident was resolved 2026-07-23 08:00 UTC. For Orb's live state, see https://down.guide/orb.

How long did it last?

0m, from 2026-07-23 14:51 UTC to 2026-07-23 08:00 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.