Ashby outage history

We are investigating reports of latency across the platform.

We have determined the part of the system causing the latency, but we are still determining the root cause.

We are starting to see improvement in overall application performance, but we are continuing to monitor. We are still investigating the root cause

This incident has been resolved.

We received reports of some users being unable to access Ashby. This appears related to a network connectivity issue reported by our upstream provider, Cloudflare. Access appears to be recovering, and we’re monitoring for further disruption.

This incident has been resolved.

Dropbox Sign and BambooHR are experiencing service disruptions, affecting their integrations with Ashby. E-signature workflows using Dropbox Sign may fail or be delayed, including creating and sending requests, sending reminders, and cancelling requests. BambooHR integration data updates and new-hire transfers may also fail or be delayed. Both providers are performing emergency maintenance. We are monitoring their recovery and will share another update as more information becomes available.

Dropbox Sign has recovered, and its integration with Ashby is now working normally. E-signature workflows, including creating and sending requests, sending reminders, and cancelling requests, are functioning as expected.

BambooHR has recovered, and its integration with Ashby is now working normally. Data updates and new-hire transfers are processing as expected.

Some AI features may be delayed or temporarily unavailable due to an issue with our upstream AI provider. We are monitoring the situation and will share another update as more information becomes available.

We are seeing signs of recovery following the disruption to our upstream AI provider. Some AI features may still experience intermittent delays or errors. We are monitoring closely and will share another update once we have confirmed sustained recovery.

We have applied a mitigation and are monitoring recovery. We are also addressing any remaining impact from the incident. We’ll share another update once recovery is confirmed.

We have completed recovery for requests affected during the incident.

We are investigating an issue delaying updates to reporting data. Reports and dashboards may not reflect recent changes. Our team is working with our data infrastructure provider to restore updates, and we will share more information as it becomes available.

Reporting data is updating again. Reports and dashboards may still show delayed data. We’ll post another update once everything is up to date.

Reports and dashboards are now up to date, and updates are running normally. Thank you for your patience.

For a period of 43 minutes, job applications failed on job boards due to an issue with an upstream provider. We have resolved the issue with the upstream provider.

## **Summary** For approximately 43 minutes, some applicants were unable to submit applications on Ashby-hosted job boards. The issue lasted from 11:29 PM UTC on October 14 to 12:12 AM UTC on October 15. ## **Why did this happen?** Ashby uses an upstream provider to power bot-detection for job applications, helping prevent automated spam submissions on our job boards. Our billing account with this service was tied to another product we used with the upstream provider. When we sunset our use of that other product, the billing account was also removed from our bot-detection service, triggering a usage limit that prevented some checks from completing. At the time, Ashby required these checks to be completed before accepting an application. As a result, affected submissions were blocked, and the applications were not created in Ashby. ## **How did we resolve the situation?** On October 14, 2026, at 11:29 PM UTC, a member of our team worked with our upstream provider’s support to sunset usage of a different product; the changes they made affected the billing for our bot-detection service, and application submissions began failing. At 11:42 PM UTC, our team identified errors from the bot-detection service and began investigating. At 11:59 PM UTC, we restored billing for the service, allowing it to process requests beyond the usage limit. Error rates began declining as the change took effect. On October 15, at approximately 12:12 AM UTC, the final error associated with this incident was recorded. We continued monitoring, did not observe further errors of this kind, and resolved the incident.  ## **What have we put in place to prevent it from happening in the future?** We have implemented changes both to reduce the likelihood of another billing issue and to prevent a temporary failure of the third-party service from blocking applications: * **We corrected our billing setup and disconnected it from other products with the upstream provider**. * We changed how Ashby handles errors from the upstream provider’s service. **Applications now go through even if the service is temporarily unavailable**. If this were to happen again, we would prefer to let all applications through to ensure valid candidates make it into the system, since we can always clean up spam applications retroactively.

We're investigating an issue with availability being slow or failing to load when using candidate availability links.

We have applied a fix, and we're starting to see full recovery

Candidate booking is operating normally.

Some data in Ashby may take longer than usual to show up. Recent changes, like stage moves, feedback, new applications or edits to candidate records, may not appear right away in search results, lists, reports or the API. Some pages may also load slowly or time out. Your changes are being saved, but may take longer to appear in Ashby. We are actively working on resolving this incident, until then if you don't see updated data, please wait before making the update again.

We are continuing to investigate this issue.

Data is now up to date across Ashby. Search, lists, reports and the API are showing current information again, and pages that were loading slowly should be back to normal speed. We are continuing to monitor to ensure things stay stable.

This incident has been resolved.

We are currently investigating an issue affecting app availability in South East Asia.

We are continuing to investigate this issue.

We have determined the issue to be a service degradation in Cloudflare's Asia region. We are working with them to get this resolved.

We are no longer seeing the issue, we will be monitoring until we have had confirmation that the issue is resolved upstream.

The issue appears to have resurfaced, we are awaiting an update from our upstream provider. If possible, we recommend using a VPN to a server outside the affected region.

Our upstream provider has identified multiple subsea internet cable outages resulting in slowdowns in the Asia-Pacific region since September 21.

We have been informed that traffic is being re-routed around the affected region by our upstream provider. We will continue monitoring until we have confirmation that the issue is fully resolved.

This incident has been resolved.

We are currently investigating an issue affecting app availability in South East Asia.

This incident has been resolved.

Some customers are experiencing degraded functionality when importing candidates in bulk. We have implemented a fix and are monitoring the system to confirm the issue is resolved.

We're investigating degraded performance affecting document uploads and signing, caused by an incident with our upstream provider, Dropbox Sign. We are monitoring for updates from Dropbox Sign and will post as we learn more.

Our upstream provider has resolved the issue.

Our Certn Assessment integration is currently unavailable due to an unexpected connection issue with Certn. We are working with them to resolve it.

Certn has restored access for most affected accounts. A small number of accounts remain impacted and we're continuing to work with Certn to restore them

This incident has been resolved.

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.

We have mitigated the issue, and response times have returned to normal. We will continue to work towards full resolution.

We are continuing to work on a fix for this issue.

This incident has been resolved.

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. The issue is caused by an incident in an upstream provider. Our team is actively monitoring the situation and will post another update as we learn more.

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. If you're currently logged in, avoid logging out while the issue persists. Other login methods, including magic-link sign-in, are unaffected. We are actively monitoring and will post another update as the situation changes.

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.

This incident has been resolved.

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.

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.

Newly-uploaded resumes are now being parsed successfully. Resumes that failed to parse during the incident will be backfilled.

This incident has been resolved. Resumes that failed to parse during the incident have been backfilled.

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.

We are currently investigating this issue.

We are getting reports of Ashby being unavailable in Sydney. We're also getting limited reports of Ashby being unavailable in other regions, like Portland and San Francisco. We're working with an upstream provider to determine the root cause.

Our upstream provider, Cloudflare, has confirmed a connectivity issue and is working on a fix.

Our upstream provider, Cloudflare, has implemented a fix and our tests indicate they have resolved the issue.

We are currently investigating this issue.

We've confirmed Ashby is available again in the Sydney region. We will work with our upstream provider to understand what happened.