- Level
- confirmed
- Worst impact
- Degraded
- Components
- Analytics
- Down Index
- 18of 100
What to do
Check whether you use Orb 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 17m it lasted.
Anything that failed between 2025-07-26 04:01 UTC and 2025-07-26 04:18 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
A recent code deploy caused a minor increase in analytics request errors. Our automated canary systems rolled this back as part of our deploy process without any operator intervention. We're continuing to monitor to ensure errors do not recur, and the offending logic is not deployed. This did not impact writes or data ingestion.
provider
- resolved
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
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-be03558645
Is Orb still down?
No, this incident was resolved 2025-07-26 04:18 UTC. For Orb's live state, see https://down.guide/orb.
How long did it last?
17m, from 2025-07-26 04:01 UTC to 2025-07-26 04:18 UTC, by the times Orb posted.
What was affected?
Orb named 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.