- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 30of 100
What to do
Check whether your product depends on Lever. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-03-26 22:00 UTC and 2026-03-26 22:00 UTC may need a replay.Subscribe to Lever's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=lever works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Lever 1
- resolved
At about 3:00pm PST on 3/26/2026 the Lever Support Team triggered a data operation job through an internal admin interface. The data required for this job did not have sufficient database indexes available on the server which caused significant strain on the database servers. The result of this caused site degradation and failed page loads for hire.lever.co between 3:04pm - 3:26pm PST. Impacted users would notice a "500 error" during the affected page loads. Service was restored to all users as of 3:26pm PST. Following this time we continued to optimize the databases for the intended data operation. Full functionality was reached at about 10:00pm PST.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8c70dfaec8
Is Lever still down?
No, this incident was resolved 2026-03-26 22:00 UTC. For Lever's live state, see https://down.guide/lever.
How long did it last?
0m, from 2026-03-26 22:00 UTC to 2026-03-26 22:00 UTC, by the times Lever posted.
What caused it?
Lever hasn't published a root cause. If it does, it shows here.
Where does this come from?
Lever's official status page, https://status.lever.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.