- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 39m it lasted.
Anything that failed between 2026-05-08 00:52 UTC and 2026-05-08 01:31 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 3
- investigating
We’re currently investigating elevated API error rates impacting multiple endpoints. We have identified issues with our cloud provider that appear to be contributing to the incident, and our team is actively working to mitigate the impact and restore full service reliability. We’ll continue to share updates as more information becomes available.
provider
- monitoring
We are seeing recovery across impacted services and are continuing to monitor closely.
provider
- resolved
Services have now fully recovered and are operating normally.
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-bdb51bb324
Is Orb still down?
No, this incident was resolved 2026-05-08 01:31 UTC. For Orb's live state, see https://down.guide/orb.
How long did it last?
39m, from 2026-05-08 00:52 UTC to 2026-05-08 01:31 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.