Lever Status Page

Aug 12, 2026 · resolved Aug 12

**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.

Aug 7, 2026 · resolved Aug 7

**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.

Jul 14, 2026 · resolved Jul 14

**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.

Jul 13, 2026 · resolved Jul 14

**Incident Summary** On July 13, 2026, customers using Microsoft \(Office 365\) for email and calendar integration experienced service disruptions. Affected users were unable to authorize or re-authorize their email and calendar connections within Lever, often encountering an "Unknown error" message. Additionally, outbound emails sent through the Microsoft integration failed to deliver during this period. Google-based email and calendar services remained fully operational and were not impacted by this incident. **Detection** The issue was identified on July 13, 2026, at 2:22 PM ET, following reports from customers to our Support team. Upon investigation, the engineering team confirmed the failures and initiated a high-priority response. While the underlying technical expiration occurred on July 12, 2026, the impact became visible as users attempted to refresh permissions or send outbound communications the following day. **Root Cause** The incident was caused by the expiration of a digital security credential used to securely communicate with Microsoft. This credential acts as a secure "password" that allows our systems to sync email and calendar data. Because this was a shared credential used for the Microsoft integration, the expiration affected customers using Office 365 broadly rather than a specific account. **Resolution** To resolve the issue, our engineering team generated a new security credential and updated the integration settings across our environments. Once the new credential propagated through the system, service was fully restored. Restoration was verified through internal testing and confirmed by successful customer re-authorizations by 8:28 PM ET on July 13, 2026. No data loss occurred as a result of this incident. **Preventative Measures** To prevent a recurrence of this issue, we are implementing the following improvements: * **Automated Expiry Tracking:** We are establishing a formal tracking process for all integration credentials with automated reminders set well in advance of expiration dates. * **Proactive Monitoring:** New alerting has been configured to detect spikes in authorization failures, allowing our team to identify and resolve similar issues before they impact customers.

Jul 8, 2026 · resolved Jul 9

**Incident Summary** Between July 2, 2026, and July 8, 2026, Some customers experienced intermittent failures affecting email and calendar services. The primary impacts included errors when sending or syncing emails and occasional "500 errors" during login. These issues were caused by a technical regression in the underlying runtime environment \(Node.js\) that handles outbound connections to third-party services. For a subset of customers using specific email integration settings, the connection instability caused the system to incorrectly perceive a successful email send as a failure. This triggered an automated retry mechanism, which in some cases resulted in a "retry loop" where the same communication was re-sent to recipients at regular intervals until the connection was stabilized. **Detection** The issue was identified following reports of intermittent service disruptions. Our support and engineering teams conducted a thorough investigation into these reports, identifying a specific pattern of connection failures within our system logs. Further analysis confirmed that the impact began on approximately July 2, 2026, following a routine update to our service infrastructure. **Root Cause** The root cause was a defect in a specific version of Node.js \(version 24.17.0\), the software environment used to run our services. This version contained a flaw in how it managed "keep-alive" connections—reusable connections used to communicate with external services. Under certain conditions, the software would prematurely close these connections before a task was completed, resulting in failed email sends and data sync errors. **Resolution** To resolve the issue, our engineering team performed the following steps: * **Identification:** Correlated the "Premature close" errors to a known regression in the Node.js runtime. * **Upgrade:** Updated our base system images to Node.js version 24.18.0, which contains the official fix for this connection issue. * **Deployment:** Rebuilt and redeployed critical services \(including email and calendar components\) on the corrected version. * **Verification:** Confirmed that connection errors ceased and service stability returned to normal levels on July 8, 2026. **Preventative Measures** To prevent similar issues in the future, we are implementing the following improvements: * **Version Pinning:** We have updated our build process to ensure we deploy only versions that have been fully verified. * **Enhanced Monitoring:** We are adding specific alerts for outbound connection errors to detect and respond to similar communication failures more rapidly. * **Automated Testing:** We are implementing new synthetic checks for email and calendar synchronization to proactively identify issues before they impact customers. * **Improved Visibility:** We are updating our internal dashboards to provide better visibility into the exact software versions running in our production environment to speed up future diagnoses.

Is Lever down right now?

No — Lever is up. All systems operational as of Aug 19, 10:39 PM UTC.

What is Lever's current status?

Lever: All Systems Operational. Alert24 checks Lever's status page continuously and can notify you the moment it changes.

How do I get alerted when Lever goes down?

Alert24 monitors Lever and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.