- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 100
What to do
Check whether your product depends on Orb. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 6h 26m it lasted.
Anything that failed between 2025-07-28 17:32 UTC and 2025-07-28 23:59 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
- identified
We've identified some revenue reporting delays in our pipeline; billing and data ingestion are not affected. Values from the API are also not affected. We expect to catch up within 24 hours, and will continue providing updates here.
provider
- resolved
As of 22:00 UTC, our revenue reporting service has caught up and is now processing data as expected.
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-9ac87a1bb2
Is Orb still down?
No, this incident was resolved 2025-07-28 23:59 UTC. For Orb's live state, see https://down.guide/providers/orb.
How long did it last?
6h 26m, from 2025-07-28 17:32 UTC to 2025-07-28 23:59 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.