Lever Status Page

Jul 13, 2026

We are continuing to investigate this issue. Next update: 5:00 PM PT

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.

Jun 22, 2026 · resolved Jun 22

Cloudflare has reported that its traffic engineering efforts have successfully mitigated the majority of congestion and packet loss associated with this incident. As a result, service conditions are improving; however, some users may still experience intermittent connectivity issues while their recovery efforts continue. Customer Impact: Most services have stabilized, but some users may continue to experience intermittent latency, timeouts, or connectivity issues during the final stages of recovery. Customers can monitor the latest updates directly on Cloudflare's status page: https://www.cloudflarestatus.com/ We will continue to provide updates as new information becomes available.

Jun 16, 2026 · resolved Jun 18

#### **Incident Summary** Between June 14 and June 18, 2026, analytics reports in the Visual Insights "Custom Data Explorer" displayed outdated information. While the live platform remained fully accurate and no data was lost, the reports stopped reflecting real-time changes \(such as candidate stage updates\). This resulted in a "stale" snapshot of data being shown to all reporting customers for approximately four days. **Detection** The issue was identified on June 17, 2026, following reports from customers who noticed that their report counts did not match the live data in the platform. Upon investigation, our engineering team confirmed that the data pipeline responsible for updating these reports had stopped processing new information on June 14. #### **Resolution** Once identified, our engineering team restarted the affected component, which safely resumed and caught up on all pending changes with no data loss. Report accuracy was fully restored, and the cited figures now match the live platform. No action was required from customers at any point. #### **Preventative Measures** To prevent this issue from recurring, we have taken the following actions: * **Enhanced Auto-Recovery:** We updated the system to automatically recognize and recover from this specific type of database restart error, allowing it to self-heal without manual intervention. * **Improved Monitoring:** We are implementing more granular alerts that monitor the specific workers within the data pipeline. This ensures that if a single worker stops, we are notified within minutes. * **Data Freshness Checks:** We are adding new automated checks that compare live platform data against the reporting store to detect any "freshness" gaps immediately.

Jun 11, 2026 · resolved Jun 12

Posting Locations should now be populating as expected. Please follow up with Lever Support if you see any postings continuing to display an inaccurate location in LinkedIn.

Is Lever down right now?

Yes — Lever is reporting a minor incident as of Jul 13, 11:48 PM UTC.

What is Lever's current status?

Lever: Partially Degraded Service. 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.