Lever EU 504 错误
Issues轻微事件
- resolved
在协调世界时8/25/2026日8:30左右,在协调世界时https://hire.eulever.co/上,一个预定的服务器自转导致超时性增加,一些页面负载失败,直到协调世界时9:15. 受到影响的用户会在受影响的页面负荷中注意到"504错误". 从协调世界时8/25/2026分9:15起,所有用户恢复服务. 将在7至10个工作日内公布一份完整的驻地协调员评估报告.
自动翻译自官方事件更新。
58 Lever incidents · 2024年6月 — official updates, affected components, duration and resolution details.
在协调世界时8/25/2026日8:30左右,在协调世界时https://hire.eulever.co/上,一个预定的服务器自转导致超时性增加,一些页面负载失败,直到协调世界时9:15. 受到影响的用户会在受影响的页面负荷中注意到"504错误". 从协调世界时8/25/2026分9:15起,所有用户恢复服务. 将在7至10个工作日内公布一份完整的驻地协调员评估报告.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
状况:已解决 我们的监测证实,没有与这一事件有关的进一步问题。 服务保持稳定,现在认为事件已经得到解决。 将在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.
问题: 我们正在调查一个似乎涉及整个平台的问题,其中提供信件未能发出。 客户影响 : 招聘者目前无法生成或向候选人发送电子邮件。 当前状况 : 工程正积极调查. 目前没有工作.
问题:我们发现一个整个平台的问题,其中要约信件未能发出。 客户影响:招聘者无法生成或向候选人发送电子邮件。 目前状况:眼前的问题已经得到缓解。 我们正在积极监测,以确认全面解决和稳定.
问题:我们发现一个整个平台的问题,其中要约信件未能发出。 客户影响:招聘者无法生成或向候选人发送电子邮件。 现况:已解决。 将在7-10个工作日内提供RCA.
** 事件摘要** 大约从2026年7月13日到7月14日,一些顾客间歇地无法发出要约信件,一些文档/重现预览未能生成. 虽然源文件被成功上传,但预览和提供生成所需的转换步骤失败了. 未发生数据损失。 ** 检测** 这个问题是在2026年7月14日大约10:43 AM ET发现的,这是在顾客向我们的支援队报告后发现的. 工程通过监测证实了影响,显示文件转换器服务内部的流程计数稳步增加,直至达到硬系统极限,导致后期任务失败. ** 循环原因** 事件由近期平台升级过程中引入的"流程泄露"所引发. 系统处理文档转换方式的改变意味着每次转换都启动了一个从未适当关闭的新的背景过程. 几天来,这些背景过程不断积累,直到系统达到最大容量。 一旦这个限制被击中,服务就不能再启动生成要约信件或文档预览所需的新流程. ** 决议** * ** 初次缓解:** 7月14日11:20 AM ET,工程师重启了受影响的服务舱. 这清除了所积累的背景过程,并立即恢复了客户发送提供信件和取景预览的能力. *** 永久固定设备:** 7月14日8:43 PM ET开发并部署了代码更新. 这种固定法确保所有背景过程在每次转换后都会被正确终止和清理,防止任何未来的积累. ** 预防措施** *** 代码改进:** 执行了一个强大的进程管理系统\(使用"Reaper"进程\),以确保所有背景任务在完成后自动关闭. * ** 加强监测:** 已经配置了新的自动提醒,以便在流程使用超过系统限制的50%时通知工程组. 这将使我们能够在类似资源泄漏影响客户前几天查明和解决这些泄漏。 * ** 包件处理:** 完成了一个单独的举措,以查明并重新处理任何在停用窗口期间未能生成的文档或恢复预览,以确保所有预览可供用户使用.
自动翻译自官方事件更新。
我们正在调查影响Nylas认证的问题。 用户在试图重置电子邮件/日历集成权限时可能会遇到"未知错误"的错误消息. 开始时间: 10: 10 a PT 下一次更新:下午1: 00 PT或更早.
我们正在继续调查这一问题。 下一次更新:下午3: 00 PT或更早.
我们正在继续调查这一问题。 下一次更新: 下午5: 00 PT
已采用缓解措施,服务功能正在恢复正常。 我们正在监测业绩和稳定。 下一次更新:在决议通过后.
问题描述:用户在试图发送邮件或同步其在Lever的微软邮件和日历时可能收到了"未知错误". 客户影响:受影响用户无法认证其微软电子邮件和日历集成,无法阻止给候选人的电子邮件发送和对招聘工作流程至关重要的日历同步功能. 状态:已解决——电子邮件发送和日历同步现在正常运行. 将在7-10个工作日内提供RCA.
** 事件摘要** 2026年7月13日,使用微软\(Office 365\)进行电子邮件和日历集成的客户体验了服务中断. 受影响的用户无法在Lever内部授权或重新授权他们的电子邮件和日历连接,经常遇到"未知错误"的消息. 此外,通过微软集成发送的境外电子邮件在此期间未能交付。 基于Google的电子邮件和日历服务仍然全面运作,没有受到这一事件的影响. ** 检测** 2026年7月13日,在顾客向我们的支援队报告后,在2:22 PM ET上确定了这个问题. 经调查,工程组确认失败,并启动高优先响应. 虽然基础技术到期发生在2026年7月12日,但随着用户试图在第二天刷新权限或发送出入境通信,影响变得明显. ** 循环原因** 事件由用于与微软安全通信的数字安全证书过期而出. 这种证书起到安全"密码"的作用,可以让我们的系统同步电子邮件和日历数据. 由于这是用于微软集成的共享证书,过期的客户使用Office 365而不是特定的账户。 ** 决议** 为了解决这一问题,我们的工程队产生了新的安全证书,并更新了我们环境中的一体化环境。 一旦新的证书通过该系统传播,服务就完全恢复。 修复通过内部测试核实,并于2026年7月13日由8:28 PM ET成功重新授权客户确认. 这一事件没有造成数据损失。 ** 预防措施** 为防止再次出现这一问题,我们正在作出以下改进: * ** 自动过期追踪:** 我们正在建立一个正式的跟踪程序,对所有一体化证书进行跟踪,并在到期日期之前及早自动发出催复通知。 * ** 预防性监测:** 已经配置了新的警报系统,以发现在授权失败时出现的激增,使我们的小组能够在类似问题影响客户之前查明和解决这些问题.
自动翻译自官方事件更新。
2026年7月3日,我们得知Nylas认证对Lever事件产生影响的问题(通常用于有微软交易所电子邮件/日历服务的客户)。 只有Nylas认证受到影响,没有观察到客户通过Office 365或Google服务认证的类似行为. 用户在试图重置电子邮件/日历权限时可能会遇到"500个错误"的消息,我们观察到几个意外的电子邮件环路,由于这个问题,导致候选人每10到15分钟收到一次重复的电子邮件. 根由:500s和电子邮件的故障由一个已知的bug在Node.js v24.17.0(https://github.com/nodejs/node/issues/63989)中引起. v24.17.0安全发布(CVE-2026-48931)改变了“http.Agent” 保持安全套接字处理方式,以便“Node-fatch”将“ERR STREAM PREMATURE CLOSE”(“提前关闭”) 丢入对外部提供者(Nylas/Google)的接头回复。 我们的服务部门通过18-24号节点的迁移(在06-30-2026年被侵入)来接收这个错误。 该bug在24.18.0号节点的上游固定 这个问题应在今天(7-8-2026年)的部署中加以解决。 我们将尽快提供问题状况和部署时间表的最新情况.
7/8/2026号大约下午12: 15PST/PDT已实施固定装置。 对配置有 Nylas 认证的 Lever 实例, 电子邮件和日历同步现在已充分运作 。 我们正在继续监测这项措施的有效性。 将在标准服务级别协议范围内为这一问题出版《根源分析》.
此事已决. 将在7-10个工作日内向本期发表《根源分析》.
** 事件摘要** 在2026年7月2日到2026年7月8日期间,一些客户间歇性地经历了影响电子邮件和日历服务的故障. 主要影响包括发送或同步电子邮件时出错,登录时偶尔出现"500个出错". 这些问题是由处理与第三方服务的外部连接的运行时间环境\(Node.js\)的技术倒退引起的。 对于使用特定电子邮件集成设置的子集客户来说,连接不稳定导致系统错误地将成功的电子邮件发送视为失败. 这引发了自动重试机制,在某些情况下导致"回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回回 ** 检测** 这个问题是在接获间歇性服务中断的报告后确定的。 我们的支助和工程小组对这些报告进行了彻底调查,查明了我们系统日志中连接故障的具体模式。 进一步分析证实,影响始于2026年7月2日左右,此前我们的服务基础设施进行了例行更新。 ** 循环原因** 其根源是Node.js\(24.17.0\)的特定版本的一个缺陷,这个软件环境曾经运行我们的服务. 这个版本在它如何管理用于与外部服务通信的"保持-活性"连接——可重复使用的连接上有一个缺陷. 在某些情况下,软件会在任务完成前过早地关闭这些连接,导致电子邮件发送和数据同步出错失败. ** 决议** 为了解决这个问题,我们的工程队采取了以下步骤: * ** 身份识别:** 与节点.js运行时间中已知的回归相连接的"提前关闭"错误. * ** 升级:** 将我们的基础系统图像更新到Node.js24.18.0版本,其中包含了这个连接问题的官方固定. * ** 部署:** 在更正的版本上重建并重新部署关键服务\(包括电子邮件和日历组件\)。 * ** 核查:** 确认连接错误已停止,服务稳定性于2026年7月8日恢复到正常水平. ** 预防措施** 为了防止今后出现类似问题,我们正在作出以下改进: *** 维相平线:** 我们更新了我们的建设进程,以确保我们只部署经过充分核实的版本。 * ** 加强监测:** 我们正在增加针对出入口连接错误的具体警报,以更快地发现和应对类似的通信故障. * ** 自动测试:** 我们正在对电子邮件和日历同步进行新的综合检查,以便在问题影响客户之前主动查明问题。 * ** 提高可见度:** 我们正在更新我们的内部仪表板,以便在我们生产环境中运行的确切软件版本中提供更好的能见度,以加快未来的诊断.
自动翻译自官方事件更新。
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.