- Level
- confirmed
- Worst impact
- Degraded
- Components
- Reads, Writes, Analytics
- Down Index
- 26of 100
What to do
Check whether you use Orb Reads, Writes, Analytics. 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 52m it lasted.
Anything that failed between 2026-03-07 13:04 UTC and 2026-03-07 13:56 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
- monitoring
Following a deployment at 5:40 UTC, the Orb API started experience elevated timeouts for applying and cancelling subscription pending changes. We have rolled back and errors have subsided fully as of 12:55 UTC, and we are continuing to monitor.
provider
- resolved
We identified the root cause to be a new query that was introduced. API traffic to the affected endpoints has been healthy since the rollback at 12:55 UTC.
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-34d7e793ac
Is Orb still down?
No, this incident was resolved 2026-03-07 13:56 UTC. For Orb's live state, see https://down.guide/orb.
How long did it last?
52m, from 2026-03-07 13:04 UTC to 2026-03-07 13:56 UTC, by the times Orb posted.
What was affected?
Orb named Reads, Writes, Analytics.
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.