Is Lever down?

At about 8:30am UTC on 8/25/2026 a scheduled server rotation at https://hire.eulever.co/ caused increased latency and some failed page loads until 9:15am UTC. Impacted users would notice a "504 error" during the affected page loads. Service was restored to all users as of 9:15am UTC on 8/25/2026. An full RCA will be posted to this issue within 7 to 10 business days.

We are currently investigating this issue.

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

Status: Resolved Our monitoring has confirmed that there are no further issues related to this incident. Service has remained stable, and the incident is now considered resolved. A Root Cause Analysis (RCA) will be provided within 7-10 business days.

At about 10:31am PST on 8/12/2026 Lever Support initiated a backend data query that caused Lever hire services to encounter an out of memory error. The result of this caused site degradation and failed page loads for hire.lever.co between 10:31am - 10:46am PST. Impacted users would notice a "500 error" during the affected page loads. Service was restored to all users as of 10:46am PST. At this time we are working on continued enhancements to mitigate the risk of Lever Support initiated queries triggering outages in the future. An full RCA will be posted to this issue within 7 to 10 business days.

**Incident Summary** On August 12, 2026, between approximately 10:31 AM and 10:45 AM PDT, the Lever platform experienced partial unavailability. During this 14-minute window, some customers were unable to access the platform, and others experienced elevated error rates for API requests.  **Detection** The issue was identified through internal monitoring. A Datadog alert for high database page faults triggered at 10:37 AM PDT, notifying the engineering team. This allowed responders to isolate the specific database nodes experiencing high load and identify the responsible operations.  **Root Cause** The incident was triggered by a safety mechanism within an internal administrative tool designed to prevent expensive database queries. When an operator searched for unindexed data, this safety check requested a "plan" from the database to see if the query was safe to run. However, because the data was unindexed, the database attempted to evaluate every possible retrieval method, resulting in the same large account being scanned 11 times for a single request. These diagnostic checks bypassed standard time limits, consuming the database read capacity required for normal customer traffic.  **Resolution** Engineering teams identified and terminated the long-running diagnostic operations, which immediately restored database performance and platform stability. Following the cleanup, a database-level safeguard was applied to force these specific queries into a single, efficient path, preventing the database from attempting multiple expensive scans in the future.  **Preventative Measures** * **Redesigning Safety Checks:** We are replacing the current diagnostic method with a new system that verifies query safety by inspecting database definitions directly, eliminating the need to run expensive tests on live data. * **Advanced Alerting**: We are implementing new monitoring for database read churn and long-running operations to detect and resolve similar issues before they affect customers. * **Enhanced Logging:** We are improving internal audit logs to ensure faster identification and attribution of administrative database activity. * Database Optimization: We are adding new indexes to properly support these search patterns, ensuring they are inherently efficient.

Issue: We are aware of an active outage with Adobe Sign, a third-party e-signature provider. This is affecting Lever customers who use the Adobe Sign integration. Customer Impact: Recruiters may be unable to generate or send offer letters for e-signature via Adobe Sign. Candidates with pending Adobe Sign requests may be unable to sign at this time. Customers using DocuSign and all other Lever functionality are unaffected. Status: Investigating. This is an upstream issue with Adobe; we are monitoring and will update as Adobe provides more information. For direct updates from Adobe, see their status page at https://status.adobe.com/

Update — Offer Letter Sending Disrupted Issue: We've identified that this disruption is broader than initially scoped. The Adobe outage is impacting our PDF conversion process, which all offer letters — regardless of e-signature provider (Adobe Sign, DocuSign, or Native eSignature) — depend on to generate the final document. Customer Impact: All customers are currently unable to send offer letters successfully. This is no longer limited to Adobe Sign integration users. Recruiters attempting to generate or send an offer letter may see failures or delays regardless of which e-signature method is configured on their account. Status: Investigating.

We found that our Fallback document converter in case of an Adobe PDF Services API outage is not working as expected. We are working on a fix to implement an immediate fallback document converter to prevent failed/stuck offer sends in cases of an Adobe PDF Services API outage. Next update: 4pm PST/PDT or earlier For the most up to date status on the Adobe API outage follow: https://status.adobe.com/products/503500/202608070024

A fix has been implement to immediately fallback to an alternate document converter after offer document conversions are stuck for a period of time. We are currently processing through a backlog of offer sends and we expect the backlog processing to take around one to two hours. Users may notice a delay sending offers, but offer documents should send successfully. Any document (resumes, offers, etc.) image previews may show loading failures while the backlog processing catches up to real time. We are continuing to actively monitor the document previewer and Adobe PDF Services API outage.

This incident has been resolved. The document converter is now processing in real time. Offers are sending with no delay and all document previews in Lever should be visible.

**Incident Summary** On August 7, 2026, between approximately 6:00 AM and 5:30 PM ET, some customers were unable to send offer letters, and some document and resume previews failed to generate. Files uploaded successfully; only the step that converts them into a viewable PDF or preview failed. No data was lost.  **Detection** Identified on August 7 at approximately 11:47 AM ET following customer reports to our Support team. **Root Cause** A third-party service we use to convert documents into PDFs experienced an outage lasting most of the day. During it, the service accepted conversion requests but never completed them. Our system is designed to switch to a backup conversion method when that service reports a failure — but because these requests neither succeeded nor failed, they simply waited, and the backup was never used. Each waiting request also occupied one of a limited number of conversion slots, so delays spread to other documents.  **Resolution** We added a strict overall time limit to document conversions: if the third-party service does not finish within that window, we stop waiting and convert the document using our own backup method instead. We also corrected a related defect that had prevented the backup from being used reliably. Both fixes were released to production on the afternoon of August 7, while the third-party outage was still ongoing, and conversion success rates returned to normal levels the following day. We then re-processed the documents that had failed to convert during the outage.  **Preventative Measures** ·       We fixed a defect that had prevented this service's health measurements from reaching our monitoring system and are adding alerts on the document conversion failure rate, so issues like this are detected automatically and quickly, rather than through customer reports. ·       The new time limit can be adjusted without a code release, and we are documenting a procedure to route all conversions away from the third-party service during a vendor outage.

Issue: We are investigating what appears to be a platform-wide issue in which offer letters fail to be sent. Customer Impact: Recruiters are currently unable to generate or deliver offer emails to candidates. Current Status: Engineering is actively investigating. No workaround is available at this time.

Issue: We identified a platform-wide issue in which offer letters failed to be sent. Customer Impact: Recruiters were unable to generate or deliver offer emails to candidates. Current Status: The immediate issue has been mitigated. We are actively monitoring to confirm full resolution and stability.

Issue: We identified a platform-wide issue in which offer letters failed to be sent. Customer Impact: Recruiters were unable to generate or deliver offer emails to candidates. Status: Resolved. An RCA will be available within 7-10 business days.

**Incident Summary** Between approximately July 13 and July 14, 2026, some customers were intermittently unable to send offer letters, and some document/resume previews failed to generate. While source files were uploaded successfully, the conversion step required for previews and offer generation failed. No data loss occurred. **Detection** The issue was identified on July 14, 2026, at approximately 10:43 AM ET, following reports from customers to our Support team. Engineering confirmed the impact through monitoring, which showed a steady increase in process counts within the document-converter service until it reached a hard system limit, causing subsequent tasks to fail. **Root Cause** The incident was caused by a "process leak" introduced during a recent platform upgrade. A change in how the system handles document conversions meant that each conversion started a new background process that was never properly closed. Over several days, these background processes accumulated until the system reached its maximum capacity. Once this limit was hit, the service could no longer start the new processes required to generate offer letters or document previews. **Resolution** * **Initial Mitigation:** At 11:20 AM ET on July 14, engineers restarted the affected service pods. This cleared the accumulated background processes and immediately restored the ability for customers to send offer letters and view previews. * **Permanent Fix:** A code update was developed and deployed at 8:43 PM ET on July 14. This fix ensures that all background processes are correctly terminated and cleaned up after every conversion, preventing any future accumulation. **Preventative Measures** * **Code Improvements:** Implemented a robust process-management system \(using a "reaper" process\) to ensure all background tasks are automatically closed upon completion. * **Enhanced Monitoring:** New automated alerts have been configured to notify the engineering team if process usage exceeds 50% of the system limit. This will allow us to identify and resolve similar resource leaks days before they impact customers. * **Backlog Processing:** A separate initiative was completed to identify and reprocess any document or resume previews that failed to generate during the outage window to ensure all previews are available to users.