Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Lever

Nylas Authenticaiton Issue - 500 Error and Email/Calendar Sync Failures

Resolved Major
July 08, 2026 - Started 13 days ago - Lasted about 23 hours
Official incident page

Incident Report

Summary AI Generated

Lever experienced a Nylas authentication failure affecting customers using on-premise Microsoft Exchange email/calendar services, causing 500 errors when resetting permissions and triggering email loops that sent candidates duplicate emails every 10–15 minutes. The issue stemmed from a bug in Node.js v24.17.0 introduced during a Node 18→24 migration on June 30, which broke socket handling and caused premature connection failures with Nylas. A fix was deployed on July 8, 2026, restoring full email and calendar sync functionality, with the incident fully resolved the following day.

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.

Trusted by 1,000+ teams

The Status Page Aggregator with Early Outage Detection

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED 12 days ago - at 07/09/2026 04:19PM

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

MONITORING 13 days ago - at 07/08/2026 08:03PM

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.

IDENTIFIED 13 days ago - at 07/08/2026 05:17PM

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.

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook