Is Lever down?

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.

We are investigating an issue affecting Nylas authentication Users may experience errors when attempting to reset email/calendar integration permissions. Start time: 10:10 am PT Next update: 1:00 pm PT or sooner.

We are continuing to investigate this issue. Next update: 3:00 pm PT or sooner.

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

Mitigation steps have been applied and service functionality is returning to normal. We are monitoring performance and stability. Next update: upon resolution.

Issue Description: Users may have received an "Unknown error" when attempting to send emails or sync their Microsoft email and calendar in Lever. Customer Impact: Affected users were unable to authenticate their Microsoft email and calendar integrations, blocking email sends to candidates and calendar sync functionality critical to recruiting workflows. Status: Resolved — Email sends and calendar sync are now functioning normally. An RCA will be available within 7-10 business days.

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

On 7-3-2026 we were made aware of an issue impacting Lever instances with Nylas authentication (generally used for customers with on-premise Microsoft Exchange email/calendar services). Only Nylas authentication is impacted, there has been no similar behavior observed for customers authenticating with Office 365 or Google services. Users may experience a "500 error" message when attempting to reset email/calendar permissions and we have observed several unexpected email loops causing candidates to receive duplicate emails every 10 to 15 minutes as a result of this issue. Root cause: The 500s and email failures are caused by a known bug in Node.js v24.17.0 (https://github.com/nodejs/node/issues/63989). The v24.17.0 security release (CVE-2026-48931) changed `http.Agent` keep-alive socket handling so that `node-fetch` throws `ERR_STREAM_PREMATURE_CLOSE` ("Premature close") on gzipped responses to external providers (Nylas/Google). Our services picked it up this bug via the Node 18→24 migration (Occurred on 06-30-2026). The bug was fixed upstream in Node 24.18.0 This issue should be fixed in a deployment today (7-8-2026). We will provide updates on the issue status and deployment timeline as soon as possible.

A fix has been implemented as of approximately 12:15pm PST/PDT on 7/8/2026. Email and Calendar sync are now fully functional for Lever instances configured with Nylas authentication. We are continuing to monitor the effectiveness of the fix. A Root Cause Analysis (RCA) will be published to this issue within the standard Service Level Agreement.

This incident is resolved. A Root Cause Analysis (RCA) will be published to this issue within the standard Service Level Agreement.

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

We are currently investigating an issue impacting access to our platforms. A broader Cloudflare service disruption is affecting connectivity, resulting in: Request timeouts Increased latency and slow page loads Cloudflare-generated error pages (including 5xx errors) Intermittent access to platform services Our teams are actively monitoring the situation and assessing the impact on our services. While the issue appears to originate from Cloudflare's infrastructure, we continue to monitor service health and will provide updates as additional information becomes available. Customers can monitor Cloudflare's incident status directly at: https://www.cloudflarestatus.com/ Start Time: ~9:35 EDT We apologize for the inconvenience and appreciate your patience while service providers work to restore normal operations. Customer Impact: Users may experience intermittent access issues, delayed responses, request failures, or Cloudflare error pages when accessing platform services. Reference: Cloudflare Status Page — https://www.cloudflarestatus.com/

Monitoring Third-Party Network Issue Status: We continue to monitor an ongoing third-party network incident affecting Cloudflare, which is causing intermittent timeouts, increased latency, and occasional Cloudflare error pages for some users accessing our platforms. Based on updates from Cloudflare, the issue is related to a network infrastructure event in North America, and their engineering teams are actively rerouting traffic and implementing mitigation measures to restore service stability. At this time, the underlying issue resides with a third-party provider and is outside of our direct control. Our teams are closely monitoring the situation and validating service availability as Cloudflare implements corrective actions. Customers may continue to experience intermittent connectivity issues, slow response times, or timeout errors until Cloudflare has fully resolved the incident. For the latest updates, please monitor Cloudflare's status page directly: https://www.cloudflarestatus.com/ We appreciate your patience and will continue to provide updates as new information becomes available.

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.

We became aware of an issue Affecting the North America data center where Visual Insights is not loading new data in some customer accounts. The issue started occurring on Tuesday, 6/16/2026 at approximately 7:30am PST/PDT. Updates will be provided as we work to investigate the issue.

We are continuing to investigate this issue affecting Visual Insights. New data may be delayed to appear in Visual Insights or may be missing. Start time: 6/16/2026 7:30am PST/PDT Next update: 6/17/2026 8am PST/PDT or sooner.

We have identified the issue affecting the Visual Insights (Snowflake) database and have implemented a fix on Wednesday, June 17 at approximately 10:30am PST/PDT.

We are continuing to monitor the effectiveness of the fix for Visual Insights reporting. We anticipate that reporting data may still have discrepancies for approximately 10 to 15 hours. We are continuing to monitor that data is backfilling on schedule as expected. Next update: 6/17/2026 5pm PST/PDT or sooner.

The data backfill has completed at approximately 5:00am PST/PDT on 6/18/2026. All Visual Insights reports should now be a complete and accurate representation of current data. A root cause analysis (RCA) will be published to this incident within the standard Service Level Agreement (SLA).

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