Skip to main content
Lever logo

Is Lever Down?

No — Lever is up

Reachable from all 8 checked regions

Average response time: 605ms

Last checked · checks run every 6 hours

Official status page: https://status.lever.co

Lever uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
535ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 23 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

23-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: 100.00% uptime, 16 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 23 checks
Sep 3: 100.00% uptime, 30 checks
Sep 4: 100.00% uptime, 32 checks
Sep 5: 100.00% uptime, 32 checks
Sep 6: 100.00% uptime, 21 checks
Sep 7: 100.00% uptime, 21 checks
Sep 8: 100.00% uptime, 31 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 24 checks
Sep 13: 100.00% uptime, 23 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 23 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

lax
387ms
DNS 28ms TCP 1ms TLS 29ms TTFB 327ms
lhr
363ms
DNS 44ms TCP 1ms TLS 8ms TTFB 282ms
nrt
672ms
DNS 177ms TCP 2ms TLS 8ms TTFB 664ms
ord
347ms
DNS 46ms TCP 8ms TLS 17ms TTFB 327ms
sin
1199ms
DNS 542ms TCP 2ms TLS 12ms TTFB 936ms
sjc
353ms
DNS 58ms TCP 12ms TLS 38ms TTFB 347ms
syd
1044ms
DNS 185ms TCP 2ms TLS 12ms TTFB 837ms
yyz
475ms
DNS 150ms TCP 11ms TLS 36ms TTFB 437ms

What Lever does

Lever is an applicant tracking system and recruiting CRM used by in-house talent teams. It manages candidate pipelines, interview scheduling, offers and hiring analytics, and publishes the career site candidates apply through. It leans heavily on integrations: calendar and email through Google, Office 365 and Nylas, plus job boards, assessments, background checks and HRIS connections.

What an outage looks like

The Lever app fails to load or candidate profiles will not open. Career Site is a separate component, so public job pages can stop serving while recruiters work normally and applications quietly stop arriving. Scheduling and interview invitations break on their own when the Office 365, G Suite or Nylas email and calendar components are the ones affected.

What to do about it

Check status.lever.co and read the component. Lever reports Career Site, Hire, Integration API and Webhooks, Data Warehouse Sync and each third-party integration separately, and lists Amazon Web Services as a dependency of its own. If Career Site is affected, warn anyone paying for job adverts pointing at it. Confirm whether scheduling failures are Lever or the calendar provider before re-sending invitations.

Is it down for everyone, or just you?

If this page says Lever is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Greenhouse
Greenhouse
Ashby
Ashby
I
Indeed
Zoom
Zoom

Lever outage FAQ

Applicants cannot reach our job page, but Lever works for our recruiters.
Career Site is reported as a component separate from Hire, so the candidate-facing pages can be down while the internal application serves normally. That combination is easy to miss because nobody inside the company sees an error. If you are running paid job adverts pointing at the career site, the cost of that window is real and worth pausing.
Are interview invitations failing because of Lever or Google?
Check which component is affected. Lever separates G Suite Email and Calendar, Microsoft Office 365 Email and Calendar, and Microsoft Exchange through Nylas from its own Hire component. Calendar and email delivery flow through those integrations, so an incident there breaks scheduling while Lever itself is healthy, and it clears when the provider recovers.
Does a Lever outage stop our webhooks and API integrations?
Integration API and Webhooks is its own component, so it can fail while the Hire interface works, or keep working through an interface incident. Lever does not publish webhook retry behaviour on its status page, so treat deliveries attempted during an incident as uncertain and reconcile against Lever once the component recovers.
Will our data warehouse sync catch up after an outage?
Data Warehouse Sync is reported as its own component, but Lever does not publish whether a missed sync backfills automatically. Assume nothing: after the component recovers, compare row counts or recent record timestamps in your warehouse against Lever before running reporting that depends on the affected window.
Is Lever down, or is it just my session?
Lever's status page reports components rather than individual accounts, so start by matching your symptom to Career Site, Hire, Visual Insights or one of the integrations. If every component reads operational, look at your browser session, SSO provider or network. Lever also lists Amazon Web Services separately, so check that row before ruling out an upstream cause.

How we measure this

  • We request Lever's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Lever publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Lever goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required