Lever experienced a minor incident on June 17, 2025 affecting Hire, lasting 9h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 17, 2025, 09:21 AM UTC
We are currently investigating an issue that is intermittently affecting the navigation of the Lever webpage. Issues impacting candidate profiles were noticed around 2 am Pacific Time. Users may intermittently experience delays/non-responsiveness when navigating through candidate profiles and attempting specific actions. Our Engineering teams are actively working to resolve this as soon as possible.
- monitoring Jun 17, 2025, 11:02 AM UTC
A fix has been implemented for the issue causing latency/interactivity issues on the candidate profiles. Customers should now be able to properly access candidate profiles and navigate the pages. We’re currently monitoring to ensure that there are no further issues, and we’ll send a final update to confirm that there have been no recurrences.
- resolved Jun 17, 2025, 06:27 PM UTC
The issue with interactions on candidate profiles has been resolved, and we have not seen any additional occurrences of this behavior. The incident occurred from approximately 1:30 am Pacific time until approximately 3:30 am Pacific time on 6/17/2025. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
- postmortem Dec 18, 2025, 10:56 PM UTC
**Incident Date:** June 17, 2025 **Issue:** Profile Flyover Latency and Navigation Failure ### **Impact Summary** On June 17, 2025, users experienced an issue where opening a profile flyover with a scheduled or completed interview triggered an error that prevented further navigation within the application. This was introduced by a deployment and resolved within 30 minutes via a rollback. ### **Root Cause** A code change introduced a query that relied on a parameter incorrectly assumed to always be present resulting in a navigation-blocking error. ### **Preventive Actions** 1. **Enhanced Testing Practices** * Additional acceptance test coverage expanded to include profile flyovers with scheduled or completed interview scenarios for similar code changes in the future 2. **Improved Error Monitoring** * We are evaluating enhancements to our error monitoring to more effectively detect spikes in specific error types.