Lever driftsforstyrrelser

1. 26. august 2026 kl. 16.24 UTCresolved

   På ca. 8: 30am UTC på 8 / 25 / 2026 en planlagt server rotation på https: / / hire.ulever.co / forårsaget øget latency og nogle mislykkedes side belastninger indtil 9: 15am UTC. Påvirkede brugere ville bemærke en "504 fejl" under den berørte side belastninger. Service blev genoprettet til alle brugere fra 9: 15 UTC på 8 / 25 / 2026. En fuld RCA vil blive sendt til dette spørgsmål inden for 7 til 10 hverdage.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. august 2026 kl. 20.12 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 21. august 2026 kl. 20.29 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 24. august 2026 kl. 14.16 UTCresolved

   Status: Opløst Vores overvågning har bekræftet, at der ikke er flere spørgsmål i forbindelse med denne hændelse. Tjenesten har været stabil, og hændelsen betragtes nu som løst. En Root Case Analysis (RCA) vil blive leveret inden for 7-10 hverdage.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. august 2026 kl. 18.13 UTCresolved

   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.

2. 14. august 2026 kl. 18.26 UTCpostmortem

   **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.

1. 7. august 2026 kl. 16.38 UTCinvestigating

   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/

2. 7. august 2026 kl. 17.11 UTCinvestigating

   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.

3. 7. august 2026 kl. 20.28 UTCidentified

   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

4. 7. august 2026 kl. 21.29 UTCmonitoring

   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.

5. 7. august 2026 kl. 22.29 UTCresolved

   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.

6. 14. august 2026 kl. 18.16 UTCpostmortem

   **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.

1. 14. juli 2026 kl. 14.47 UTCinvestigating

   Udstedelse: Vi undersøger, hvad der synes at være en platformbred spørgsmål, hvor tilbud breve undlader at blive sendt. Kundeeffekt: Rekruttere er i øjeblikket ude af stand til at generere eller levere tilbud e-mails til kandidater. Nuværende status: Engineering undersøger aktivt. Der er ikke arbejde på nuværende tidspunkt.

2. 14. juli 2026 kl. 16.24 UTCmonitoring

   Emne: Vi identificerede en platformbred spørgsmål, hvor tilbud breve undladt at blive sendt. Kundeeffekt: Rekruttere var ude af stand til at generere eller levere tilbud e-mails til kandidater. Nuværende status: Det umiddelbare problem er blevet afbødet. Vi overvåger aktivt for at bekræfte fuld opløsning og stabilitet.

3. 14. juli 2026 kl. 23.50 UTCresolved

   Emne: Vi identificerede en platformbred spørgsmål, hvor tilbud breve undladt at blive sendt. Kundeeffekt: Rekruttere var ude af stand til at generere eller levere tilbud e-mails til kandidater. Status: Opløst. En RCA vil være tilgængelig inden for 7-10 hverdage.

4. 22. juli 2026 kl. 13.20 UTCpostmortem

   * * Hændelsesoversigt * * Mellem ca. 13. juli og 14. juli 2026 var nogle kunder ikke i stand til at sende tilbud, og nogle dokumenter / genoptage forhåndsvisninger ikke at generere. Mens kildefiler blev uploadet med succes, den konvertering trin kræves for previews og tilbyde generation mislykkedes. Ingen tab af data opstod. * * Detection * * Spørgsmålet blev identificeret den 14. juli 2026, omkring 10: 43 AM ET, efter rapporter fra kunder til vores Support team. Engineering bekræftede virkningen gennem overvågning, som viste en støt stigning i procestæller inden for dokument- konverter service, indtil det nåede en hård systemgrænse, hvilket får efterfølgende opgaver til at mislykkes. * * Rodårsag * * Hændelsen var forårsaget af en "proces lækage" indført under en nylig platform opgradering. En ændring i, hvordan systemet håndterer dokument konverteringer betød, at hver konvertering startede en ny baggrundsproces, der aldrig blev ordentligt lukket. over flere dage, disse baggrundsprocesser akkumuleres indtil systemet nåede sin maksimale kapacitet. Når denne grænse blev ramt, tjenesten kunne ikke længere starte de nye processer, der kræves for at generere tilbud breve eller dokument previews. * * Opløsning * * * * * Indledende mitigation: * * Klokken 11: 20 ET den 14. juli, ingeniører genstartet de berørte service bælge. Dette ryddet den akkumulerede baggrund processer og straks genoprettet evnen for kunderne til at sende tilbud breve og se previews. * * * Permanent Fix: * * En kode opdatering blev udviklet og indsat på 8: 43 PM ET den 14. juli. Denne rettelse sikrer, at alle baggrundsprocesser afsluttes og renses korrekt efter hver konvertering, hvilket forhindrer fremtidig akkumulering. * * Forebyggende foranstaltninger * * * * * Kodeforbedringer: * * Implementeret et robust processtyringssystem\ (ved hjælp af en "reaper" proces\) for at sikre, at alle baggrundsopgaver automatisk lukkes efter afslutningen. * * * Forbedret overvågning: * * Nye automatiske alarmer er konfigureret til at underrette ingeniørholdet, hvis procesforbruget overstiger 50% af systemgrænsen. Dette vil give os mulighed for at identificere og løse lignende ressource lækager dage, før de påvirker kunderne. * * * Backlog behandling: * * Et separat initiativ blev afsluttet for at identificere og genbehandle ethvert dokument eller genoptage forhåndsvisninger, der ikke kunne generere under udbrudsvinduet for at sikre, at alle forhåndsvisninger er tilgængelige for brugerne.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. juli 2026 kl. 18.04 UTCinvestigating

   Vi undersøger et problem, der påvirker Nylas godkendelse. Brugere kan opleve en fejlmeddelelse "Ukendt fejl", når de forsøger at nulstille e-mail / kalender integration tilladelser. Starttidspunkt: 10: 10 på PT Næste opdatering: 1: 00 pm PT eller tidligere.

2. 13. juli 2026 kl. 19.57 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål. Næste opdatering: 15: 00 PT eller tidligere.

3. 13. juli 2026 kl. 21.59 UTCidentified

   Vi fortsætter med at undersøge dette spørgsmål. Næste opdatering: 05: 00 PM PT

4. 14. juli 2026 kl. 00.28 UTCmonitoring

   Der er blevet anvendt mitigationstrin, og servicefunktionen vender tilbage til normal. Vi overvåger præstationer og stabilitet. Næste opdatering: ved opløsning.

5. 14. juli 2026 kl. 13.08 UTCresolved

   Emne Beskrivelse: Brugere kan have modtaget en "Ukendt fejl", når de forsøger at sende e-mails eller synkronisere deres Microsoft e-mail og kalender i Lever. Customer Impact: Berørte brugere var ude af stand til at autentificere deres Microsoft e-mail og kalender integreringer, blokering e-mail sender til kandidater og kalender sync funktionalitet afgørende for at rekruttere arbejdsgange. Status: Opløst - E-mail sender og kalender synkronisering fungerer nu normalt. En RCA vil være tilgængelig inden for 7-10 hverdage.

6. 22. juli 2026 kl. 13.19 UTCpostmortem

   * * Hændelsesoversigt * * Den 13. juli 2026, kunder ved hjælp af Microsoft\ (Office 365\) for e-mail og kalender integration oplevet service forstyrrelser. Berørte brugere var ude af stand til at godkende eller re- godkende deres e-mail og kalender forbindelser i Lever, ofte støder på en "Ukendt fejl" besked. Derudover, outbound e-mails sendt gennem Microsoft integration undladt at levere i denne periode. Googlebaserede e-mail og kalendertjenester forblev fuldt operationelle og blev ikke påvirket af denne hændelse. * * Detection * * Spørgsmålet blev identificeret den 13. juli 2026 kl. 02: 22 ET, efter rapporter fra kunder til vores Support team. Efter undersøgelsen bekræftede ingeniørholdet fejlene og indledte et højt prioriteret svar. Mens den underliggende tekniske udløb fandt sted den 12. juli 2026, virkningen blev synlig, da brugerne forsøgte at opdatere tilladelser eller sende udgående kommunikation den følgende dag. * * Rodårsag * * Hændelsen var forårsaget af udløbet af en digital sikkerhed kredit bruges til sikkert at kommunikere med Microsoft. Dette creditial fungerer som en sikker "password", der tillader vores systemer at synkronisere e-mail og kalenderdata. Fordi dette var en delt creditial anvendes til Microsoft integration, udløb berørte kunder ved hjælp af Office 365 bredt snarere end en specifik konto. * * Opløsning * * For at løse problemet, vores engineering team genereret en ny sikkerhed creditial og opdateret integration indstillinger på tværs af vores miljøer. Når den nye creditial formeres gennem systemet, service blev fuldt restaureret. Restaurering blev verificeret gennem intern test og bekræftet af succesfulde kunde re-autorisationer af 8: 28 PM ET den 13 juli 2026. Ingen tab af data opstod som følge af denne hændelse. * * Forebyggende foranstaltninger * * For at forhindre en gentagelse af dette spørgsmål gennemfører vi følgende forbedringer: * * * Automated Explacy Tracking: * * Vi er ved at etablere en formel tracking proces for alle integration legitimation med automatiserede påmindelser sat godt i forvejen af udløbsdatoer. * * * Proaktiv overvågning: * * Ny alarmering er blevet konfigureret til at opdage pigge i godkendelse fejl, så vores team til at identificere og løse lignende problemer, før de påvirker kunderne.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 17.17 UTCidentified

   På 7-3- 2026 blev vi gjort opmærksom på et problem påvirker Lever tilfælde med Nylas godkendelse (generelt anvendes til kunder med on- premise Microsoft Exchange e-mail / kalender tjenester). Kun Nylas godkendelse er påvirket, der har ikke været nogen lignende adfærd observeret for kunder autentificering med Office 365 eller Google-tjenester. Brugere kan opleve en "500 fejl" meddelelse, når de forsøger at nulstille e-mail / kalender tilladelser, og vi har observeret flere uventede e-mail loops forårsager kandidater til at modtage duplikerede e-mails hvert 10 til 15 minutter som følge af dette problem. Root årsag: 500s og e-mail fejl er forårsaget af en kendt fejl i Node.js v24.17.0 (https: / / github.com / nodejs / node / issues / 63989). V24.17.0 security release (CVE- 2026- 48931) ændrede 'http.Agent' keep-alive socket handling, således at 'node-hente' kaster 'ERR _ STREAM _ PREMATURE _ CLOSE' ("Premature close") på gzipped svar til eksterne udbydere (Nylas / Google). Vores tjenester samlede det op denne fejl via Node 18 → 24 migration (Occurred on 06- 30- 2026). Fejlen blev rettet opstrøms i Node 24.18.0 Dette spørgsmål bør fastsættes i en implementering i dag (7-8-2026). Vi vil give opdateringer om spørgsmålet status og implementering tidslinje så hurtigt som muligt.

2. 8. juli 2026 kl. 20.03 UTCmonitoring

   En rettelse er blevet gennemført fra ca. 12: 15 pm PST / PDT på 7 / 8 / 2026. e-mail og kalender synkronisering er nu fuldt funktionsdygtig for Lever tilfælde konfigureret med Nylas godkendelse. Vi fortsætter med at overvåge effektiviteten af fixet. En Root Case Analysis (RCA) vil blive offentliggjort til dette nummer inden for standard Service Level Agreement.

3. 9. juli 2026 kl. 16.19 UTCresolved

   Denne hændelse er løst. En Root Case Analysis (RCA) vil blive offentliggjort til dette nummer inden for 7-10 hverdage.

4. 9. juli 2026 kl. 20.43 UTCpostmortem

   * * Hændelsesoversigt * * Mellem 2 juli, 2026, og 8 juli, 2026, Nogle kunder oplevede intermitterende svigt påvirker e-mail og kalender tjenester. De primære effekter omfattede fejl ved afsendelse eller synkronisering af e-mails og lejlighedsvis "500 fejl" under login. Disse spørgsmål var forårsaget af en teknisk regression i den underliggende runtime miljø\ (Node.js\), der håndterer udgående forbindelser til tredjeparts tjenester. For en delmængde af kunder ved hjælp af specifikke e-mail integration indstillinger, forbindelsen ustabilitet forårsaget systemet til fejlagtigt opfatte en vellykket e-mail sende som en fiasko. Dette udløste en automatiseret retry mekanisme, som i nogle tilfælde resulterede i en "retry loop", hvor den samme kommunikation blev sendt tilbage til modtagerne med regelmæssige mellemrum, indtil forbindelsen blev stabiliseret. * * Detection * * Spørgsmålet blev identificeret efter rapporter om intermitterende serviceforstyrrelser. Vores støtte- og ingeniørhold foretog en grundig undersøgelse af disse rapporter, der identificerede et specifikt mønster af forbindelsesfejl i vores systemlogfiler. Yderligere analyse bekræftede, at virkningen begyndte omkring 2 juli 2026, efter en rutinemæssig opdatering til vores serviceinfrastruktur. * * Rodårsag * * Den grundlæggende årsag var en defekt i en specifik version af Node.js\ (version 24.17.0\), softwaremiljøet bruges til at køre vores tjenester. Denne version indeholdt en fejl i, hvordan det forvaltede "keeping-live" forbindelser - genanvendelige forbindelser, der bruges til at kommunikere med eksterne tjenester. Under visse betingelser, ville softwaren for tidligt lukke disse forbindelser, før en opgave blev afsluttet, hvilket resulterer i mislykkede e-mail sender og datasynkronisering fejl. * * Opløsning * * For at løse problemet udførte vores ingeniørteam følgende trin: * * * Identifikation: * * Korrelerede "for tidlig lukning" fejl til en kendt regression i Node.js runtime. * * * Opgradering: * * Opdateret vores base system billeder til Node.js version 24.18.0, som indeholder den officielle rettelse for denne forbindelse problem. * * * Implementering: * * Genopbygget og genindsat kritiske tjenester\ (herunder e-mail og kalenderkomponenter\) på den korrigerede version. * * * Verifikation: * * Bekræftet, at forbindelsen fejl ophørte og service stabilitet tilbage til normale niveauer den 8 juli 2026. * * Forebyggende foranstaltninger * * For at undgå lignende spørgsmål i fremtiden er vi ved at gennemføre følgende forbedringer: * * * Version Sinning: * * Vi har opdateret vores byggeproces for at sikre, at vi kun anvender versioner, der er blevet fuldt verificeret. * * * Forbedret overvågning: * * Vi tilføjer specifikke advarsler for udgående forbindelsesfejl for at opdage og reagere hurtigere på lignende kommunikationsfejl. * * * Automatisk test: * * Vi gennemfører nye syntetiske kontroller for e-mail og kalender synkronisering til proaktivt at identificere problemer, før de påvirker kunderne. * * * Forbedret synlighed: * * Vi opdaterer vores interne dashboards for at give bedre synlighed i de præcise softwareversioner, der kører i vores produktionsmiljø for at fremskynde fremtidige diagnoser.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 14.44 UTCinvestigating

   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/

2. 22. juni 2026 kl. 16.17 UTCidentified

   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.

3. 22. juni 2026 kl. 18.21 UTCresolved

   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.

1. 16. juni 2026 kl. 22.25 UTCinvestigating

   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.

2. 16. juni 2026 kl. 22.33 UTCinvestigating

   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.

3. 17. juni 2026 kl. 18.31 UTCidentified

   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.

4. 17. juni 2026 kl. 18.33 UTCmonitoring

   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.

5. 18. juni 2026 kl. 16.24 UTCresolved

   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).

6. 22. juni 2026 kl. 19.49 UTCpostmortem

   #### **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.

1. 11. juni 2026 kl. 17.28 UTCinvestigating

   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.

2. 11. juni 2026 kl. 19.33 UTCinvestigating

   We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 2:30 PM Pacific 6/11/2026 or sooner

3. 11. juni 2026 kl. 21.42 UTCinvestigating

   We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 4:30 PM Pacific 6/11/2026 or sooner

4. 11. juni 2026 kl. 23.25 UTCinvestigating

   We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 9:30 AM Pacific 6/12/2026 or sooner

5. 12. juni 2026 kl. 16.43 UTCinvestigating

   We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 11:30 AM Pacific 6/12/2026 or sooner

6. 12. juni 2026 kl. 19.03 UTCinvestigating

   We are continuing to investigate this issue in partnership with the LinkedIn team. Next Update 1:30 PM Pacific 6/12/2026 or sooner

7. 12. juni 2026 kl. 19.10 UTCresolved

   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.

1. 23. april 2026 kl. 18.26 UTCinvestigating

   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

2. 23. april 2026 kl. 20.11 UTCresolved

   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.

1. 21. april 2026 kl. 21.07 UTCinvestigating

   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.

2. 21. april 2026 kl. 23.26 UTCinvestigating

   We are continuing to investigate this issue.

3. 22. april 2026 kl. 01.05 UTCmonitoring

   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.

4. 22. april 2026 kl. 12.07 UTCresolved

   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.

5. 23. april 2026 kl. 13.33 UTCpostmortem

   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.

1. 17. april 2026 kl. 17.45 UTCinvestigating

   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

2. 17. april 2026 kl. 18.53 UTCresolved

   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.

1. 17. april 2026 kl. 17.15 UTCinvestigating

   We are currently investigating this issue.

2. 17. april 2026 kl. 17.33 UTCidentified

   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.

3. 17. april 2026 kl. 17.36 UTCidentified

   We are continuing to work on a fix for this issue.

4. 17. april 2026 kl. 18.59 UTCmonitoring

   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/

5. 17. april 2026 kl. 21.11 UTCresolved

   This incident has been resolved.

1. 27. marts 2026 kl. 18.07 UTCresolved

   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.

1. 26. marts 2026 kl. 12.02 UTCinvestigating

   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.

2. 26. marts 2026 kl. 12.36 UTCidentified

   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.

3. 26. marts 2026 kl. 14.12 UTCmonitoring

   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.

4. 26. marts 2026 kl. 14.13 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 26. marts 2026 kl. 18.13 UTCresolved

   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

1. 5. marts 2026 kl. 19.59 UTCidentified

   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.

2. 6. marts 2026 kl. 21.25 UTCidentified

   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.

3. 9. marts 2026 kl. 16.36 UTCidentified

   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.

4. 9. marts 2026 kl. 18.13 UTCresolved

   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

1. 11. februar 2026 kl. 18.26 UTCinvestigating

   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.

2. 11. februar 2026 kl. 20.08 UTCidentified

   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.

3. 12. februar 2026 kl. 01.36 UTCresolved

   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

1. 4. februar 2026 kl. 12.04 UTCinvestigating

   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.

2. 4. februar 2026 kl. 12.33 UTCidentified

   The issue has been identified and we are working on the fix.

3. 4. februar 2026 kl. 12.37 UTCmonitoring

   A fix has been implemented, and we are monitoring the results.

4. 4. februar 2026 kl. 13.05 UTCresolved

   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

1. 29. januar 2026 kl. 19.04 UTCinvestigating

   We are currently investigating this issue.

2. 30. januar 2026 kl. 20.38 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 31. januar 2026 kl. 00.34 UTCresolved

   This incident has been resolved.