58 Lever incidents · Haziran 2024 — official updates, affected components, duration and resolution details.
Yaklaşık 8:30am UTC 8/25/2026'da https://hire.eulever.co / geç kalmış ve 9:15am UTC'ye kadar bazı başarısız sayfa yüklerine neden oldu. Etkilenen kullanıcılar etkilenen sayfa yükleri sırasında "504 hata" fark ederler. Hizmet tüm kullanıcılara 8/25/2026'da 9:15am UTC olarak restore edildi. Tam bir RCA bu konuya 7 ila 10 iş günü içinde gönderilecek.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Şu anda bu konuyu araştırıyoruz.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Durum: Yeniden çözülmemiş İzlememiz bu olayla ilgili daha fazla sorun olmadığını doğruladı. Servis istikrarlı kaldı ve olay şimdi çözüldü. Bir Kök Sebep Analizi (RCA) 7-10 iş günü içinde sağlanacaktır.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
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.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
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.
Sorun: Hangi platform çapında bir sorun olduğunu araştırıyoruz ki bu mektuplar gönderilemez. Müşteri Etkisi: İşe alımcılar şu anda adaylara e-postalar üretemezler veya sunabilirler. Mevcut Durum: Mühendislik aktif olarak araştırıyor. Bu anda hiçbir iş mevcut değildir.
Sorun: mektupların gönderilmediği bir platform çapında bir konu tespit ettik. Müşteri Etkisi: İşverenler adaylara e-postalar üretemedi veya sunabilirdi. Mevcut Durum: Acil konu azaltıldı. Tam çözümü ve istikrarı doğrulamak için aktif olarak izliyoruz.
Sorun: mektupların gönderilmediği bir platform çapında bir konu tespit ettik. Müşteri Etkisi: İşverenler adaylara e-postalar üretemedi veya sunabilirdi. Durum: Çözüldü. Bir RCA 7-10 iş günleri içinde kullanılabilir.
**Incident Özet** Yaklaşık 13 Temmuz ve 14 Temmuz 2026 arasında, bazı müşteriler mektuplar gönderemedi ve bazı belge/resume önizlemeleri üretemedi. Kaynak dosyaları başarıyla yüklenmiş olsa da, önizlemeler için gereken dönüşüm adımını ve nesil başarısız oldu. Hiçbir veri kaybı gerçekleşmedi. **Deteksiyon** Sorun 14 Temmuz 2026'da tespit edildi, yaklaşık 10:43 AM ET, müşterilerin Destek ekibimize raporlarını takip etti. Mühendislik izleme yoluyla etkisini doğruladı, bu işlemde istikrarlı bir artış, zor bir sistem sınırına ulaşana kadar belge-konverter servisi içinde gerçekleşti, sonraki görevleri başarısız hale getirdi. **Root Cause** Olay, son bir platform yükseltmesi sırasında ortaya çıkan bir "işlem sızıntısı" nedeniyle neden oldu. Sistem belge dönüşümlerinin nasıl işlediği bir değişiklik, her dönüşümün asla düzgün bir şekilde kapatılmayan yeni bir arka plan süreci başladığını ifade eder. Birkaç gün boyunca, sistem maksimum kapasiteye ulaşana kadar bu arka plan süreçleri. Bu sınır vurulduktan sonra, hizmet artık mektuplar veya belge önizlemeleri üretmek için gerekli olan yeni süreçleri başlatamaz. **Resolution** * **Initial Mitigation:** 11:20'de AM ET 14 Temmuz'da mühendisler etkilenen servisi yeniden başlattı. Bu, birikmiş arka plan süreçlerini temizledi ve müşterilerin mektuplar ve görüş önizlemelerini sunma yeteneğini hemen restore etti. * **Permanent Fix:** 8:43 PM ET'de 14 Temmuz'da bir kod güncellemesi geliştirildi ve dağıtıldı. Bu düzeltme, tüm arka plan süreçlerinin her dönüşümden sonra doğru şekilde sona erdiğini ve temizlendiğini, gelecekteki herhangi bir birikimi önlemesini sağlar. **Proventative Measures** * **Koçlamalar:** Tüm arka plan görevlerinin otomatik olarak tamamlanmasını sağlamak için sağlam bir süreç yönetim sistemi \(örneğin "reaper" bir süreç) uygulamak. * **Enhanced Watch:** Yeni otomatik uyarılar, sistem limitinin %50'sini aşsa mühendislik ekibini bilgilendirmek için yapılandırıldı. Bu, müşterileri etkilemeden önce benzer kaynak sızıntılarını tanımlamamıza ve çözmemize izin verecektir. * **Backlog Processing:** Ayrı bir inisiyatif, tüm önizlemelerin kullanıcılar için mevcut olmasını sağlamak için dışlama penceresi sırasında üretemeyen herhangi bir belge veya özgeçmiş önizlemelerini tanımlamak ve yeniden işlemek için tamamlandı.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Nylas doğrulamasını etkileyen bir sorunu araştırıyoruz. Kullanıcılar e-posta/calendar entegrasyon izinlerini sıfırlamaya çalışırken bir hata mesajı yaşayabilirler. Başlangıç zamanı: 10:10 Sonraki güncelleme: 1:00 PT veya er.
Bu konuyu araştırmaya devam ediyoruz. Sonraki güncelleme: 3:00 PT veya er.
Bu konuyu araştırmaya devam ediyoruz. Sonraki güncelleme: 5:00 PM PT
Dava adımları uygulandı ve hizmet işlevselliği normale dönüyor. Performansı ve istikrarı takip ediyoruz. Sonraki güncelleme: karar üzerine.
Sorun Açıklama: Kullanıcılar, e-posta göndermeye veya Microsoft e-postalarını ve takvimlerini yükseltmeye çalışırken "Bililmeyen bir hata" almış olabilirler. Müşteri Etkisi: Etkilenen kullanıcılar Microsoft e-postalarını ve takvim entegrasyonlarını gerçekleştiremediler, e-posta başvurur ve iş akışlarını işe almak için eleştirel takvim senkronizasyonuna gönderirler. Durum: Yeniden çözülebilir - E-posta gönderir ve takvim senkronizasyonu artık normal olarak çalışır. Bir RCA 7-10 iş günleri içinde kullanılabilir.
**Incident Özet** 13 Temmuz'da 2026'da, Microsoft \ (Office 365\) e-posta ve takvim entegrasyon deneyimli hizmet kesintileri için müşteriler kullanıyor. Etkilenen kullanıcılar, e-postalarını ve takvim bağlantılarını, genellikle "Bilmeyen bir hata" mesajıyla karşılaşamadılar. Ek olarak, Microsoft entegrasyonu aracılığıyla gönderilen e-postalar bu dönemde teslim edilemez. Google tabanlı e-posta ve takvim hizmetleri tamamen operasyonel kaldı ve bu olay tarafından etkilenmedi. **Deteksiyon** Sorun 13 Temmuz 2026'da tespit edildi, 2:22 PM ET, müşterilerin Destek ekibimize raporlarını takip etti. Soruşturmada, mühendislik ekibi başarısızlıkları doğruladı ve yüksek öncelikli bir yanıt başlattı. Altta yatan teknik sona erme 12 Temmuz 2026'da gerçekleştiğinde, kullanıcılar izinleri yenilemeye veya ertesi gün iletişim göndermeye çalıştılar. **Root Cause** Olay, Microsoft ile güvenli bir şekilde iletişim kurmak için kullanılan bir dijital güvenlik haçının sona ermesinden kaynaklanıyordu. Bu credential, sistemlerimizin e-posta ve takvim verilerini senkronize etmesine izin veren güvenli bir "password" olarak hareket eder. Çünkü bu, Microsoft entegrasyonu için paylaşılan bir haçlıydı, Office 365 kullanan son müşteriler belirli bir hesaptan daha geniş bir şekilde kullanıyorlardı. **Resolution** Sorunu çözmek için, mühendislik ekibimiz, çevremizdeki entegrasyon ayarlarını yeni bir güvenlik credential ve güncelledi. Sistem aracılığıyla yeni kriedential propagated sonra, hizmet tamamen restore edildi. Restorasyon iç test yoluyla doğrulandı ve 8:28 PM ET tarafından 13 Temmuz'da başarılı bir müşteri yeniden yazarlığıyla doğrulandı. Hiçbir veri kaybı bu olayın bir sonucu olarak gerçekleşmedi. **Proventative Measures** Bu sorunun bir recurrence önlemek için, aşağıdaki gelişmeleri uyguluyoruz: * **Otomatik Açıklama:** Tüm entegrasyon referansları için resmi bir takip süreci kuruyoruz otomatik hatırlatmalar sona erme tarihlerine iyi ayarlanmıştır. * **Proaktif İzleme:** Yeni uyarılama, yetki başarısızlıklarını tespit etmek için yapılandırıldı, ekibimizin müşterileri etkilemeden önce benzer sorunları tanımlamasına ve çözmesine izin verdi.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
7-3-2026'da, Nylas kimlik doğrulama ile ilgili bir sorundan haberdar olduk (genellikle Microsoft Exchange e-calendar hizmetleri ile müşteriler için kullanılır). Sadece Nylas kimlik doğrulaması etkileniyor, Office 365 veya Google hizmetleriyle ilgili müşteriler için gözlemlenen benzer bir davranış yok. Kullanıcılar e-posta/calendar izinlerini sıfırlamaya çalışırken bir "500 hata" mesajı yaşayabilir ve adayların bu sorunun sonucu olarak her 10 ila 15 dakika tekrar e-posta almalarına neden olan birkaç beklenmedik e-posta döngüsü gözlemlemiştir. Kök nedeni: 500'ler ve e-posta başarısızlıkları Node.js v24.17.0 (https://github.com/nodejs/node/ports/63989) bilinen bir otobüse neden oluyor. v24.17.0 güvenlik serbestliği (CVE-2026-48931), "https://www.Agent' keep-alive soketi bu yüzden "node-fetch' atlar "ERR STREAM PREM form CLOSE" ("Premature close") dış sağlayıcılara (Nylas/Google). Hizmetlerimiz bunu Node 18→24 göçü aracılığıyla aldı ( 06-30-2026). Bug Node 24.18.0'te sabitlendi. Bu konu bugün bir dağıtımda düzeltilmelidir (7-8-2026). En kısa sürede konu durumu ve dağıtım süresi hakkında güncellemeler vereceğiz.
Bir düzeltme 7/8/2026'da yaklaşık 12:15pm PST/PDT olarak uygulandı. E-posta ve Takvim senkronizasyonu şimdi Nyla kimlik doğrulama ile yapılandırılan yedekler için tamamen işlevseldir. Biz düzeltmenin etkinliğini izlemeye devam ediyoruz. Bir Kök Sebep Analizi (RCA) standart Hizmet Düzeyi Anlaşması dahilinde bu konu için yayınlanacaktır.
Bu olay çözüldü. Bir Kök Sebep Analizi (RCA) bu konuya 7-10 iş günü içinde yayınlanacaktır.
**Incident Özet** 2 Temmuz 2026 ve 8 Temmuz 2026 arasında, bazı müşteriler e-posta ve takvim hizmetlerini etkileyen geçici başarısızlıklar yaşadı. birincil etkiler, e-posta gönderme veya senkronize e-posta gönderme sırasında hataları içeriyordu ve giriş sırasında "500 hata". Bu sorunlar, alt üst düzey runtime environment \ (Node.js\) üçüncü taraf servislerine giden bağlantıları ele alan teknik bir regresyon tarafından neden edildi. Belirli bir e-posta entegrasyonu ayarlarını kullanan müşterilerin alt kümesi için, bağlantı istikrarsızlığı sistemin başarısız bir e-posta göndermesine neden oldu. Bu, bazı durumlarda, aynı iletişimin düzenli aralıklarla alıcılara yeniden yönlendirildiği bir “retry loop” ile sonuçlandı. **Deteksiyon** Sorun intermittent servis kesintilerinin raporlarını takiben tespit edildi. Destek ve mühendislik ekiplerimiz bu raporlara kapsamlı bir soruşturma yürüttüler, sistemimizdeki belirli bir bağlantı hatası tespit ettiler. Daha fazla analiz, etkinin yaklaşık 2 Temmuz 2026'da başladığını, hizmet altyapımıza rutin bir güncelleme takip ettiğini doğruladı. **Root Cause** Kök nedeni Node.js \(vers 24.17.0\), hizmetlerimizi çalıştırmak için kullanılan yazılım ortamıydı. Bu versiyon, dış hizmetlerle iletişim kurmak için kullanılan "sağlayıcı" bağlantıları nasıl yönetilen bir kusur içeriyordu. Bazı koşullar altında, yazılım bu bağlantıları bir görev tamamlanmadan önce erken kapatacak ve başarısız e-posta gönderme ve veri senkronizasyon hatalarına yol açacaktı. **Resolution** Sorunu çözmek için, mühendislik ekibimiz aşağıdaki adımları gerçekleştirdi: * **İdentification:** “Premature yakın” hataları ile Node.js runtime'da bilinen bir regresyonla ilgilidir. * **Upgrad:** Bu bağlantı konusu için resmi düzeltme içeren Node.js versiyonu 24.18.0 için temel sistemimiz görüntülerini güncelledi. * **Deployment: ** Yeniden inşa edilmiş ve işe alındı e-posta ve takvim bileşenleri de dahil) düzeltme sürümde. * **Verification:** Bu bağlantı hatalarının sona erdiğini ve hizmet istikrarının 8 Temmuz 2026'da normal seviyelere geri döndüğünü doğruladı. **Proventative Measures** Gelecekte benzer sorunları önlemek için aşağıdaki gelişmeleri uyguluyoruz: * **Version Pinning:** Tamamen doğrulanmış olan sadece versiyonları dağıtmamızı sağlamak için inşa sürecimizi güncelledik. * **Enhanced Watch:** Daha hızlı bir şekilde benzer iletişim başarısızlıklarına cevap vermek için gelen bağlantı hataları için belirli uyarılar ekliyoruz. * **Otomatik Test:** Yeni sentetik çekleri e-posta ve takvim senkronizasyonu müşterileri etkilemeden önce proaktif olarak tanımlamak için uyguluyoruz. * ** Geliştirilmiş Vibilite:** Üretim ortamımızda gelecekteki teşhisleri hızlandırmak için çalışan tam yazılım versiyonlarına daha iyi görünürlük sağlamak için iç panolarımızı güncelliyoruz.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
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.
