58 Lever incidents · 2024년 6월 — official updates, affected components, duration and resolution details.
오전 8시 30분에 UTC는 오전 8시 25분에서 예정된 서버 교체에 대한 https://hire.eulever.co/는 늦게 증가했으며, 오후 9시 15분까지 실패한 페이지로드가 실패했습니다. 영향 받은 사용자는 영향을 받은 페이지로드 중 "504 오류"를 알 수 있습니다. 서비스는 모든 사용자에게 8/25/2026의 9:15am UTC로 복원되었습니다. 전체 RCA는 7 ~ 10 영업일 이내에이 문제에 게시됩니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리는 현재이 문제를 조사하고 있습니다.
수정이 구현되어 결과를 모니터링하고 있습니다.
상태: 해결 우리의 모니터링은이 사건과 관련된 더 이상 문제가 없다는 것을 확인했습니다. 서비스는 안정적으로 유지되고, 사건은 이제 해결되었습니다. 뿌리 원인 분석 (RCA)는 7-10 영업일 이내에 제공됩니다.
공식 인시던트 업데이트를 자동 번역했습니다.
At about 10:31am PST on 8/12/2026 Lever Support initiated a backend data query that caused Lever hire services to encounter an out of memory error. The result of this caused site degradation and failed page loads for hire.lever.co between 10:31am - 10:46am PST. Impacted users would notice a "500 error" during the affected page loads. Service was restored to all users as of 10:46am PST. At this time we are working on continued enhancements to mitigate the risk of Lever Support initiated queries triggering outages in the future. An full RCA will be posted to this issue within 7 to 10 business days.
**Incident Summary** On August 12, 2026, between approximately 10:31 AM and 10:45 AM PDT, the Lever platform experienced partial unavailability. During this 14-minute window, some customers were unable to access the platform, and others experienced elevated error rates for API requests. **Detection** The issue was identified through internal monitoring. A Datadog alert for high database page faults triggered at 10:37 AM PDT, notifying the engineering team. This allowed responders to isolate the specific database nodes experiencing high load and identify the responsible operations. **Root Cause** The incident was triggered by a safety mechanism within an internal administrative tool designed to prevent expensive database queries. When an operator searched for unindexed data, this safety check requested a "plan" from the database to see if the query was safe to run. However, because the data was unindexed, the database attempted to evaluate every possible retrieval method, resulting in the same large account being scanned 11 times for a single request. These diagnostic checks bypassed standard time limits, consuming the database read capacity required for normal customer traffic. **Resolution** Engineering teams identified and terminated the long-running diagnostic operations, which immediately restored database performance and platform stability. Following the cleanup, a database-level safeguard was applied to force these specific queries into a single, efficient path, preventing the database from attempting multiple expensive scans in the future. **Preventative Measures** * **Redesigning Safety Checks:** We are replacing the current diagnostic method with a new system that verifies query safety by inspecting database definitions directly, eliminating the need to run expensive tests on live data. * **Advanced Alerting**: We are implementing new monitoring for database read churn and long-running operations to detect and resolve similar issues before they affect customers. * **Enhanced Logging:** We are improving internal audit logs to ensure faster identification and attribution of administrative database activity. * Database Optimization: We are adding new indexes to properly support these search patterns, ensuring they are inherently efficient.
Issue: We are aware of an active outage with Adobe Sign, a third-party e-signature provider. This is affecting Lever customers who use the Adobe Sign integration. Customer Impact: Recruiters may be unable to generate or send offer letters for e-signature via Adobe Sign. Candidates with pending Adobe Sign requests may be unable to sign at this time. Customers using DocuSign and all other Lever functionality are unaffected. Status: Investigating. This is an upstream issue with Adobe; we are monitoring and will update as Adobe provides more information. For direct updates from Adobe, see their status page at https://status.adobe.com/
Update — Offer Letter Sending Disrupted Issue: We've identified that this disruption is broader than initially scoped. The Adobe outage is impacting our PDF conversion process, which all offer letters — regardless of e-signature provider (Adobe Sign, DocuSign, or Native eSignature) — depend on to generate the final document. Customer Impact: All customers are currently unable to send offer letters successfully. This is no longer limited to Adobe Sign integration users. Recruiters attempting to generate or send an offer letter may see failures or delays regardless of which e-signature method is configured on their account. Status: Investigating.
We found that our Fallback document converter in case of an Adobe PDF Services API outage is not working as expected. We are working on a fix to implement an immediate fallback document converter to prevent failed/stuck offer sends in cases of an Adobe PDF Services API outage. Next update: 4pm PST/PDT or earlier For the most up to date status on the Adobe API outage follow: https://status.adobe.com/products/503500/202608070024
A fix has been implement to immediately fallback to an alternate document converter after offer document conversions are stuck for a period of time. We are currently processing through a backlog of offer sends and we expect the backlog processing to take around one to two hours. Users may notice a delay sending offers, but offer documents should send successfully. Any document (resumes, offers, etc.) image previews may show loading failures while the backlog processing catches up to real time. We are continuing to actively monitor the document previewer and Adobe PDF Services API outage.
This incident has been resolved. The document converter is now processing in real time. Offers are sending with no delay and all document previews in Lever should be visible. An RCA will be available within 7-10 business days.
**Incident Summary** On August 7, 2026, between approximately 6:00 AM and 5:30 PM ET, some customers were unable to send offer letters, and some document and resume previews failed to generate. Files uploaded successfully; only the step that converts them into a viewable PDF or preview failed. No data was lost. **Detection** Identified on August 7 at approximately 11:47 AM ET following customer reports to our Support team. **Root Cause** A third-party service we use to convert documents into PDFs experienced an outage lasting most of the day. During it, the service accepted conversion requests but never completed them. Our system is designed to switch to a backup conversion method when that service reports a failure — but because these requests neither succeeded nor failed, they simply waited, and the backup was never used. Each waiting request also occupied one of a limited number of conversion slots, so delays spread to other documents. **Resolution** We added a strict overall time limit to document conversions: if the third-party service does not finish within that window, we stop waiting and convert the document using our own backup method instead. We also corrected a related defect that had prevented the backup from being used reliably. Both fixes were released to production on the afternoon of August 7, while the third-party outage was still ongoing, and conversion success rates returned to normal levels the following day. We then re-processed the documents that had failed to convert during the outage. **Preventative Measures** · We fixed a defect that had prevented this service's health measurements from reaching our monitoring system and are adding alerts on the document conversion failure rate, so issues like this are detected automatically and quickly, rather than through customer reports. · The new time limit can be adjusted without a code release, and we are documenting a procedure to route all conversions away from the third-party service during a vendor outage.
문제: 우리는 편지가 보내질 때까지 플랫폼 전체 문제로 나타나는 것을 조사하고 있습니다. 고객 충격: 채용자는 현재 후보자에게 제안 이메일을 생성하거나 제공 할 수 없습니다. 현재 상태: 공학은 적극적인 조사입니다. 이 시간에 workaround는 유효하지 않습니다.
문제: 우리는 편지를 보내지 못하는 플랫폼 넓은 문제점을 확인했습니다. 고객 영향: 채용자는 후보자에게 제안 이메일을 생성하거나 전달할 수 없습니다. 현재 상태: 즉각적인 문제는 mitigated. 우리는 적극적으로 풀 해상도와 안정성을 확인하는 모니터링.
문제: 우리는 편지를 보내지 못하는 플랫폼 넓은 문제점을 확인했습니다. 고객 영향: 채용자는 후보자에게 제안 이메일을 생성하거나 전달할 수 없습니다. 상태: 해결. RCA는 7-10 영업일 이내에 사용할 수 있습니다.
**정보** 약 7 월 13 일과 7 월 14 일 사이에, 일부 고객은 간헐적으로 제공 편지를 보낼 수 없으며 일부 문서 / 이력서 미리보기가 생성되지 않았습니다. 소스 파일이 성공적으로 업로드 된 동안, 미리보기에 필요한 변환 단계 및 생성 실패를 제공합니다. 데이터 손실이 발생하지 않습니다. **멸종 ** 문제는 7 월 14, 2026에 확인되었다, 약 10 : 43 AM ET, 우리의 지원 팀에 고객에게 다음과 같은 보고서. 엔지니어링은 하드 시스템 제한에 도달 할 때까지 문서 변환기 서비스 내에서 프로세스 카운트의 꾸준한 증가를 보여주기 위해 모니터링을 통해 영향을 확인, 후속 작업을 실패. ** 루트 원인 ** 사건은 최근 플랫폼 업그레이드 중 도입 된 "공정 누출"에 의해 발생했습니다. 시스템이 문서 변환을 처리하는 방법에 대한 변경은 각 변환이 제대로 닫히지 않은 새로운 배경 프로세스를 시작했습니다. 몇몇 일 이상, 이 배경은 체계가 그것의 최대 수용량에 도달될 때까지 축적했습니다. 이 제한이 히트되면 서비스는 더 이상 제공 문자 또는 문서 미리보기를 생성 할 필요가있는 새로운 프로세스를 시작할 수 없습니다. ** 해결책 ** * **Initial 소송:** 7 월 14 일 오전 11시 20 분에 엔지니어가 영향을받은 서비스 팟을 재시작했습니다. 이것은 축적 된 배경 프로세스를 정리하고 즉시 고객에게 제공 편지를 보내고 미리보기를 볼 수있는 능력을 복원했습니다. * ** 영구 수정 : ** 코드 업데이트는 7월 14일 오후 8시 43분에서 개발 및 배포되었습니다. 이 수정은 모든 배경 프로세스가 올바르게 종결되고 모든 변환 후 정리되어 미래의 축적을 방지합니다. ** 사전 측정 ** ***Code 개선:** 견고한 공정 관리 시스템 \ ( "reaper" Process\)를 구현하여 모든 배경 작업을 자동으로 완료합니다. * ** 감시: ** 새로운 자동화된 경고는 프로세스 사용이 시스템 제한의 50%를 초과하면 엔지니어링 팀을 통지하도록 구성되었습니다. 이것은 고객에게 영향을 미치는 전에 유사한 자원 누출 일을 식별하고 해결 할 수 있습니다. ***Backlog 처리:** 별도의 이니셔티브는 모든 문서 또는 이력서 미리보기를 식별하고 재처리 할 수 있도록 완료되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
Nylas 인증에 영향을 미치는 문제점을 조사하고 있습니다. 사용자는 이메일 / 달력 통합 권한을 재설정 할 때 오류 메시지 "Unknown error"를 경험할 수 있습니다. 시작 시간: 10:10 오전 PT 다음 업데이트: 오후 1시 PT 또는 빨리.
이 문제를 조사하고 있습니다. 다음 업데이트: 오후 3시 PT 또는 빨리.
이 문제를 조사하고 있습니다. 다음 업데이트: 오후 5시 PT
청구 단계는 적용되고 서비스 기능은 정상에 돌려보내집니다. 우리는 성과와 안정성을 감시하고 있습니다. 다음 업데이트: 해상도.
문제점 묘사: 사용자는 이메일 또는 레버에 있는 그들의 Microsoft 이메일 및 달력을 동기화하는 시도할 때 "Unknown error"를 받을지도 모릅니다. 고객 영향: Affected 사용자는 Microsoft 이메일 및 캘린더 통합을 인증할 수 없으며 이메일 차단은 채용 워크플로우에 중요한 후보와 캘린더 동기화 기능으로 보냅니다. Status: Resolved — Email sends and Calendar sync는 이제 정상적으로 작동하고 있습니다. RCA는 7-10 영업일 이내에 사용할 수 있습니다.
**정보** 7월 13, 2026일, 이메일 및 캘린더 통합 경험있는 서비스 중단을 위해 Microsoft \(Office 365\)를 사용하는 고객. 익명의 사용자들은 사용자의 이메일과 달력 연결을 승인하거나 재 승인할 수 없었으며 종종 "Unknown error" 메시지가 발생했습니다. 또한 Microsoft 통합을 통해 전송 된 아웃 바운드 이메일은이 기간 동안 전달하지 못했습니다. Google 기반 이메일 및 캘린더 서비스는 완전히 운영되고이 사건에 영향을 미치지 않았습니다. **멸종 ** 문제는 7 월 13, 2026, 2 : 22 PM ET에서 고객 지원 팀에 대한 보고서를 다음과 같이 확인되었습니다. 조사에, 기술설계 팀은 실패를 확인하고 높 순수성 응답을 개시했습니다. 기술 만료가 7 월 12, 2026에 발생했지만, 영향은 사용자가 권한을 새로 고침하거나 아웃바운드 통신을 다음 날 보내려고 시도 한 것으로 볼 수 있습니다. ** 루트 원인 ** 사건은 Microsoft와 안전하게 통신하는 데 사용되는 디지털 보안 자격 증명의 만료에 의해 발생했습니다. 이 자격은 안전한 "password"로 작동하며, 시스템은 이메일과 캘린더 데이터를 동기화 할 수 있습니다. 이것은 Microsoft 통합에 사용되는 공유 자격이었기 때문에, 특정 계정보다 Office 365를 사용하여 Expiration 영향을받는 고객. ** 해결책 ** 문제를 해결하기 위해, 우리의 엔지니어링 팀은 새로운 보안 자격 증명을 생성하고 우리의 환경 전체에 통합 설정을 업데이트했습니다. 시스템을 통해 새로운 자격 증명을 한 번, 서비스는 완전히 복원되었습니다. 복원은 내부 테스트를 통해 확인되었으며 7 월 13, 2026에 8 : 28 PM ET의 성공적인 고객 재 승인에 의해 확인되었습니다. 이 사건의 결과로 데이터 손실이 발생하지 않았습니다. ** 사전 측정 ** 이 문제의 재발을 방지하기 위해 다음과 같은 개선을 구현하고 있습니다. * ** 자동화 된 만기 추적 : ** 자동화된 알림으로 모든 통합 자격 증명을 위한 공식 추적 프로세스를 구축하고 있습니다. * **비활성 모니터링:** 새로운 경고는 허가 실패에 스파이크를 감지하기 위해 구성되었습니다, 우리의 팀은 고객에게 영향을 미치는 전에 유사한 문제를 식별하고 해결 할 수 있습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
7-3-2026에서 우리는 Nylas 인증 (즉시 Microsoft Exchange 이메일 / 달력 서비스로 고객에게 사용) 레버 인스턴스에 영향을 미치는 문제의 인식을했다. Nylas 인증은 영향을 받으며 Office 365 또는 Google 서비스로 인증된 고객에게는 유사한 행동이 없습니다. 사용자는 이메일 / 달력 권한을 재설정하려고 시도 할 때 "500 오류"메시지를 경험할 수 있으며 후보자가이 문제의 결과로 10 ~ 15 분마다 중복 이메일을받을 수있는 여러 예기치 않은 이메일 루프를 관찰했습니다. 루트 원인: 500s 및 이메일 실패는 Node.js v24.17.0 (https://github.com/nodejs/node/issues/63989)의 알려진 버그에 의해 발생합니다. v24.17.0 보안 릴리즈 (CVE-2026-48931)는 `http.Agent`는 `node-fetch`가 `ERR STREAM PREMATURE CLOSE`("Premature close")가 외부 공급자(Nylas/Google)에 대한 즈음 응답에 대한 즈음향을 변경했습니다. 우리의 서비스는 Node 18→24 마이그레이션을 통해이 버그를 차지했습니다 (06-30-2026). 버그는 Node 24.18.0의 고정 업스트림이었습니다. 이 문제는 오늘 배포에 고정되어야한다 (7-8-2026). 우리는 가능한 한 빨리 문제 상태 및 배포 타임 라인에 업데이트를 제공 할 것입니다.
수정은 약 12:15pm PST/PDT로 구현되었습니다. 이메일 및 캘린더 동기화는 이제 Nylas 인증으로 구성된 레버 인스턴스에 대한 완벽한 기능입니다. 우리는 해결의 효과를 모니터링하고 있습니다. 루트 원인 분석 (RCA)은 표준 서비스 수준 계약 내에서이 문제에 게시됩니다.
이 사건은 해결됩니다. 루트 원인 분석 (RCA)은 7-10 영업일 이내에이 문제에 게시됩니다.
**정보** 7 월 2, 2026 및 7 월 8, 2026 사이, 일부 고객은 이메일 및 달력 서비스에 영향을 미치는 간헐적 인 실패를 경험했습니다. 로그인 중에 이메일 및 가끔 "500 오류"를 전송하거나 동기화 할 때 기본 영향이 포함된 오류. 이 문제는 제3자 서비스에 대한 아웃바운드 연결을 처리하는 언바운드 환경 \(Node.js\)의 기술 회귀에 의해 발생했습니다. 특정 이메일 통합 설정을 사용하여 고객의 subset을 위해, 연결 불안정은 실패로 성공적인 이메일 전송을 incorrectly에 시스템 발생. 이것은 연결이 안정화 될 때까지 정기적 인 간격으로 수신자에 의존하는 "retry Loop"에서 발생 한 일부 경우에 자동화 된 복원 메커니즘을 트리밍했습니다. **멸종 ** 문제는 intermittent 서비스 중단의 보고서에 따라 식별되었습니다. 우리의 지원 및 엔지니어링 팀은 이러한 보고서에 철저한 조사를 수행했으며, 시스템 로그 내의 연결 실패의 특정 패턴을 식별합니다. 더 많은 분석은 영향이 약 7 월 2, 2026에서 시작되었는지 확인했습니다. 우리의 서비스 인프라에 대한 일상적인 업데이트. ** 루트 원인 ** 루트 원인은 Node.js \ (version 24.17.0\)의 특정 버전의 결함이 있었으며, 우리의 서비스를 실행하는 데 사용되는 소프트웨어 환경. 이 버전에는 "keep-alive"연결을 관리하는 방법에 대한 결함이 포함되어있어 외부 서비스와 통신하는 데 사용됩니다. 특정 조건 하에서, 소프트웨어는 작업을 완료하기 전에이 연결을 조기에 닫을 것, 실패 이메일 전송 및 데이터 동기화 오류 발생. ** 해결책 ** 문제점을 해결하기 위해, 우리의 기술설계 팀은 뒤에 오는 단계를 실행했습니다: * **Identification:** Node.js runtime에서 알려진 회귀에 "Premature close" 오류와 관련이 있습니다. * ** 업그레이드:** Node.js 버전 24.18.0에 기본 시스템 이미지를 업데이트하면 이 연결 문제의 공식 수정이 포함됩니다. ***Deployment:** 수정된 버전의 Rebuilt 및 redeployed Critical services \(이메일 및 캘린더 구성 요소 포함). * ** 인증:** 연결 오류가 중단되고 서비스 안정성이 7 월 8, 2026에서 정상 수준으로 반환됨. ** 사전 측정 ** 미래에 유사한 문제를 방지하기 위해 다음과 같은 개선을 구현하고 있습니다. ***Version Pinning:** 우리는 우리가 완전히 확인 된 버전 만 배포되도록 빌드 프로세스를 업데이트했습니다. * ** 감시: ** 우리는 아웃바운드 연결 오류에 대한 특정 경고를 추가하고 비슷한 통신 실패에 응답 더 빠르게. * **자동 테스트:** 우리는 이메일 및 달력 동기화에 대한 새로운 합성 검사를 구현하여 고객에게 영향을 미치는 전 문제를 신속하게 식별합니다. * ** 개선된 가시성: ** 우리는 우리의 생산 환경에서 실행 정확한 소프트웨어 버전으로 더 나은 가시성을 제공하기 위해 내부 대시보드를 업데이트하여 미래의 진단을 가속화합니다.
공식 인시던트 업데이트를 자동 번역했습니다.
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/
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.
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.
We became aware of an issue affecting the North America data center where Visual Insights is not loading new data in some customer accounts. The issue started occurring on Tuesday, 6/16/2026 at approximately 7:30am PST/PDT. Updates will be provided as we work to investigate the issue.
We are continuing to investigate this issue affecting Visual Insights. New data may be delayed to appear in Visual Insights or may be missing. Start time: 6/16/2026 7:30am PST/PDT Next update: 6/17/2026 8am PST/PDT or sooner.
We have identified the issue affecting the Visual Insights (Snowflake) database and have implemented a fix on Wednesday, June 17 at approximately 10:30am PST/PDT.
We are continuing to monitor the effectiveness of the fix for Visual Insights reporting. We anticipate that reporting data may still have discrepancies for approximately 10 to 15 hours. We are continuing to monitor that data is backfilling on schedule as expected. Next update: 6/17/2026 5pm PST/PDT or sooner.
The data backfill has completed at approximately 5:00am PST/PDT on 6/18/2026. All Visual Insights reports should now be a complete and accurate representation of current data. A root cause analysis (RCA) will be published to this incident within the standard Service Level Agreement (SLA).
#### **Incident Summary** Between June 14 and June 18, 2026, analytics reports in the Visual Insights "Custom Data Explorer" displayed outdated information. While the live platform remained fully accurate and no data was lost, the reports stopped reflecting real-time changes \(such as candidate stage updates\). This resulted in a "stale" snapshot of data being shown to all reporting customers for approximately four days. **Detection** The issue was identified on June 17, 2026, following reports from customers who noticed that their report counts did not match the live data in the platform. Upon investigation, our engineering team confirmed that the data pipeline responsible for updating these reports had stopped processing new information on June 14. #### **Resolution** Once identified, our engineering team restarted the affected component, which safely resumed and caught up on all pending changes with no data loss. Report accuracy was fully restored, and the cited figures now match the live platform. No action was required from customers at any point. #### **Preventative Measures** To prevent this issue from recurring, we have taken the following actions: * **Enhanced Auto-Recovery:** We updated the system to automatically recognize and recover from this specific type of database restart error, allowing it to self-heal without manual intervention. * **Improved Monitoring:** We are implementing more granular alerts that monitor the specific workers within the data pipeline. This ensures that if a single worker stops, we are notified within minutes. * **Data Freshness Checks:** We are adding new automated checks that compare live platform data against the reporting store to detect any "freshness" gaps immediately.
We are investigating an issue affecting the LinkedIn Job Board integration. Users may experience inaccurate posting locations appearing in LinkedIn when passing postings via the LinkedIn Job Board integration, we do not currently have any reports of inaccuracies from the LinkedIn Apply Connect integration. Start time: 9:00 AM Pacific 6/11/2026 Next update: 12:30 PM 6/11/2026 or sooner.
We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 2:30 PM Pacific 6/11/2026 or sooner
We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 4:30 PM Pacific 6/11/2026 or sooner
We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 9:30 AM Pacific 6/12/2026 or sooner
We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 11:30 AM Pacific 6/12/2026 or sooner
We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 1:30 PM Pacific 6/12/2026 or sooner
Posting Locations should now be populating as expected. Please follow up with Lever Support if you see any postings continuing to display an inaccurate location in LinkedIn.
We are investigating an issue affecting some users Microsoft Office 365 email/calendar services are unable to schedule interview events or send emails in Lever. The impact appears to be limited to only accounts where Administrator Consent for email/calendar permissions is enabled. Affected users are currently unable to schedule interviews or send emails in Lever and may see one or more error messages including “Could not load events” and/or “Your email/calendar integration isn't working” related to scheduling and email. We are currently investigating this issue and will provide updates from our Engineering team as new information becomes available. Users may experience issues when scheduling interviews or sending emails. Start time: April 21, 2026, 1:40 PM PDT
This incident has been resolved. Incident Duration: April 21, 2026, 1:40 PM– April 23, 2026 11:00 AM PT Impact Summary: During this window, customers using Microsoft Office365 were unable to retrieve interviewer availability or schedule interviews. Existing data was not lost, but new scheduling actions failed until service was restored. Cause: An internal encryption key rotation was completed for several services, but a related dependency used by the calendar service was not updated. As a result, the calendar service was unable to read newly issued Microsoft access tokens, causing scheduling requests to fail for Office365-connected accounts. Mitigation: The calendar service was updated to use the correct dependency compatible with the new encryption keys. Once deployed, scheduling functionality was fully restored and verified in production. An RCA will be provided within 7-10 business days if applicable.
Around 8:50am PT on 4/21/2026 we became aware of an issue where some users Microsoft Office 365 email/calendar services are unable to schedule interview events or send emails in Lever. The impact appears to be limited to only accounts where Administrator Consent for email/calendar permissions is enabled. Affected users are currently unable to schedule interviews or send emails in Lever and may see one or more error messages including “Could not load events” and/or “Your email/calendar integration isn't working” related to scheduling and email. We are currently investigating this issue and will provide updates from our Engineering team as new information becomes available.
We are continuing to investigate this issue.
We have identified the issue causing failed Lever user permission syncs with Microsoft Office 365 email/calendar services for users with Administrator provided email/calendar permissions. A fix was deployed at approx. 4:39pm PT on 4/21/2026. We are actively monitoring the fix to ensure continued email/calendar sync availability.
This incident has been resolved. Issue: Users with Microsoft 365 calendar integrations experienced authentication failures, causing email and calendar sync to stop working. Resetting the calendar cache resulted in an endless loading state. Impact: Affected users were unable to schedule interviews or view availability in Lever. The issue was limited to accounts using Admin Consent–based Microsoft 365 authentication. A fix was applied at approximately 4:39 pm PDT on 4/24/2026. An RCA will be available within 7-10 business days if applicable.
We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again. **Date/Time:** April 21, 2026, **1:40 PM – 4:39 PM PDT** **Duration:** **2 hours 59 minutes** ### Customer Impact During this window, customers using Microsoft Office365 were unable to retrieve interviewer availability or schedule interviews. Existing data was not lost, but new scheduling actions failed until service was restored. ### Root Cause An internal encryption key rotation was completed for several services, but a related dependency used by the calendar service was not updated. As a result, the calendar service was unable to read newly issued Microsoft access tokens, causing scheduling requests to fail for Office365-connected accounts. ### Resolution The calendar service was updated to use the correct dependency compatible with the new encryption keys. Once deployed, scheduling functionality was fully restored and verified in production. ### Preventative Actions * Expand automated test coverage to explicitly validate scheduling flows for Microsoft Office365 accounts. * Improve internal validation and service dependency checks during encryption key rotations.
We are currently investigating an issue preventing new API keys from being generated in our EU environment (EUDC). Impact: Existing or pre-existing API connections in the EU region may also be impacted. Global (non-EU) environments remain unaffected at this time. Updates to follow shortly
This incident has been resolved. Impact Summary: Customers may have had an issue preventing new API keys from being generated in our EU environment (EUDC). Existing or pre-existing API connections in the EU region may also be impacted. Global (non-EU) environments were unaffected An RCA will be provided within 7-10 business days if applicable.
We are currently investigating this issue.
Impact: Partial outage – subset of users unable to access Lever We are investigating reports that some users receive a “Site Not Found” error when accessing hire.lever.co and related pages. This issue appears limited to a subset of customers and is related to an ongoing incident with our upstream network provider (Cloudflare): https://www.cloudflarestatus.com/ Our systems are operating normally, but connectivity for some users is being impacted by this third‑party provider. We are monitoring their incident and will provide updates as more information becomes available. There is currently no known workaround.
We are continuing to work on a fix for this issue.
Cloudflare has implemented a fix for this issue and are currently monitoring. Impact: Partial outage – a subset of users were unable to access Lever Some users may have received a “Site Not Found” error when accessing hire.lever.co and related pages. For updated info and an RCA, refer to Cloudflare's status page: https://www.cloudflarestatus.com/
This incident has been 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.
We are investigating an issue affecting the availability of reporting data. Users may experience delays in getting up-to-date reporting data, specifically related to profile cards. Start time: Approximately 4 am EST Next update: 10 am EST or sooner.
We have identified the root cause affecting the delay of data related top profile cards. Mitigation is currently in progress. Next update: 10:30 am EST or sooner.
Mitigation steps have been applied and service functionality is returning to normal and processing of delayed data should be complete within the next 2 hours. We are monitoring for continued performance and stability. Next update: 12 pm EST or upon full resolution.
We are continuing to monitor for any further issues.
This incident has been resolved. Impact Summary: Users may have experienced delays in getting up-to-date reporting data, specifically related to profile cards. Incident Duration: Started at approximately 4 am EST and resolution confirmed at 9 am EST An RCA will be provided within 7-10 business days
We’ve identified the issue causing the "enable AI Interview Companion for all postings" button to not work, and we’re working to implement a fix. Additional updates will be provided as soon as a resolution is in place.
We’ve completed a fix for the issue that caused the “Enable AI Interview Companion for all postings” button to stop working. The team is currently finishing testing, and the release is planned for Monday, March 9. Additional updates will be provided as soon as the fix is deployed. Next update: Monday, March 9 at 12:00 PM ET or earlier.
We’ve completed a fix for the issue that caused the “Enable AI Interview Companion for all postings” button to stop working. The release is expected to be deployed today. Next update: Monday, March 9, at 5:00 PM ET or earlier.
The issue with the AI Interview Companion Enable for all Jobs settings in Lever has been resolved. The incident occurred from 11:59 am PST 3/6/2026 - 10 am PST 3/9/2026. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
We are currently investigating an issue that is causing general opportunities to be created when an opportunity is archived. Issues impacting candidate archiving were noticed around February 10, 2026 at 1:00 PM PT. Our Engineering teams are actively working to resolve this as soon as possible.
We’ve identified the issue causing general opportunities to be created when an opportunity is archived, and we’re working to implement a fix. Additional updates will be provided as soon as a resolution is in place.
The issue where general opportunities were showing when archiving opportunities has been resolved. The incident occurred from February 10, 2026 at 1:00 PM PT to February 11, 2026 at 5:30 PM PT. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
We are currently investigating an issue that is intermittently affecting the API. Our Engineering teams are actively working to resolve this as soon as possible.
The issue has been identified and we are working on the fix.
A fix has been implemented, and we are monitoring the results.
The incident occurred from 3:30 am Pacific time until 5:00 am Pacific time. No further action will be required from impacted users to have restored functionality. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
