Skip to main content
Lever logo

Is Lever Down?

No — Lever is up
Lever's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 639 ms

Right now

The verdict is the worse of these two. How we decide

Lever's status page

status.lever.co · read · checked every 3 minutes

Operational
Lever's components, as its status page reports them
ComponentStatus
AssessmentsOperational
Background CheckOperational
Communication & eSignatureOperational
Diversity & InclusionOperational
Hiring & OnboardingOperational
HRISOperational
Job BoardsOperational
SchedulingOperational
Sourcing & ReferralsOperational
Microsoft Office 365 Email/Calendar IntegrationOperational
G Suite Email/Calendar IntegrationOperational
Microsoft Exchange (Nylas) Email/Calendar IntegrationOperational
9 more, all operational · show all 21
All of Lever's components
ComponentStatus
Partner Ecosystem
AssessmentsOperational
Background CheckOperational
Communication & eSignatureOperational
Diversity & InclusionOperational
Hiring & OnboardingOperational
HRISOperational
Job BoardsOperational
SchedulingOperational
Sourcing & ReferralsOperational
Third-Party Workflow Dependencies
Microsoft Office 365 Email/Calendar IntegrationOperational
G Suite Email/Calendar IntegrationOperational
Microsoft Exchange (Nylas) Email/Calendar IntegrationOperational
SlackOperational
LinkedIn RSC/Easy ApplyOperational
ZoomOperational
Google AnalyticsOperational
Google HangoutsOperational
Third-Party Infrastructure Dependencies
Amazon Web ServicesOperational
Lever.co
Contact SupportOperational
Lever.co websiteOperational
SandboxOperational
12 locations All operational

FlareWarden checks

lever.co from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
639 ms
Checked

By region

  • Ashburn reachable, 313 ms
  • Dallas reachable, 394 ms
  • Frankfurt reachable, 612 ms
  • Johannesburg reachable, 1587 ms
  • Newark reachable, 356 ms
  • Paris reachable, 389 ms
  • Stockholm reachable, 724 ms
  • São Paulo reachable, 737 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn58 ms1 ms9 ms305 ms
Dallas161 ms1 ms53 ms369 ms
Frankfurt78 ms2 ms9 ms507 ms
Johannesburg268 ms1 ms45 ms1323 ms
Newark166 ms2 ms23 ms348 ms
Paris44 ms10 ms17 ms297 ms
Stockholm76 ms20 ms21 ms610 ms
São Paulo58 ms1 ms8 ms507 ms
We check that lever.co loads, not every feature behind it. Test it yourself

History

Incidents Lever reported

Since Oct 22, 15 days · from status.lever.co

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Lever website availability

Measured by FlareWarden · lever.co

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

Last 30 days

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

Measured by FlareWarden's own checks of lever.co from multiple regions every 6 hours. Lever's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 69 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Lever itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Lever goes down

We check Lever every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required