- 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 2025-03-31 20:01 UTC and 2025-03-31 19:17 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
- resolved
From approximately 12:17pm PT to 12:22pm PT, customers may have seen an elevated rate of API response times and errors. The cause of this issue has been resolved. The root cause of the issue was due to elevated latency on our event data store.
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-f869b06569
Is Orb still down?
No, this incident was resolved 2025-03-31 19:17 UTC. For Orb's live state, see https://down.guide/orb.
How long did it last?
0m, from 2025-03-31 20:01 UTC to 2025-03-31 19:17 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.