Live / Ashby / Incident
Ashby: Delays in updated data appearing in Ashby
Ashby · ashbyhq.comMinor incidentResolved2026-10-05 22:42 UTC
Public — what happened
Summary
Ashby reported a minor incident beginning at 18:46 UTC on October 5, 2026, in which recent changes such as candidate stage moves, feedback, new applications and record edits were slow to show up in search, lists, reports and the API, and some pages loaded slowly or timed out. The company said the changes were still being stored and asked users to hold off on repeating updates that hadn't appeared yet. By 21:21 UTC Ashby said information was current again and page speeds had recovered, and it marked the incident resolved at 22:42 after a period of monitoring. No cause was given in its updates.
Affected
Recruiting, Analytics
Timeline
- Started — 2026-10-05 18:46 UTC
- Investigating — 2026-10-05 18:46 UTC (2 updates)
- Monitoring — 2026-10-05 21:21 UTC
- Resolved — 2026-10-05 22:42 UTC · 3h 56m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Ashby against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Ashby: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Ashby report →
More from Ashby
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.