58 Lever incidents · 2024年6月 — official updates, affected components, duration and resolution details.
8/25/2026の8:30am UTCでは、https://hire.eulever.co/でスケジュールされたサーバーの回転が増加し、9:15am UTCまで失敗したページが読み込まれました。 影響を受けたユーザーは、影響を受けるページの読み込み中に「504 エラー」に気づくでしょう。 8/25/2026 に 9:15am UTC としてすべてのユーザーにサービスが復元されました。 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.
課題: 私たちは、文字が送信されず、プラットフォーム全体の問題になるように見えるものを調査しています。 顧客の影響: 採用担当者は、候補者にオファーメールを生成または配信できません。 現在の状態: エンジニアリングは積極的に調査しています。 今回は、ワークアラウンドはありません.
課題: 送信できなかった文字を提供するプラットフォーム全体の問題を特定しました。 顧客への影響: 採用担当者は、候補者にオファーメールを生成または配信できませんでした。 現在の状態: 即時の問題は緩和されています。 完全な解像度と安定性を確認するために積極的に監視しています.
課題: 送信できなかった文字を提供するプラットフォーム全体の問題を特定しました。 顧客への影響: 採用担当者は、候補者にオファーメールを生成または配信できませんでした。 状態: 解決される。 RCAは7-10営業日以内に対応いたします.
**事件要約** 2026年7月13日と7月14日の間に、一部の顧客はオファーの手紙を送らなかったため、一部の文書/再開プレビューは生成できませんでした。 ソースファイルが正常にアップロードされましたが、プレビューと生成失敗に必要な変換ステップ。 データの損失が発生しません。 **検出** 2026年7月14日(水)に、お客様から当社サポートチームへ報告するにあたり、約10:43(火)に発行されました。 エンジニアリングは、監視による影響を確認しました。これは、ハードシステム限界に達したまで、文書変換サービス内のプロセスカウントの着実な増加を示し、その後のタスクが失敗しました。 **ルート原因** 最近のプラットフォームのアップグレード中に導入された「プロセスリーク」によるインシデントが発生しました。 システムが文書変換を処理する方法の変化は、各変換が適切に閉じられなかった新しい背景プロセスを開始しました。 数日間にわたり、システムが最大容量に達するまで蓄積されたこれらの背景プロセス。 この制限がヒットしたら、サービスが提供の文字や文書のプレビューを生成するために必要な新しいプロセスを開始することはできません。 **決断** ***初期の緩和:** 7月14日の午前11時20分、エンジニアは、影響を受けたサービスポッドを再起動しました。 これは、蓄積された背景プロセスをクリアし、すぐに顧客にオファー文字を送信し、プレビューを表示するための能力を復元しました。 * **永久的な修正:** 7月14日(日)に8:43 PM ETにてコード更新を行いました。 この修正では、すべての背景プロセスが正しく終了し、すべての変換後にクリーンアップされ、将来の蓄積を防ぎます。 **予防措置** ***コード改善:** 堅牢なプロセス管理システム\(「リーパー」プロセスを使用して)を実装し、すべての背景タスクが自動的に完了時に閉鎖されるようにします。 ***監視の強化:** プロセス使用量がシステムの制限の50%を超えた場合は、エンジニアリングチームに通知するために、新しい自動アラートが設定されています。 これにより、お客様に影響を与える前に同様のリソース漏れ日を識別し、解決することができます。 ***バックログ処理:** 別のイニシアチブは、すべてのプレビューがユーザーに利用可能であることを確認するために、アウトエイジウィンドウの間に生成できなかった文書または再開プレビューを識別し、再処理するために完了しました.
公式のインシデント更新を自動翻訳しています。
Nylas認証に影響を及ぼす問題について調査しています。 ユーザーは、メール/カレンダーの統合権限をリセットしようとすると、エラーメッセージ「未知のエラー」が発生することがあります。 開始時間: 10:10 PT 次回更新:午後1時以降.
今後もこの問題について調査を続けてまいります。 次回更新:午後3時以降.
今後もこの問題について調査を続けてまいります。 次のアップデート: 17:00 PT
移行手順を適用し、サービス機能が正常に戻ります。 性能・安定性を監視しています。 次のアップデート: 解像度で.
問題の説明:ユーザーは、メールを送ったり、LeverのMicrosoftメールとカレンダーを同期しようとすると、「未知のエラー」を受け取ることがあります。 顧客への影響: 欠陥のあるユーザーは、Microsoftのメールとカレンダーの統合を認証できませんでした。メールをブロックすると、候補者やカレンダーの同期機能がワークフローをリクルートするのに不可欠です。 ステータス: 解決済み — メール送信とカレンダーの同期が正常に機能します。 RCAは7-10営業日以内に対応いたします.
**事件要約** 2026年7月13日、Microsoft\(Office 365\)を使用して、電子メールとカレンダーの統合の経験豊富なサービス中断。 感染したユーザーは、Lever内の電子メールとカレンダーの接続を承認または再承認することはできませんでした。多くの場合、「未知のエラー」メッセージに遭遇しました。 また、この期間中にMicrosoftの統合によって送信されたアウトバウンドメールは配信できませんでした。 Google ベースのメールとカレンダーサービスは、完全に運用されず、この事件の影響を受けていませんでした。 **検出** 2026年7月13日(水)午後2時22分に、お客さまから当社サポートチームへお寄せいただきました。 調査では、エンジニアリングチームは故障を確認し、高い優先応答を開始しました。 2026年7月12日、基礎技術普及が進んでいますが、利用者が次の日をリフレッシュしたり、アウトバウンド通信を送ったりしようとすると、影響が見えるようになりました。 **ルート原因** 事件は、Microsoftと安全に通信するために使用されるデジタルセキュリティ資格の普及によって引き起こされました。 このクレデンシャルは、システムが電子メールとカレンダーデータを同期できるように、安全な「パスワード」として機能します。 これは、Microsoftの統合に用いられる共有資格だったため、特定のアカウントではなく、Office 365を使用した有効期限の影響を受けている顧客です。 **決断** 問題を解決するために、エンジニアリングチームは、新しいセキュリティ認証を生成し、環境全体の統合設定を更新しました。 システムを通した新たなクレデンシャル伝搬をすると、サービスが完全に復元されました。 2026年7月13日(水)午後8時28分までに、内部試験を行い、顧客再承認を成功させることにより、修復が確認されました。 本件によるデータ損失は発生しません。 **予防措置** 本問題の再発防止のため、次の改善を実施します。 * **Automated Expiryの追跡:** 私たちは、すべての統合資格情報のための正式な追跡プロセスを確立しています。 自動リマインダーは、有効期限の事前設定でうまく設定されています。 * **積極的な監視:** 承認障害でスパイクを検出するために、新しいアラートを設定しました。これにより、チームは、顧客に影響を与える前に同様の問題を識別し、解決することができます.
公式のインシデント更新を自動翻訳しています。
7-3-2026 では、Nylas 認証(オンプレミスの Microsoft Exchange 電子メール/カレンダーサービスをご利用のお客様向けに、Lever インスタンスに影響する問題を認識しました。) Nylas認証は、Office 365またはGoogleサービスで認証する顧客に対して、Nylas認証のみに影響されます。 ユーザーは、メール/カレンダーの許可をリセットしようとすると、「500エラー」メッセージが発生し、候補者がこの問題の結果として10〜15分ごとに重複したメールを受け取るために、いくつかの予期しない電子メールループを観察しました。 ルート原因: Node.js v24.17.0 (https://github.com/nodejs/node/issues/63989) の既知のバグによって、500 秒とメールの失敗が引き起こされます。 v24.17.0セキュリティリリース(CVE-2026-48931)は、`node-fetch` が `ERR STREAM PREMATURE CLOSE`("Premature close") を外部プロバイダー (Nylas/Google) に対する gzipped 応答でスローするように、 `http.Agent` の保留ソケット処理を変更しました。 当社のサービスは、Node 18→24の移行(06-30-2026)を介してこのバグをピックアップしました。 Node 24.18.0 でバグを修正 この問題は、今日の展開(7-8-2026)で修正する必要があります。 問題のステータスと展開タイムラインの更新をできるだけ早く行います.
7/8/2026 の PST/PDT のおよそ 12:15pm として固定が実施されました。 メールとカレンダーの同期は、Nylas認証で設定されたLeverインスタンスに完全に機能します。 修正の有効性を監視し続けています。 ルート原因分析(RCA)は、標準サービスレベル契約内でこの問題に公開されます.
この事件は解決しました。 ルート原因分析(RCA)は、7-10営業日以内にこの問題に公表されます.
**事件要約** 2026年7月2日～2026年7月8日、一部の顧客は、メールやカレンダーサービスに影響を及ぼす断続的な障害を経験しました。 ログイン時にメールや時々「500エラー」を送ったり、同期したりすると、プライマリインパクトが含まれている。 これらの問題は、外部サービスへのアウトバウンド接続を処理する、アンダーリーイングランタイム環境\(Node.js\)の技術的な回帰によって引き起こされました。 特定の電子メールの統合設定を使用して顧客のサブセットのために、システムが誤って成功した電子メールが失敗として送信を知覚させる接続の不安定性を引き起こしました。 これは自動再試行機構をトリガーしました。場合によっては、接続が安定するまで、同じ通信が定期的に受信者に再送信された「再試行ループ」が発生しました。 **検出** 問題は、断続的なサービスの中断の報告に従って特定されました。 当社のサポートおよびエンジニアリングチームは、システムログ内の接続障害の特定のパターンを特定し、これらのレポートに徹底的に調査を行いました。 2026年7月2日、サービスインフラの定期更新に伴い、影響が始まったことを確認しました。 **ルート原因** 根本的な原因は、Node.js\(バージョン24.17.0\)の特定のバージョンで欠損しました。 このバージョンでは、外部サービスと通信するために使用される再利用可能な接続 - keep-alive の接続を管理する方法の欠陥が含まれています。 特定の条件下では、ソフトウェアはタスクが完了する前に、これらの接続を早期に閉じ、失敗したメール送信とデータ同期エラーが発生します。 **決断** 課題を解決するために、エンジニアリングチームは次の手順を実行しました。 ***Identification:** Node.js のランタイムで既知の回帰に対する "Premature close" エラーを関連付けます。 ***アップグレード:** ベースシステムイメージをNode.jsバージョン24.18.0に更新し、この接続の問題の公式修正が含まれています。 ***Deployment:** 修正されたバージョンで、再構築および再採用された重要なサービス\(メールおよびカレンダーコンポーネントを含む)。 *** 確認:** 接続エラーが停止し、サービス安定性が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.
