Is Ashby down?
Last checked 7m agoNo incidents right now.
Ashby is operational right now. Last checked 7m ago; the most recent incident resolved 4d ago.
Real-time Ashby status, recent outages, and incident history — pulled directly from Ashby's official status page at https://status.ashbyhq.com every 5 minutes. Pingoru tracks 31 Ashby services and has captured 23 incidents in the last 90 days (97.85% uptime). Get email, Slack, Discord, or webhook alerts the moment Ashby reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Ashby API
Timeline · 4 updates
- investigating · Jul 27, 2026, 02:56 PM UTC
We are experiencing elevated latency on the Ashby API available at api.ashbyhq.com, requests may take longer to be processed or time out altogether. The Engineering team is investigating the issue.
- identified · Jul 27, 2026, 03:12 PM UTC
We have mitigated the issue, and response times have returned to normal. We will continue to work towards full resolution.
- identified · Jul 27, 2026, 09:10 PM UTC
We are continuing to work on a fix for this issue.
- resolved · Jul 27, 2026, 09:12 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Single Sign On
Timeline · 4 updates
- identified · Jul 16, 2026, 08:40 AM UTC
We are investigating intermittent failures when signing in to Ashby using SSO. Affected users may see a login error and need to retry. Other sign-in methods and the rest of Ashby are operating normally. Our team is actively monitoring and working to restore full SSO reliability, and we will post another update as we learn more.
- identified · Jul 16, 2026, 09:12 AM UTC
We are continuing to monitor an issue where some users may intermittently experience a failed or timed-out login when signing in via SSO because of an issue in our upstream provider. If you hit an error signing in via SSO, please retry. Other login methods, including magic-link sign-in, are unaffected. We are actively monitoring and will post another update as the situation changes.
- monitoring · Jul 16, 2026, 10:57 AM UTC
Our upstream provider has resolved the incident affecting SSO sign-ins. Users should now be able to log in normally. We are continuing to monitor recovery and will provide another update if the situation changes.
- resolved · Jul 16, 2026, 11:00 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Jul 14, 2026, 02:48 AM UTC
For approximately 11 minutes from 10:19 AM PDT to 10:30 AM PDT, Ashby users experienced long-running loading screens and, in some cases, errors. This was the result of requests to our servers taking too long to respond. Candidates applying for jobs were unaffected. Our maintenance this weekend will address the root cause of this issue by increasing our database capacity.
Latest: For approximately 11 minutes from 10:19 AM PDT to 10:30 AM PDT, Ashby users experienced long-running loading screens and, in some cases, errors. This was the result of requests to …
-
- Recruiting
Timeline · 3 updates
- identified · Jul 08, 2026, 12:40 AM UTC
Due to an issue with a downstream provider, newly uploaded resumes are not being automatically parsed into structured data. Resume files remain available in the app, but contact info, work history, and plain-text content are not currently being extracted from newly-uploaded resumes. Application form autofill, AI job criteria evaluation, and resume-based search may be affected for new resumes. Email and Chrome extension resume imports may also fail until parsing is restored.
- monitoring · Jul 08, 2026, 12:58 AM UTC
Newly-uploaded resumes are now being parsed successfully. Resumes that failed to parse during the incident will be backfilled.
- resolved · Jul 08, 2026, 04:17 AM UTC
This incident has been resolved. Resumes that failed to parse during the incident have been backfilled.
Latest: This incident has been resolved. Resumes that failed to parse during the incident have been backfilled.
-
-
Timeline · 1 update
- resolved · Jul 06, 2026, 08:46 PM UTC
From 11:30am until 1:40pm PDT, candidate PDF exports failed with a generic message. The cause of this issue has already been identified and fixed.
Latest: From 11:30am until 1:40pm PDT, candidate PDF exports failed with a generic message. The cause of this issue has already been identified and fixed.
-
See the full Ashby outage history
15 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Ashby outage history →Or sign up free to get alerts when Ashby breaks · 10 free monitors · No credit card
- Elevated Ashby API Latency ResolvedStarted Jul 27, 2026, 02:56 PM UTC · Resolved Jul 27, 2026, 09:12 PM UTC · 6h 16m
- Some SSO sign-ins may fail ResolvedStarted Jul 16, 2026, 08:40 AM UTC · Resolved Jul 16, 2026, 11:00 AM UTC · 2h 20m
- Started Jul 13, 2026, 05:19 PM UTC · Resolved Jul 13, 2026, 05:19 PM UTC · —
- Started Jul 08, 2026, 12:40 AM UTC · Resolved Jul 08, 2026, 04:17 AM UTC · 3h 37m
- Candidate PDF Export Errors ResolvedStarted Jul 06, 2026, 08:46 PM UTC · Resolved Jul 06, 2026, 06:30 PM UTC · —
- Started Jul 01, 2026, 08:19 PM UTC · Resolved Jul 02, 2026, 02:14 AM UTC · 5h 54m
- Started Jul 01, 2026, 06:49 PM UTC · Resolved Jul 01, 2026, 07:03 PM UTC · 13m
- Started Jun 24, 2026, 09:16 PM UTC · Resolved Jun 24, 2026, 10:21 PM UTC · 1h 4m