Lever Outage History

Started Aug 25, 2026, 08:30 AM UTC· resolved Aug 25, 2026, 09:15 AM UTC

1. resolved Aug 26, 2026, 04:24 PM UTC

   At about 8:30am UTC on 8/25/2026 a scheduled server rotation at https://hire.eulever.co/ caused increased latency and some failed page loads until 9:15am UTC. Impacted users would notice a "504 error" during the affected page loads. Service was restored to all users as of 9:15am UTC on 8/25/2026. An full RCA will be posted to this issue within 7 to 10 business days.

Read the full incident report →

Started Aug 21, 2026, 08:12 PM UTC· resolved Aug 24, 2026, 02:16 PM UTC

1. investigating Aug 21, 2026, 08:12 PM UTC

   We are currently investigating this issue.

2. monitoring Aug 21, 2026, 08:29 PM UTC

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

3. resolved Aug 24, 2026, 02:16 PM UTC

   Our monitoring has confirmed that there are no further issues related to this incident. Service has remained stable, and the incident is now considered resolved. A Root Cause Analysis (RCA) will be provided within 7-10 business days.

Read the full incident report →

Started Aug 12, 2026, 05:31 PM UTC· resolved Aug 12, 2026, 05:37 PM UTC

1. resolved Aug 12, 2026, 06:13 PM UTC

   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. postmortem Aug 14, 2026, 06:26 PM UTC

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

Read the full incident report →

Started Aug 07, 2026, 04:38 PM UTC· resolved Aug 07, 2026, 10:29 PM UTC

1. investigating Aug 07, 2026, 04:38 PM UTC

   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. investigating Aug 07, 2026, 05:11 PM UTC

   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. identified Aug 07, 2026, 08:28 PM UTC

   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. monitoring Aug 07, 2026, 09:29 PM UTC

   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. resolved Aug 07, 2026, 10:29 PM UTC

   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.

6. postmortem Aug 14, 2026, 06:16 PM UTC

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

Read the full incident report →

Started Jul 14, 2026, 02:47 PM UTC· resolved Jul 14, 2026, 11:50 PM UTC

1. investigating Jul 14, 2026, 02:47 PM UTC

   Issue: We are investigating what appears to be a platform-wide issue in which offer letters fail to be sent. Customer Impact: Recruiters are currently unable to generate or deliver offer emails to candidates. Current Status: Engineering is actively investigating. No workaround is available at this time.

2. monitoring Jul 14, 2026, 04:24 PM UTC

   Issue: We identified a platform-wide issue in which offer letters failed to be sent. Customer Impact: Recruiters were unable to generate or deliver offer emails to candidates. Current Status: The immediate issue has been mitigated. We are actively monitoring to confirm full resolution and stability.

3. resolved Jul 14, 2026, 11:50 PM UTC

   Issue: We identified a platform-wide issue in which offer letters failed to be sent. Customer Impact: Recruiters were unable to generate or deliver offer emails to candidates. Status: Resolved. An RCA will be available within 7-10 business days.

4. postmortem Jul 22, 2026, 01:20 PM UTC

   **Incident Summary** Between approximately July 13 and July 14, 2026, some customers were intermittently unable to send offer letters, and some document/resume previews failed to generate. While source files were uploaded successfully, the conversion step required for previews and offer generation failed. No data loss occurred. **Detection** The issue was identified on July 14, 2026, at approximately 10:43 AM ET, following reports from customers to our Support team. Engineering confirmed the impact through monitoring, which showed a steady increase in process counts within the document-converter service until it reached a hard system limit, causing subsequent tasks to fail. **Root Cause** The incident was caused by a "process leak" introduced during a recent platform upgrade. A change in how the system handles document conversions meant that each conversion started a new background process that was never properly closed. Over several days, these background processes accumulated until the system reached its maximum capacity. Once this limit was hit, the service could no longer start the new processes required to generate offer letters or document previews. **Resolution** * **Initial Mitigation:** At 11:20 AM ET on July 14, engineers restarted the affected service pods. This cleared the accumulated background processes and immediately restored the ability for customers to send offer letters and view previews. * **Permanent Fix:** A code update was developed and deployed at 8:43 PM ET on July 14. This fix ensures that all background processes are correctly terminated and cleaned up after every conversion, preventing any future accumulation. **Preventative Measures** * **Code Improvements:** Implemented a robust process-management system \(using a "reaper" process\) to ensure all background tasks are automatically closed upon completion. * **Enhanced Monitoring:** New automated alerts have been configured to notify the engineering team if process usage exceeds 50% of the system limit. This will allow us to identify and resolve similar resource leaks days before they impact customers. * **Backlog Processing:** A separate initiative was completed to identify and reprocess any document or resume previews that failed to generate during the outage window to ensure all previews are available to users.

Read the full incident report →

Started Jul 13, 2026, 06:04 PM UTC· resolved Jul 14, 2026, 01:08 PM UTC

1. investigating Jul 13, 2026, 06:04 PM UTC

   We are investigating an issue affecting Nylas authentication Users may experience errors when attempting to reset email/calendar integration permissions. Start time: 10:10 am PT Next update: 1:00 pm PT or sooner.

2. investigating Jul 13, 2026, 07:57 PM UTC

   We are continuing to investigate this issue. Next update: 3:00 pm PT or sooner.

3. identified Jul 13, 2026, 09:59 PM UTC

   We are continuing to investigate this issue. Next update: 5:00 PM PT

4. monitoring Jul 14, 2026, 12:28 AM UTC

   Mitigation steps have been applied and service functionality is returning to normal. We are monitoring performance and stability. Next update: upon resolution.

5. resolved Jul 14, 2026, 01:08 PM UTC

   Issue Description: Users may have received an "Unknown error" when attempting to send emails or sync their Microsoft email and calendar in Lever. Customer Impact: Affected users were unable to authenticate their Microsoft email and calendar integrations, blocking email sends to candidates and calendar sync functionality critical to recruiting workflows. Status: Resolved — Email sends and calendar sync are now functioning normally. An RCA will be available within 7-10 business days.

6. postmortem Jul 22, 2026, 01:19 PM UTC

   **Incident Summary** On July 13, 2026, customers using Microsoft \(Office 365\) for email and calendar integration experienced service disruptions. Affected users were unable to authorize or re-authorize their email and calendar connections within Lever, often encountering an "Unknown error" message. Additionally, outbound emails sent through the Microsoft integration failed to deliver during this period. Google-based email and calendar services remained fully operational and were not impacted by this incident. **Detection** The issue was identified on July 13, 2026, at 2:22 PM ET, following reports from customers to our Support team. Upon investigation, the engineering team confirmed the failures and initiated a high-priority response. While the underlying technical expiration occurred on July 12, 2026, the impact became visible as users attempted to refresh permissions or send outbound communications the following day. **Root Cause** The incident was caused by the expiration of a digital security credential used to securely communicate with Microsoft. This credential acts as a secure "password" that allows our systems to sync email and calendar data. Because this was a shared credential used for the Microsoft integration, the expiration affected customers using Office 365 broadly rather than a specific account. **Resolution** To resolve the issue, our engineering team generated a new security credential and updated the integration settings across our environments. Once the new credential propagated through the system, service was fully restored. Restoration was verified through internal testing and confirmed by successful customer re-authorizations by 8:28 PM ET on July 13, 2026. No data loss occurred as a result of this incident. **Preventative Measures** To prevent a recurrence of this issue, we are implementing the following improvements: * **Automated Expiry Tracking:** We are establishing a formal tracking process for all integration credentials with automated reminders set well in advance of expiration dates. * **Proactive Monitoring:** New alerting has been configured to detect spikes in authorization failures, allowing our team to identify and resolve similar issues before they impact customers.

Read the full incident report →

Started Jul 08, 2026, 05:17 PM UTC· resolved Jul 09, 2026, 04:19 PM UTC

1. identified Jul 08, 2026, 05:17 PM UTC

   On 7-3-2026 we were made aware of an issue impacting Lever instances with Nylas authentication (generally used for customers with on-premise Microsoft Exchange email/calendar services). Only Nylas authentication is impacted, there has been no similar behavior observed for customers authenticating with Office 365 or Google services. Users may experience a "500 error" message when attempting to reset email/calendar permissions and we have observed several unexpected email loops causing candidates to receive duplicate emails every 10 to 15 minutes as a result of this issue. Root cause: The 500s and email failures are caused by a known bug in Node.js v24.17.0 (https://github.com/nodejs/node/issues/63989). The v24.17.0 security release (CVE-2026-48931) changed `http.Agent` keep-alive socket handling so that `node-fetch` throws `ERR_STREAM_PREMATURE_CLOSE` ("Premature close") on gzipped responses to external providers (Nylas/Google). Our services picked it up this bug via the Node 18→24 migration (Occurred on 06-30-2026). The bug was fixed upstream in Node 24.18.0 This issue should be fixed in a deployment today (7-8-2026). We will provide updates on the issue status and deployment timeline as soon as possible.

2. monitoring Jul 08, 2026, 08:03 PM UTC

   A fix has been implemented as of approximately 12:15pm PST/PDT on 7/8/2026. Email and Calendar sync are now fully functional for Lever instances configured with Nylas authentication. We are continuing to monitor the effectiveness of the fix. A Root Cause Analysis (RCA) will be published to this issue within the standard Service Level Agreement.

3. resolved Jul 09, 2026, 04:19 PM UTC

   This incident is resolved. A Root Cause Analysis (RCA) will be published to this issue within the standard Service Level Agreement.

4. postmortem Jul 09, 2026, 08:43 PM UTC

   **Incident Summary** Between July 2, 2026, and July 8, 2026, Some customers experienced intermittent failures affecting email and calendar services. The primary impacts included errors when sending or syncing emails and occasional "500 errors" during login. These issues were caused by a technical regression in the underlying runtime environment \(Node.js\) that handles outbound connections to third-party services. For a subset of customers using specific email integration settings, the connection instability caused the system to incorrectly perceive a successful email send as a failure. This triggered an automated retry mechanism, which in some cases resulted in a "retry loop" where the same communication was re-sent to recipients at regular intervals until the connection was stabilized. **Detection** The issue was identified following reports of intermittent service disruptions. Our support and engineering teams conducted a thorough investigation into these reports, identifying a specific pattern of connection failures within our system logs. Further analysis confirmed that the impact began on approximately July 2, 2026, following a routine update to our service infrastructure. **Root Cause** The root cause was a defect in a specific version of Node.js \(version 24.17.0\), the software environment used to run our services. This version contained a flaw in how it managed "keep-alive" connections—reusable connections used to communicate with external services. Under certain conditions, the software would prematurely close these connections before a task was completed, resulting in failed email sends and data sync errors. **Resolution** To resolve the issue, our engineering team performed the following steps: * **Identification:** Correlated the "Premature close" errors to a known regression in the Node.js runtime. * **Upgrade:** Updated our base system images to Node.js version 24.18.0, which contains the official fix for this connection issue. * **Deployment:** Rebuilt and redeployed critical services \(including email and calendar components\) on the corrected version. * **Verification:** Confirmed that connection errors ceased and service stability returned to normal levels on July 8, 2026. **Preventative Measures** To prevent similar issues in the future, we are implementing the following improvements: * **Version Pinning:** We have updated our build process to ensure we deploy only versions that have been fully verified. * **Enhanced Monitoring:** We are adding specific alerts for outbound connection errors to detect and respond to similar communication failures more rapidly. * **Automated Testing:** We are implementing new synthetic checks for email and calendar synchronization to proactively identify issues before they impact customers. * **Improved Visibility:** We are updating our internal dashboards to provide better visibility into the exact software versions running in our production environment to speed up future diagnoses.

Read the full incident report →

Started Jun 22, 2026, 02:44 PM UTC· resolved Jun 22, 2026, 06:21 PM UTC

1. investigating Jun 22, 2026, 02:44 PM UTC

   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. identified Jun 22, 2026, 04:17 PM UTC

   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. resolved Jun 22, 2026, 06:21 PM UTC

   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.

Read the full incident report →

Started Jun 16, 2026, 05:30 PM UTC· resolved Jun 18, 2026, 12:00 PM UTC

1. investigating Jun 16, 2026, 10:25 PM UTC

   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. investigating Jun 16, 2026, 10:33 PM UTC

   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. identified Jun 17, 2026, 06:31 PM UTC

   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. monitoring Jun 17, 2026, 06:33 PM UTC

   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. resolved Jun 18, 2026, 04:24 PM UTC

   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. postmortem Jun 22, 2026, 07:49 PM UTC

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

Read the full incident report →

Started Jun 11, 2026, 05:28 PM UTC· resolved Jun 12, 2026, 07:10 PM UTC

1. investigating Jun 11, 2026, 05:28 PM UTC

   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. investigating Jun 11, 2026, 07:33 PM UTC

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

3. investigating Jun 11, 2026, 09:42 PM UTC

   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. investigating Jun 11, 2026, 11:25 PM UTC

   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. investigating Jun 12, 2026, 04:43 PM UTC

   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. investigating Jun 12, 2026, 07:03 PM UTC

   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. resolved Jun 12, 2026, 07:10 PM UTC

   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.

Read the full incident report →

Started Apr 23, 2026, 06:26 PM UTC· resolved Apr 23, 2026, 08:11 PM UTC

1. investigating Apr 23, 2026, 06:26 PM UTC

   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. resolved Apr 23, 2026, 08:11 PM UTC

   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.

Read the full incident report →

Started Apr 21, 2026, 03:50 PM UTC· resolved Apr 22, 2026, 12:07 PM UTC

1. investigating Apr 21, 2026, 09:07 PM UTC

   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 the error messages “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. investigating Apr 21, 2026, 11:26 PM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 22, 2026, 01:05 AM UTC

   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. resolved Apr 22, 2026, 12:07 PM UTC

   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. postmortem Apr 23, 2026, 01:33 PM UTC

   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.

Read the full incident report →

Started Apr 17, 2026, 05:45 PM UTC· resolved Apr 17, 2026, 06:53 PM UTC

1. investigating Apr 17, 2026, 05:45 PM UTC

   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. resolved Apr 17, 2026, 06:53 PM UTC

   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.

Read the full incident report →

Started Apr 17, 2026, 05:15 PM UTC· resolved Apr 17, 2026, 09:11 PM UTC

1. investigating Apr 17, 2026, 05:15 PM UTC

   We are currently investigating this issue.

2. identified Apr 17, 2026, 05:33 PM UTC

   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. identified Apr 17, 2026, 05:36 PM UTC

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

4. monitoring Apr 17, 2026, 06:59 PM UTC

   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. resolved Apr 17, 2026, 09:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 26, 2026, 12:02 PM UTC· resolved Mar 26, 2026, 06:13 PM UTC

1. investigating Mar 26, 2026, 12:02 PM UTC

   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. identified Mar 26, 2026, 12:36 PM UTC

   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. monitoring Mar 26, 2026, 02:12 PM UTC

   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. monitoring Mar 26, 2026, 02:13 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Mar 26, 2026, 06:13 PM UTC

   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

Read the full incident report →

Started Mar 05, 2026, 07:59 PM UTC· resolved Mar 09, 2026, 06:13 PM UTC

1. identified Mar 05, 2026, 07:59 PM UTC

   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. identified Mar 06, 2026, 09:25 PM UTC

   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. identified Mar 09, 2026, 04:36 PM UTC

   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. resolved Mar 09, 2026, 06:13 PM UTC

   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

Read the full incident report →

Started Feb 11, 2026, 06:26 PM UTC· resolved Feb 12, 2026, 01:36 AM UTC

1. investigating Feb 11, 2026, 06:26 PM UTC

   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. identified Feb 11, 2026, 08:08 PM UTC

   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. resolved Feb 12, 2026, 01:36 AM UTC

   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

Read the full incident report →

Started Feb 04, 2026, 12:04 PM UTC· resolved Feb 04, 2026, 01:05 PM UTC

1. investigating Feb 04, 2026, 12:04 PM UTC

   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. identified Feb 04, 2026, 12:33 PM UTC

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

3. monitoring Feb 04, 2026, 12:37 PM UTC

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

4. resolved Feb 04, 2026, 01:05 PM UTC

   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

Read the full incident report →

Started Jan 29, 2026, 07:04 PM UTC· resolved Jan 31, 2026, 12:34 AM UTC

1. investigating Jan 29, 2026, 07:04 PM UTC

   We are currently investigating this issue.

2. monitoring Jan 30, 2026, 08:38 PM UTC

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

3. resolved Jan 31, 2026, 12:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 26, 2026, 07:06 PM UTC· resolved Jan 28, 2026, 12:46 PM UTC

1. investigating Jan 26, 2026, 07:06 PM UTC

   We are currently investigating an issue that is intermittently affecting reporting data. Issues impacting reporting data were noticed around 8:30 AM PT on Friday January 23, 2026. Users may see issues with data refreshing in Data Explorer and Visual Insights. Our Engineering teams are actively working to resolve this as soon as possible.

2. identified Jan 27, 2026, 02:52 PM UTC

   Our data team has identified gaps in data updates occurring between January 20 and 23. We are currently re-processing the missing data and expect this to be completed within the next 24 hours. We apologize for any disruption this may have caused and appreciate your patience as we work to resolve the issue.

3. resolved Jan 28, 2026, 12:46 PM UTC

   Our team has completed re-processing the missing data from January 20–23. All data updates are now fully restored and functioning as expected. We appreciate your patience while we worked to resolve this issue.

Read the full incident report →

Started Jan 22, 2026, 06:57 PM UTC· resolved Jan 24, 2026, 01:39 AM UTC

1. identified Jan 22, 2026, 06:57 PM UTC

   This issue with automation workflow trigger delays has resurfaced. See the original report of this issue here: https://status.lever.co/incidents/h5ypwy1cllrl Our Engineering team has identified the issue and is actively working on a fix.

2. monitoring Jan 22, 2026, 09:22 PM UTC

   Workflow trigger delays have been resolved and we are actively monitoring to ensure continued performance and stability.

3. monitoring Jan 23, 2026, 05:31 PM UTC

   Update: We are continuing to observe good performance and stability across all processes. At this time, all systems are operating as expected. Our team will maintain active monitoring throughout the day to ensure continued reliability and success. We will provide additional updates as needed.

4. resolved Jan 24, 2026, 01:39 AM UTC

   This incident has been resolved. All systems related to Automation Workflows continue to perform and operate as expected.

5. postmortem Feb 02, 2026, 07:54 PM UTC

   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. ## Customer Impact Between **January 21 and January 23, 2026**, some customers experienced delays in automated workflow execution. Automation workflows entered a _“waiting”_ state and were processed behind schedule rather than in real time. While no data was lost, workflow execution was slower than expected, which may have delayed downstream actions that depend on automation completion. Service levels were fully restored by **January 23, 2026 at 08:54**, and workflows have been operating in real time since that point. ## Root Cause We had a single instance that had accumulated a very large number of automation workflows configured to trigger on the same event type. Each time an application event occurred, all of these workflows were evaluated simultaneously. This configuration resulted in **tens of thousands of unnecessary database queries per event**, which significantly increased system load. As volume grew, the automation system was no longer able to process workflows at the rate they were being generated, causing a backlog and delays for all automation tasks. In short: * The automation system encountered an unusually high and inefficient workload pattern. * Existing safeguards and scaling assumptions were insufficient for this edge case. ## Resolution Once the issue was identified, we implemented multiple performance optimizations to reduce unnecessary processing and improve throughput, including: * Skipping workflows that did not apply to the triggering event before running expensive queries. * Reducing redundant queries where only a single result was required. * Improving the overall efficiency of the automation workflow. These changes significantly reduced system load, allowed processing queues to catch up, and restored real‑time workflow execution. Service levels returned to normal by **January 23, 2026**, and the system has remained stable since. ## Preventative Actions To prevent similar incidents in the future, we have taken and are continuing the following actions: * **Improved monitoring and alerting** for automation workflow latency, enabling earlier detection before customer impact. * **Hardened automation workflow performance**, ensuring the system can safely handle large numbers of workflows without unnecessary processing. * **Reviewed and updated testing strategies** to better reflect real‑world production workloads and edge cases. * **Ongoing optimization work** to further improve the scalability and resilience of the automation system. * **Evaluation of capacity and scaling behavior** to ensure consistent performance during peak and non‑peak hours. These measures are already in place or actively underway and are designed to ensure automation workflows continue to operate reliably as usage grows. We appreciate your trust and patience, and we’re committed to continuously improving the reliability and performance of the automation experience.

Read the full incident report →

Started Jan 21, 2026, 10:08 PM UTC· resolved Jan 22, 2026, 04:04 PM UTC

1. investigating Jan 21, 2026, 10:08 PM UTC

   We became aware of an issue where automation workflows are not triggering starting around 1/21/2026 at 9:40am PT. We are currently investigating and will provide an update as soon as possible.

2. investigating Jan 22, 2026, 01:55 AM UTC

   We are continuing to investigate this issue. We have found that automation workflows are still processing with a delay. New information will be shared as soon as possible.

3. investigating Jan 22, 2026, 01:57 AM UTC

   We are continuing to investigate this issue.

4. monitoring Jan 22, 2026, 01:14 PM UTC

   This issue has been resolved and our teams are monitoring to ensure continued stability

5. resolved Jan 22, 2026, 04:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 21, 2026, 07:01 PM UTC· resolved Jan 26, 2026, 06:58 PM UTC

1. investigating Jan 21, 2026, 07:01 PM UTC

   We are aware of an issue impacting Adobe offer letter packet generation that may produce the error: “Error sending offer packet: /public/oauth APIs are not allowed to access for this application.” Our Engineering team is actively investigating and working toward a fix.

2. investigating Jan 21, 2026, 07:01 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jan 22, 2026, 01:05 PM UTC

   The issue has been resolved and our teams are monitoring to ensure continued stability.

4. identified Jan 22, 2026, 01:13 PM UTC

   The issue has been identified and our Engineers are working on a solution. We will provide further updates as soon as available.

5. identified Jan 22, 2026, 10:01 PM UTC

   Our Engineering team is actively working on a fix for this issue. We will update the status once a deployment timeline is confirmed.

6. identified Jan 23, 2026, 05:24 PM UTC

   Our team has identified the root cause of the issue and is currently validating and testing to ensure a complete and stable resolution. We are actively working to complete this phase as quickly as possible. Our next update will be provided by 5:00 PM ET. Thank you for your patience while we work to restore full functionality.

7. identified Jan 23, 2026, 09:49 PM UTC

   Our team is continuing to test and validate the proposed fix to ensure it fully resolves the issue and maintains system stability. This phase is still in progress, and we are working diligently to complete it as quickly as possible. Thank you for your continued patience as we work to restore full functionality.

8. monitoring Jan 24, 2026, 04:02 AM UTC

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

9. resolved Jan 26, 2026, 06:58 PM UTC

   This incident has been resolved. Please follow up with the Lever Support team if you encounter continued disruptions when attempting Adobe Sign supported sendings.

Read the full incident report →

Started Jan 20, 2026, 04:52 PM UTC· resolved Jan 20, 2026, 07:51 PM UTC

1. investigating Jan 20, 2026, 04:52 PM UTC

   We are currently investigating an issue that is intermittently affecting the candidate pipeline tab in Lever. Issues impacting access to the hire.lever.co/candidates were noticed around 8 am Pacific time. Users may intermittently experience 500 errors when navigating to the candidate pipeline page. Our Engineering teams are actively working to resolve this as soon as possible.

2. monitoring Jan 20, 2026, 05:13 PM UTC

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

3. resolved Jan 20, 2026, 07:51 PM UTC

   The issue with 500 errors for some users accessing the 'candidates' tab has been resolved. The incident occurred from 8 am Pacific time until 9 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

Read the full incident report →

Started Jan 06, 2026, 10:52 AM UTC· resolved Jan 06, 2026, 01:51 PM UTC

1. investigating Jan 06, 2026, 10:52 AM UTC

   We are investigating an issue where resumes are not loading, offers are not displaying, and errors occur when manually adding resumes to opportunities. Our team is actively working to identify the root cause and restore normal functionality.

2. monitoring Jan 06, 2026, 12:47 PM UTC

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

3. resolved Jan 06, 2026, 01:51 PM UTC

   This incident has been resolved.

4. postmortem Jan 21, 2026, 03:26 PM UTC

   We understand how important this functionality is to your hiring workflows, and our team moved quickly to investigate and address the issue. We can confirm this issue has been fully resolved, and our team has taken steps to ensure system stability moving forward. ## Customer Impact * On January 6th, 2026, between 15:07 and 18:20 \(UTC\), users were **unable to upload resumes or documents** in Lever ATS. * Upload attempts failed with an authorization-related error. * Any new uploads during the incident window may result in references to non-existent files within the ATS. Unfortunately, these files are not recoverable. * Other areas of the application continued to function normally. ## Root Cause The incident was caused by an updated **configuration in Amazon S3 access policies** following a security-related infrastructure change. As part of a security initiative, an existing IAM policy condition was updated in accordance with an AWS-recommended best practice. While this change was intended to improve security, the revised policy **did not behave as expected in our environment**, resulting in S3 denying permission for file uploads. Because file uploads rely on this S3 permission, customers encountered authorization errors when uploading resumes and documents. ## Resolution Once the issue was identified, the infrastructure team **reverted the policy change** to the previously functioning configuration. After the rollback: * File uploads resumed successfully * Error rates returned to normal levels * Customer impact was fully resolved The system was verified as restored by confirming: * Successful resume uploads from the application * Elimination of S3 authorization errors in logs and dashboards Invalid file reference cleanup * Our Engineering teams are in the process of removing any invalid references to files that were not successfully uploaded during this time ## Preventative Actions To reduce the likelihood of similar issues in the future, we are implementing the following improvements: 1. **Post-Deployment Monitoring** * Enhanced monitoring after infrastructure and security-related changes in production 2. **Automated Alerts** * Alerts for elevated file-upload failures and S3 authorization errors to reduce detection time 3. **Change Validation** * Additional validation and testing of IAM policy changes, especially those involving AWS-recommended updates 4. **Documentation & Review** * Improved documentation and cross-team review for security-driven infrastructure changes These steps will help detect issues sooner and minimize customer impact in the event of future changes.

Read the full incident report →