- Level
- confirmed
- Worst impact
- Degraded
- Components
- Microsoft 365
- Down Index
- 24of 100
What to do
Check whether you use Ashby Microsoft 365. 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 15h 16m it lasted.
Anything that failed between 2026-01-22 22:00 UTC and 2026-01-23 13:16 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
- identified
We have identified an issue with the upstream provider that is causing delays in syncing information.
provider
- monitoring
We are seeing improved performance and will continue to monitor.
provider
- resolved
This incident has been resolved.
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-ee9d9b02ff
Is Ashby still down?
No, this incident was resolved 2026-01-23 13:16 UTC. For Ashby's live state, see https://down.guide/ashby.
How long did it last?
15h 16m, from 2026-01-22 22:00 UTC to 2026-01-23 13:16 UTC, by the times Ashby posted.
What was affected?
Ashby named Microsoft 365.
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.