Skip to main content
Lever

Service Disruption Due to Cloudflare Outage

Degraded Lasted 3h 37m · started · Lever's page

Level
confirmed
Worst impact
Degraded
Components
Hire
Regions
us
Down Index
24of 100

What to do

  • Check whether you use Lever Hire in us. 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 3h 37m it lasted.

    Anything that failed between 2026-06-22 14:44 UTC and 2026-06-22 18:21 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

  1. investigating

    We are currently investigating an issue impacting access to our platforms. A broader Cloudflare service disruption is affecting connectivity, resulting in: Request timeouts Increased latency and slow page loads Cloudflare-generated error pages (including 5xx errors) Intermittent access to platform services Our teams are actively monitoring the situation and assessing the impact on our services. While the issue appears to originate from Cloudflare's infrastructure, we continue to monitor service health and will provide updates as additional information becomes available. Customers can monitor Cloudflare's incident status directly at: https://www.cloudflarestatus.com/ Start Time: ~9:35 EDT We apologize for the inconvenience and appreciate your patience while service providers work to restore normal operations. Customer Impact: Users may experience intermittent access issues, delayed responses, request failures, or Cloudflare error pages when accessing platform services. Reference: Cloudflare Status Page — https://www.cloudflarestatus.com/

    provider

  2. identified

    Monitoring Third-Party Network Issue Status: We continue to monitor an ongoing third-party network incident affecting Cloudflare, which is causing intermittent timeouts, increased latency, and occasional Cloudflare error pages for some users accessing our platforms. Based on updates from Cloudflare, the issue is related to a network infrastructure event in North America, and their engineering teams are actively rerouting traffic and implementing mitigation measures to restore service stability. At this time, the underlying issue resides with a third-party provider and is outside of our direct control. Our teams are closely monitoring the situation and validating service availability as Cloudflare implements corrective actions. Customers may continue to experience intermittent connectivity issues, slow response times, or timeout errors until Cloudflare has fully resolved the incident. For the latest updates, please monitor Cloudflare's status page directly: https://www.cloudflarestatus.com/ We appreciate your patience and will continue to provide updates as new information becomes available.

    provider

  3. resolved

    Cloudflare has reported that its traffic engineering efforts have successfully mitigated the majority of congestion and packet loss associated with this incident. As a result, service conditions are improving; however, some users may still experience intermittent connectivity issues while their recovery efforts continue. Customer Impact: Most services have stabilized, but some users may continue to experience intermittent latency, timeouts, or connectivity issues during the final stages of recovery. Customers can monitor the latest updates directly on Cloudflare's status page: https://www.cloudflarestatus.com/ We will continue to provide updates as new information becomes available.

    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-ae8ba3f258

Is Lever still down?

No, this incident was resolved 2026-06-22 18:21 UTC. For Lever's live state, see https://down.guide/lever.

How long did it last?

3h 37m, from 2026-06-22 14:44 UTC to 2026-06-22 18:21 UTC, by the times Lever posted.

What was affected?

Lever named Hire in us.

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.