
Lever Status
Real-time updates of Lever issues and outages
Lever status is Operational
Hire
Microsoft Exchange (Nylas) Email/Calendar Integration
You're checking on Lever - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
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.
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.
Recently Resolved Incidents
We are investigating an issue affecting Nylas authentication.
Users may experience an error message "Unknown error" when attempting to reset email/calendar integration permissions. Start time: 10:10 am PT Next update: 1:00 pm PT or sooner.
Lever Outage Survival Guide
Lever Components
Global Data Center - LeverTRM
Career Site
Visual Insights
Integration API & Webhooks
Hire
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.
Lever Global Data Center - Advanced Analytics
Lever Talent Intelligence
Data Warehouse Sync
EU Data Center - LeverTRM
Career Site
Visual Insights
Integration API & Webhooks
Hire
Lever EU Data Center - Advanced Analytics
Lever Talent Intelligence
Data Warehouse Sync
Lever Third-Party Workflow Dependencies
Microsoft Office 365 Email/Calendar Integration
G Suite Email/Calendar Integration
Microsoft Exchange (Nylas) Email/Calendar Integration
We are investigating an issue affecting Nylas authentication.
Users may experience an error message "Unknown error" when attempting to reset email/calendar integration permissions. Start time: 10:10 am PT Next update: 1:00 pm PT or sooner.
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.