- Level
- confirmed
- Worst impact
- Major outage
- Components
- Sandbox
- Down Index
- 40of 100
What to do
Check whether you use Lever Sandbox. 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 42m it lasted.
Anything that failed between 2025-12-03 13:50 UTC and 2025-12-03 14:31 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 3
- investigating
We’ve identified a potential issue affecting Sandbox environment accessibility, and our team is currently investigating. We’ll share additional updates as soon as more information becomes available.
provider
- monitoring
A fix has been implemented for the issue causing Lever's Sandbox environment to be down. Customers should now be able to log in to sandbox environments. We’re currently monitoring to ensure that there are no further issues, and we’ll send a final update to confirm that there have been no recurrences.
provider
- resolved
The issue causing Lever's Sandbox environment to go down has been resolved.
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-b594ea34a7
Is Lever still down?
No, this incident was resolved 2025-12-03 14:31 UTC. For Lever's live state, see https://down.guide/lever.
How long did it last?
42m, from 2025-12-03 13:50 UTC to 2025-12-03 14:31 UTC, by the times Lever posted.
What was affected?
Lever named Sandbox.
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.