Lever

All Systems Operational

About This Site

Lever eliminates the burden of manual work in the hiring process, freeing up teams to get back to the real work of recruiting. With Lever, fragmented communication and data are a thing of the past. Recruiters, hiring managers, interviewers, and leadership have a source of truth for all hiring activity. And with Lever's real-time reports, teams can easily target where to double-down on hiring efforts.

Global Data Center - LeverTRM Operational
90 days ago
99.98 % uptime
Today
Career Site Operational
90 days ago
100.0 % uptime
Today
Visual Insights Operational
90 days ago
100.0 % uptime
Today
Integration API & Webhooks Operational
90 days ago
100.0 % uptime
Today
Hire Operational
90 days ago
99.95 % uptime
Today
Global Data Center - Advanced Analytics Operational
90 days ago
100.0 % uptime
Today
Lever Talent Intelligence Operational
90 days ago
100.0 % uptime
Today
Data Warehouse Sync Operational
90 days ago
100.0 % uptime
Today
EU Data Center - LeverTRM Operational
90 days ago
99.99 % uptime
Today
Career Site Operational
90 days ago
100.0 % uptime
Today
Visual Insights Operational
90 days ago
100.0 % uptime
Today
Integration API & Webhooks Operational
90 days ago
99.96 % uptime
Today
Hire Operational
90 days ago
100.0 % uptime
Today
EU Data Center - Advanced Analytics Operational
90 days ago
100.0 % uptime
Today
Lever Talent Intelligence Operational
Data Warehouse Sync Operational
90 days ago
100.0 % uptime
Today
Third-Party Workflow Dependencies Operational
Microsoft Office 365 Email/Calendar Integration Operational
G Suite Email/Calendar Integration Operational
Microsoft Exchange (Nylas) Email/Calendar Integration Operational
Slack Operational
LinkedIn RSC/Easy Apply Operational
Zoom Operational
Google Analytics Operational
Google Hangouts Operational
Third-Party Infrastructure Dependencies Operational
Amazon Web Services Operational
Partner Ecosystem Operational
Assessments Operational
Background Check Operational
Communication & eSignature Operational
Diversity & Inclusion Operational
Hiring & Onboarding Operational
HRIS Operational
Job Boards Operational
Scheduling Operational
Sourcing & Referrals Operational
Sandbox Operational
Lever.co Operational
Contact Support Operational
Lever.co website Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jul 10, 2026

No incidents reported today.

Jul 9, 2026
Postmortem - Read details
Jul 9, 13:43 PDT
Resolved - This incident is resolved. A Root Cause Analysis (RCA) will be published to this issue within 7-10 business days.
Jul 9, 09:19 PDT
Monitoring - 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.

Jul 8, 13:03 PDT
Identified - 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.

Jul 8, 10:17 PDT
Jul 8, 2026
Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026

No incidents reported.

Jul 1, 2026

No incidents reported.

Jun 30, 2026

No incidents reported.

Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.