Ashby incident
Increased Errors Due to Amazon Web Services Outage
Ashby experienced a major incident on October 20, 2025 affecting Email and Google and 1 more component, lasting 17h 44m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 07:06 AM UTC
We are currently investigating a spike in error rates impacting various parts of the Ashby platform. The issue appears to be widespread and may be related to upstream service provider. Some users may experience difficulty logging in or intermittent errors. We will provide updates as we learn more.
- identified Oct 20, 2025, 07:25 AM UTC
Our upstream service provider AWS acknowledged a widespread incident affecting multiple services. We'll continue to monitor and provide updates as we learn more.
- identified Oct 20, 2025, 08:36 AM UTC
We are currently experiencing widespread availability issues. Multiple components of Ashby are unavailable at this time. We have implemented partial service restrictions to minimize impact and are actively working to restore full functionality.
- identified Oct 20, 2025, 09:54 AM UTC
We are gradually restoring services. Multiple components are being brought back online in a controlled manner. Performance may be intermittent as we complete the recovery process.
- monitoring Oct 20, 2025, 10:16 AM UTC
All services have been restored. We are currently processing the backlog of queued tasks and will provide an update once this is complete.
- monitoring Oct 20, 2025, 12:00 PM UTC
We have processed the backlog of queued actions and are currently working on replaying actions that failed during the incident
- monitoring Oct 20, 2025, 02:49 PM UTC
All of our systems have fully recovered and are running at nominal levels. We have secured enough capacity to ensure we can run our services as normal throughout the day. AWS has shared a recent update where they're seeing increased error rates in some of their services, which are not currently affecting Ashby. We will continue to monitor further announcements from AWS and will provide an update once we have confirmation of full recovery. We continue to work on replaying actions that failed during the incident.
- monitoring Oct 20, 2025, 02:56 PM UTC
We are aware of an issue with the AI Notetaker, where the Meeting Bot fails to show up to the interview. We have determined this to be caused by the AWS incident, and will continue to monitor for recovery.
- monitoring Oct 20, 2025, 03:44 PM UTC
We are seeing issues with Direct Booking links, where candidates may see an error when trying to schedule an interview. We are also seeing delays when scanning incoming files for viruses. Reports and Dashboards may also display stale data. We will continue to monitor AWS status, and will provide further updates as soon as we have them.
- monitoring Oct 20, 2025, 08:00 PM UTC
We are seeing reduced errors in our Direct Booking system. Reports and Dashboards should no longer display stale data. We are still experiencing delays when scanning incoming files for viruses, and when sending report alerts and scheduled dashboard deliveries. We will continue to monitor AWS's recovery and will provide further updates as we have them.
- monitoring Oct 20, 2025, 10:07 PM UTC
AWS is reporting decreased error rates across their services. We have restored our virus scan, report alert, and scheduled dashboard delivery systems. AI Notetaker bots should now be joining interviews as expected. We are continuing to monitor our system's health as it works through the backlogs of queued tasks for those components.
- monitoring Oct 21, 2025, 12:18 AM UTC
AWS has resolved their upstream incident. Our systems have caught up on their backlogs of pending tasks. We are continuing to monitor our systems to ensure a full recovery.
- resolved Oct 21, 2025, 12:51 AM UTC
This incident is resolved. All systems are operating normally.