Is Ashby Down Right Now? Check if there is a current outage ongoing.

We are continuing to monitor for any further issues.

We are aware of and are monitoring an issue with the command.ai service which is affecting the usability of the AI chat in Ashby Help Center.

Google Workspace APIs are intermittently erroring without explanation. Google has not yet created an official incident, but we are monitoring. Ashby customers using Google Workspace will not be able to reliably email or schedule.

We have identified and resolved an issue affecting email sending in Ashby between 13:05PM and 13:30PM UTC.

We are aware of and monitoring an outage with the OpenAI service, which is impacting certain AI features in Ashby.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified an issue causing the login page to be unavailable to users. We are actively working on a fix.

We have identified an issue causing the login page to be unavailable to users. We are actively working on a fix.

This incident has been resolved.

The fix has been deployed. We recommend refreshing your browser. We're monitoring rollout of the fix.

We have an identified an issue viewing job details pages within Ashby, such as when configuring or editing a job. We're deploying a fix.

We have an identified an issue with job configuration pages failing to load. We're deploying a fix.

This incident has been resolved. Please refresh Ashby in your browser.

A fix has been implemented and we are monitoring the results.

We have identified an issue adding filters in Ashby. We have located the cause and are working on a fix. Please use advanced mode until a fix is deployed.

We have identified an issue adding filters in Ashby. We have located the cause and are working on a fix. Please use advanced mode until a fix is deployed.

The fix is live, and we've verified that candidate email replies are working again.

We have identified an issue where clicking reply on a candidate email closes the candidate profile. We're deploying a fix.

We have identified an issue where clicking reply on a candidate email closes the candidate profile. We're deploying a fix.

This incident has been resolved.

The Zoom service is having a major outage which is impacting scheduling in Ashby. If you need to schedule or reschedule a candidate, please use Google Meet or another video conferencing service. We've put together a quick video of how to do it here: https://www.tella.tv/video/how-to-change-meeting-location-0af4

The Zoom service is having a major outage which is impacting scheduling in Ashby. If you need to schedule or reschedule a candidate, please use Google Meet or another video conferencing service. We've put together a quick video of how to do it here: https://www.tella.tv/video/how-to-change-meeting-location-0af4

This incident has been resolved.

We've shipped a fix. Users will need to refresh Ashby in their browser to see the fix.

We have identified an issue where editing an Application Form does not save. We are implementing a fix.

We have identified an issue where editing an Application Form does not save. We are implementing a fix.

This incident has been resolved.

We've identified an issue causing intermittent errors in Ashby and are working on a fix.

This incident has been resolved.

We've identified an issue causing intermittent errors in Ashby and are working on a fix.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing maintenance on the infrastructure that supports Ashby. We expect this maintenance window to last less than 1 minute.During this period, all Ashby pages may take longer to load, or fail to load entirely.If you have any concerns, please contact us at support@ashbyhq.com.

This incident has been resolved.

We are investigating an issue with loading some candidate profile pages. The issue is intermittent.

This incident has been resolved.

We're aware of and monitoring 3rd party issues affecting Ashby notifications sent to Slack and interview channel creation on Slack.

This incident has been resolved.

We have identified the bottleneck and applied a fix. Latency is improving and we are monitoring.

Since about 00:40 UTC, bulk actions, webhooks, email campaigns, offer templates and some notifications have been experiencing delays and errors. We are investigating the issue

A fix has been applied and calculated fields of grouping type are now loading. The incident has been resolved.

We have identified a potential issue preventing the loading of calculated fields of grouping type and are applying mitigations.

Our engineering team is currently investigating an issue where calculated fields of grouping field type are currently unable to load in Ashby.

From Thursday, January 9 to Tuesday, January 14, 2025, Ashby’s scheduling features allowed users and candidates to book over a subset of recurring calendar events \(events without an end date\). The issue impacted all scheduling features: direct booking, manual scheduling, and auto-scheduling. Approximately 6.6% of interviews scheduled during this timeframe conflicted with existing recurring events. **Why did this happen?** Ashby keeps an up-to-date record of users' calendar events in order to power our scheduling features. To speed up these features, an automated task regularly deletes these events when they are no longer relevant for scheduling. An update to this task was deployed on January 9. This update contained a bug that deleted all recurring events without a specified end date. **How did we resolve the situation?** On Thursday, January 9, 2025 at 3:06AM PST, we deployed the change containing the bug. At 6:05PM PST, the affected code ran as scheduled and deleted events that should not have been deleted. On Friday, January 10 at 8:19AM PST, we became aware of the issue. By 10:28am PST, we had identified the steps required to restore the missing events and began that process. By Saturday, January 11 at 1:14AM PST, we had restored what we then thought were all missing events for all customers. On Monday, January 13 at 6:16AM PST, we received new reports of double-booked interviews. By 2:58PM PST, we had identified an issue in how we had restored missing events, impacting 2.8% of application users. By 5:11AM PST on January 14, we had fixed the root cause and started restoring the remaining events. By 8:30AM PST, this restoration was finished. **What have we put in place to prevent it from happening in the future?** For the specific automated task that deletes events, we have implemented a method for allowing near-immediate restoration of deleted calendar events. In addition, we have updated our QA processes to be more comprehensive for changes to this automated task. As part of the postmortem we conducted after the incident was fully resolved, we determined that better tooling could have allowed us to release this update to a small subset of customers before rolling it out further. While we do this for most features, we do not have it for these automated tasks. We are currently working on that tooling.

This incident has been resolved.

We have now re-synced all calendars and are continuing to monitor.

We're continuing to resync customers' calendars.

We're continuing to resync customers' calendars, but due to the volume, we're doing it incrementally and anticipate this will continue over the weekend.

We have rolled back the change. Only some recurring calendar events were affected, but we are resyncing the calendars of all customers. This process may take up to several hours and we will provide updates throughout the day.

We've identified an issue where busy recurring calendar events are not being considered in scheduling features: manual scheduling, direct booking, and autoschedule. We are rolling back a change.

The issue has been successfully resolved.

We have identified the issue and are currently rolling out a fix.

We are currently looking into an issue affecting email sending via Ashby.

Reports using the Job's Was Open filter are operating normally again.

The fix is being rolled out.

We have a fix coming, and while working on the fix, we identified that this issue impacts all reports that use the Job's Was Open filter.

We have identified an issue that is resulting in some reports in the jobs core dashboard incorrectly reporting no results. It's impacting the following reports on this dashboard: Open Jobs by Recruiter, Open Jobs by Department, Open Jobs by Hiring Manager, and Monthly Open Jobs

This incident has been resolved.

We have identified an issue that is slowing down some features including: * Bulk actions * Email campaigns * Notifications * AI products * Webhook processing. We are identifying the root cause and mitigation.

We are no longer observing delays with email and calendar syncs.

We've now found a resolution, and are waiting for sync to catch up.

We've identified an infrastructure issue causing delays with calendar and email sync. We anticipate it being resolved in the next hour or so.

We're investigating an infrastructure issue that causes delays with calendar and email sync.

This incident has been resolved.

Due to an earlier incident, reports and dashboards may require more time to load.

This incident has been resolved.

Reports are now loading, however performance is still degraded for some reports and dashboards. Reports may show increased errors.

We have identified a potential issue causing reports to be unable to load and are applying mitigations.

We have identified an issue at 10:32 PST where reports are currently unable to load in Ashby. Our engineering team is investigating.

We are no longer observing delays with email and calendar syncs.

We've now found a resolution, and are waiting for sync to catch up.

We've identified an infrastructure issue causing delays with calendar and email sync. This impacts Sequences and Scheduling, and we anticipate it being resolved in the next hour or so.

We have now fixed this and will continue to monitor

We have identified an issue preventing viewing some candidate projects and are working on a fix

This incident has been resolved.

Since about 15:30 UTC, bulk actions, webhooks, and some notifications have been experiencing delays of up to 15 minutes. Latency is improving and we're monitoring performance.

For approximately 15 minutes, features in Ashby that acted on candidates had a higher frequency of errors. Our monitoring paged our team and we quickly identified and resolved the issue.

This incident has been resolved.

We've identified an issue that is causing the Bulk Application Review to initially show a blank page for the candidate's details and are working on a fix. The workaround is to click one of the tabs "All," "Application," or "Resume." Once a tab is clicked Bulk Application Review will no longer show a blank page.

We are no longer observing rate limit errors at normal load so are considering this issue resolved.

Google Support confirmed they are receiving multiple reports of an issue and they are investigating. We have seen rate limit errors decrease significantly and have enabled real-time sync. We will continue to monitor.

Gmail's API has unexpectedly decreased rate limits, significantly reducing the number of emails we can send and sync on behalf of customers. We have reached out to Google Support for further information. We have disabled real-time sync of email for all customers to allow emails to be sent via Ashby.

We've identified that other vendors (e.g., Front) are experiencing similar issues with the Gmail integration. We have contacted Google Support for further information on whether their API is experiencing an outage. We have disabled realtime sync of email for all customers to allow emails to be sent via Ashby

We are currently looking into an issue affecting email sending and syncing with Gmail.

This incident has been resolved.

We are seeing recovery and are monitoring the situation.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We've identified an issue preventing offer letters and other signature documents from being generated from templates. We are deploying a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We have identified an issue that is preventing sequences from being sent in the Chrome Extension and are reverting

We've rolled back a change and confirmed the issue is now fixed. Please refresh Ashby in your browser.

We've identified an issue that's causing all candidate resumes not to be available in the browser and require a download.

This incident has been resolved.

The issue has been fixed. You may need to refresh Ashby in your browser to see the missing scheduling activity again.

We've identified an issue with some customers where scheduling activities are missing when moving a candidate to a stage with an activity configured. We are working on a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue where users encounter an error when clicking on a custom list report in the dashboard.

Between 1:31PM-1:36PM (UTC) Ashby was unavailable due to a bad deployment. We've fixed the issue and Ashby is operating as normal.

This incident has been resolved.

Failures have stopped, and we are monitoring the situation

We are experiencing intermittent application submission failures

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We’re seeing reports of customers running into errors during application review. We’re investigating the issue.

This incident has been resolved

We have deployed a fix and are monitoring the situation

We are currently deploying a fix

Our data sync queue size has returned to normal levels.

The data sync queue is clearing, and we expect to be fully recovered in 10 minutes.

We have identified an issue with our data sync queue and are working on a mitigation.

We are investigating an issue preventing sync from Google services including user, email, and calendar sync.

The responsible change has been rolled back.

We identified an issue that prevents logging in via Google Auth.

We deployed a configuration change that inadvertently resulted in some scheduled jobs failing to run. This resulted in delays in syncing users and calendars, refreshing job and data feeds, syncing some HR integrations, and sending interview digest emails and reminders. Service was restored 1 hour and 37 minutes after deploying the configuration change.

Mar 18, from 1:22PM PDT \(20:22 UTC\) to 3:20PM PDT \(22:20 UTC\), when a candidate visited a Direct Booking Link, selected a time, and clicked “Book,” Ashby presented the candidate with an error that the time could not be booked. #### **Why did this happen?** Our infrastructure runs snapshots of code built for specific computer architectures we provision in our servers on Amazon Web Services. Last week, we inadvertently changed the targeted computer architecture of our direct booking code snapshots to ones incompatible with our servers. Since we keep backups of snapshots, direct booking continued to work until the old snapshot expired today. The expiration caused our infrastructure to use the newer incompatible snapshots and fail. #### **How did we resolve the situation?** Our on-call engineer identified the issue internally within 30 minutes, updated [status.ashbyhq.com](http://status.ashbyhq.com/) immediately, and resolved the issue approximately 2 hours later. As part of remediation, we contacted affected candidates and customers directly. #### **What have we put in place to prevent it from happening in the future?** That day, we added monitoring to detect this specific issue immediately \(versus minutes later\). We also performed a post-mortem and determined that the root cause was the lack of developer tooling and safeguards on some of our infrastructure. We have started adding the necessary hardening features to prevent this situation from occurring again.

We are considering the incident resolved.

We have resolved the infrastructure issue and are monitoring.

We've identified an infrastructure issue and are working on a fix.

We are investigating an issue where direct booking links error when candidates select a time.

This incident has been resolved.

We've identified the issue and are preparing a fix.

We are currently investigating an issue where scheduled dashboards are sent with blank squares in place of the intended reports.

This incident has been resolved.

We have put a fix in place and are monitoring the situation.

We have put a fix in place and are monitoring the situation.

We've identified an issue where emails and notifications from the Ashby no-reply address are failing to send.

The incident has been resolved.

We are seeing errors subside and traffic levels return to normal across the board. We will continue monitoring for further signs of issues.

Our upstream DNS provider, Cloudflare, is currently experiencing issues. Users may be unable to load the Ashby website or access Ashby APIs.

Dropbox Sign identified the bug and has resolved the issue with our integration.

Signature requests that have a signer order may get sent in reverse order due to an issue with our downstream e-signature provider, Dropbox Sign. The email Dropbox Sign sends you after sending the e-signature request has the order it will be sent in, which may or may not match what was set in Ashby. Please verify the order matches what you expect, until we reach a resolution.

The issue has been resolved.

Service has recovered, and we are continuing to monitor.

Some customers are reporting issues with email sending and calendar syncing in Ashby. We’ve identified that Google Workspace is rate-limiting these customers. This is affecting multiple companies with Google Workspace integrations (e.g., Front: https://www.frontstatus.com/), and we have no indication this is isolated to Ashby. We are continuing to investigate whether we can make any changes on our side, but customers have reported success with logging out and re-authorizing their Google Workspace connection. You can do so here: https://app.ashbyhq.com/settings/gsuite.

This incident has been resolved.

OpenAI implemented a fix and AI features should be available again.

Our partner OpenAI is reporting an incident in their API. Due to that, AI features in Ashby are currently slow or unavailable. This includes: - AI outreach token - AI filter assistant - Automatic sequence reply status

This incident has been resolved.

We've rolled back the change. Users will need to refresh Ashby in their browser.

We've identified an issue where forms are showing no fields. This affects any form in Ashby, from application forms to referral forms. We are rolling back a recent change to resolve the issue.

This issue has been resolved. If you continue to see issues, please deactivate and reactivate the extension.

The fix for the Ashby Chrome Extension on LinkedIn has been released. If you continue to see issues, please deactivate and reactivate the extension.

We've identified a change on LinkedIn's site and are deploying a fix for the Ashby extension.

We're currently investigating elevated failure rates loading candidate profiles from LinkedIn.

We have verified that candidate activities are now auto-populating.

We are currently investigating an issue where some activities, such as interview activities are not auto-populating when changing a candidate's stage. Refreshing the candidate profile will make the activities appear.

This incident has been resolved.

A fix has been implemented, and updates from Dropbox Sign are being processed normally. We are working to fix existing signature requests to show the correct most recent status.

Some e-signatures and offer letters in Ashby may not show the most recent status (e.g., sent, viewed, signed) due to issues with our vendor, Dropbox Sign. We are investigating a workaround and working with Dropbox Sign to resolve the issue. E-signatures and offers are still operational but, for instance, may show unsigned in Ashby when the offer or document has been signed. A byproduct is some additional features like reminders may error because they are not relevant to the current status of the document.

Google has indicated the incident with Google Calendar has been resolved. We have confirmed that Ashby Calendar Sync and Scheduling is no longer affected by this third-party outage.

There is an ongoing disruption to the Google Calendar service. We will continue to monitor the situation until it has been corrected. You can find more details for this disruption on the Google Workspace Status Dashboard: https://www.google.com/appsstatus/dashboard/incidents/7uJZ5F1Uy4n1n74iMacQ

We're experiencing issues with scheduling and calendar sync due to a Google Workspace outage. You can see additional details on this Google Workspace outage at: https://www.google.com/appsstatus/dashboard/incidents/7uJZ5F1Uy4n1n74iMacQ

This incident has been resolved.

A fix has been implemented, and we are monitoring the results.

We've identified an issue where candidate profiles are erroring. We are working to resolve the issue.