- Level
- confirmed
- Worst impact
- Degraded
- Components
- Analytics
- Down Index
- 20of 100
What to do
Check whether you use Ashby 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 2h 15m it lasted.
Anything that failed between 2026-02-12 16:30 UTC and 2026-02-12 18:46 UTC may need a replay.Subscribe to Ashby's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=ashby works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Ashby 3
- investigating
We have identified an issue with the upstream provider that is causing delays in Reporting data
provider
- investigating
We are seeing a recovery with the upstream provider, and Reporting data is catching up.
provider
- resolved
Resolved: Reporting data is now up to date. Thank you for your patience.
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-ec35be2e7a
Is Ashby still down?
No, this incident was resolved 2026-02-12 18:46 UTC. For Ashby's live state, see https://down.guide/ashby.
How long did it last?
2h 15m, from 2026-02-12 16:30 UTC to 2026-02-12 18:46 UTC, by the times Ashby posted.
What was affected?
Ashby named Analytics.
What caused it?
Ashby hasn't published a root cause. If it does, it shows here.
Where does this come from?
Ashby's official status page, https://status.ashbyhq.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.