Historial de interrupciones de Lever

1. 26 de agosto de 2026 a las 16:24 UTCresolved

   A las 8:30 horas UTC el 8/25/2026 una rotación programada del servidor en https://hire.eulever.co/ causó mayor latencia y algunas cargas de página fallidas hasta las 9:15am UTC. Los usuarios afectados notarán un "error 504" durante las cargas de la página afectada. El servicio fue restaurado a todos los usuarios a partir de las 9:15am UTC el 8/25/2026. Un RCA completo se publicará en este número dentro de 7 a 10 días hábiles.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de agosto de 2026 a las 20:12 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 21 de agosto de 2026 a las 20:29 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 24 de agosto de 2026 a las 14:16 UTCresolved

   Estado: Resuelvado Nuestro monitoreo ha confirmado que no hay más problemas relacionados con este incidente. El servicio ha permanecido estable y el incidente se considera resuelto. Se proporcionará un análisis de causa raíz (RCA) dentro de 7-10 días hábiles.

Traducido automáticamente desde la actualización oficial del incidente.

1. 12 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 16:38 UTCinvestigating

   Edición: Somos conscientes de una salida activa con Adobe Sign, un proveedor de firma electrónica de terceros. Esto está afectando a los clientes de Lever que utilizan la integración de Adobe Sign. Impacto del cliente: El equipo puede ser incapaz de generar o enviar cartas para la firma electrónica a través de Adobe Sign. Los candidatos con solicitudes pendientes de Adobe Sign pueden ser incapaces de firmar en este momento. Los clientes que usan DocuSign y todas las demás funcionalidades de Lever no son afectados. Estado: Investigación. Esta es una cuestión de arriba con Adobe; estamos monitoreando y actualizaremos como Adobe proporciona más información. Para actualizaciones directas de Adobe, consulte su página de estado en https://status.adobe.com/

2. 7 de agosto de 2026 a las 17:11 UTCinvestigating

   Actualización — Oferta Carta Enviar Disrupción Edición: Hemos identificado que esta perturbación es más amplia que inicialmente. El outage de Adobe está impactando nuestro proceso de conversión de PDF, que todas las cartas ofrecen — independientemente del proveedor de la firma electrónica (Adobe Sign, DocuSign o Native eSignature)— dependen de generar el documento final. Impacto del cliente: Actualmente todos los clientes no pueden enviar cartas de oferta con éxito. Esto ya no se limita a los usuarios de integración de Adobe Sign. Los reclutadores que intentan generar o enviar una carta de oferta pueden ver fallos o retrasos, independientemente del método de asignación electrónica que se configura en su cuenta. Estado: Investigación.

3. 7 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de julio de 2026 a las 14:47 UTCinvestigating

   Cuestión: Estamos investigando lo que parece ser una cuestión de toda la plataforma en la que no se envían cartas. Impacto del cliente: El programa no puede generar o entregar correos electrónicos a los candidatos. Situación actual: Ingeniería está investigando activamente. No hay solución de trabajo disponible en este momento.

2. 14 de julio de 2026 a las 16:24 UTCmonitoring

   Edición: Identificamos una cuestión de toda la plataforma en la que no se enviaron cartas. Impacto del cliente: El equipo no pudo generar o entregar correos electrónicos a los candidatos. Situación actual: Se ha mitigado la cuestión inmediata. Estamos monitoreando activamente para confirmar la plena resolución y estabilidad.

3. 14 de julio de 2026 a las 23:50 UTCresolved

   Edición: Identificamos una cuestión de toda la plataforma en la que no se enviaron cartas. Impacto del cliente: El equipo no pudo generar o entregar correos electrónicos a los candidatos. Estado: Resuelto. Un RCA estará disponible dentro de 7-10 días hábiles.

4. 22 de julio de 2026 a las 13:20 UTCpostmortem

   ** Resumen del incidente** Entre el 13 de julio y el 14 de julio de 2026, algunos clientes fueron intermitentemente incapaces de enviar cartas de oferta, y algunos documentos/reconocimientos no generaron. Mientras que los archivos fuente fueron subidos con éxito, el paso de conversión requerido para previsualizaciones y generación de oferta falló. No se produjo pérdida de datos. **Detección** La cuestión fue identificada el 14 de julio de 2026, aproximadamente a las 10:43 AM ET, siguiendo informes de clientes a nuestro equipo de soporte. La ingeniería confirmó el impacto mediante la vigilancia, lo que mostró un aumento constante de los procesos cuenta dentro del servicio converter de documentos hasta que alcanzó un límite de sistema duro, causando que las tareas posteriores fallaran. *Causa real* El incidente fue causado por una "pérdida de procesamiento" introducida durante una actualización reciente de la plataforma. Un cambio en cómo el sistema maneja las conversiones de documentos significaba que cada conversión comenzó un nuevo proceso de fondo que nunca fue debidamente cerrado. Durante varios días, estos procesos de fondo se acumularon hasta que el sistema alcanzó su máxima capacidad. Una vez alcanzado este límite, el servicio ya no pudo iniciar los nuevos procesos necesarios para generar cartas de oferta o previsualizaciones de documentos. **Resolución** * ** Mitigación interior* A las 11:20 AM ET el 14 de julio, los ingenieros reanudaron las cápsulas de servicio afectadas. Esto despejó los procesos de fondo acumulados y restauró inmediatamente la capacidad de los clientes para enviar cartas de oferta y ver previsiones. * **Permanent Fix:** Una actualización de código fue desarrollada y desplegada a las 8:43 PM ET el 14 de julio. Esta solución garantiza que todos los procesos de fondo estén correctamente terminados y limpiados después de cada conversión, evitando cualquier acumulación futura. Medidas preventivas** * ** Mejoras del proyecto:** Implementado un robusto sistema de gestión de procesos \(utilizando un proceso "reaper"\) para asegurar que todas las tareas de fondo se cierren automáticamente al finalizar. * ** Vigilancia mejorada** Se han configurado nuevas alertas automatizadas para notificar al equipo de ingeniería si el uso del proceso supera el 50% del límite del sistema. Esto nos permitirá identificar y resolver pérdidas de recursos similares días antes de que impacten a los clientes. * **Procesamiento de Backlog:** Se completó una iniciativa separada para identificar y reprocesar cualquier documento o reanudar las previsiones que no generaron durante la ventana de salida para asegurar que todos los previsualizaciones estén disponibles para los usuarios.

Traducido automáticamente desde la actualización oficial del incidente.

1. 13 de julio de 2026 a las 18:04 UTCinvestigating

   Estamos investigando un problema que afecta la autenticación de Nylas. Los usuarios pueden experimentar un mensaje de error "Unknown error" al intentar restablecer permisos de integración de correo electrónico/calendar. Hora de inicio: 10:10 am PT Siguiente actualización: 1:00 pm PT o antes.

2. 13 de julio de 2026 a las 19:57 UTCinvestigating

   Seguimos investigando esta cuestión. Siguiente actualización: 3:00 pm PT o antes.

3. 13 de julio de 2026 a las 21:59 UTCidentified

   Seguimos investigando esta cuestión. Siguiente actualización: 5:00 PM PT

4. 14 de julio de 2026 a las 0:28 UTCmonitoring

   Se han aplicado medidas de mitigación y la funcionalidad de servicio está volviendo a la normalidad. Estamos monitoreando el rendimiento y la estabilidad. Siguiente actualización: sobre resolución.

5. 14 de julio de 2026 a las 13:08 UTCresolved

   Edición Descripción: Los usuarios pueden haber recibido un "error desconocido" al intentar enviar correos electrónicos o sincronizar su correo electrónico y calendario de Microsoft en Lever. Impacto del cliente: Los usuarios afectados no pudieron autenticar sus integraciones de correo electrónico y calendario de Microsoft, bloqueando el correo electrónico envía a los candidatos y la funcionalidad de sincronización del calendario crítica para la contratación de flujos de trabajo. Estado: Resuelto - Correo electrónico envía y sincronización calendario están funcionando normalmente. Un RCA estará disponible dentro de 7-10 días hábiles.

6. 22 de julio de 2026 a las 13:19 UTCpostmortem

   ** Resumen del incidente** El 13 de julio de 2026, los clientes que utilizan Microsoft \(Office 365\) para la integración de correo electrónico y calendario experimentaron interrupciones de servicio. Los usuarios afectados no pudieron autorizar o reautorizar sus conexiones de correo electrónico y calendario dentro de Lever, a menudo encontrando un mensaje de "error desconocido". Además, correos electrónicos externos enviados a través de la integración de Microsoft no pudo entregar durante este período. Los servicios de correo electrónico y calendario basados en Google permanecieron plenamente operativos y no se vieron afectados por este incidente. **Detección** El tema fue identificado el 13 de julio de 2026, a las 2:22 PM ET, siguiendo informes de clientes a nuestro equipo de soporte. Tras la investigación, el equipo de ingeniería confirmó los fallos e inició una respuesta de alta prioridad. Mientras que la caducidad técnica subyacente ocurrió el 12 de julio de 2026, el impacto se hizo visible ya que los usuarios intentaron refrescar permisos o enviar comunicaciones externas al día siguiente. *Causa real* El incidente fue causado por la expiración de una credencial de seguridad digital utilizada para comunicarse de forma segura con Microsoft. Esta credencial actúa como una "palabra" segura que permite a nuestros sistemas sincronizar datos de correo electrónico y calendario. Debido a que esto era una credencial compartida utilizada para la integración de Microsoft, la caducidad afectaba a los clientes usando Office 365 ampliamente en lugar de una cuenta específica. **Resolución** Para resolver el problema, nuestro equipo de ingeniería generó una nueva credencial de seguridad y actualizó los ajustes de integración en nuestros entornos. Una vez que el nuevo credencial propagado a través del sistema, el servicio fue totalmente restaurado. La restauración fue verificada a través de pruebas internas y confirmada por reautorizaciones exitosas del cliente por 8:28 PM ET el 13 de julio de 2026. No se produjeron pérdidas de datos como resultado de este incidente. Medidas preventivas** Para evitar la repetición de esta cuestión, estamos implementando las siguientes mejoras: * **Automated Expiry Tracking:** Estamos estableciendo un proceso formal de seguimiento de todas las credenciales de integración con recordatorios automatizados bien establecidos antes de las fechas de vencimiento. * ** Vigilancia activa:** Se ha configurado un nuevo aviso para detectar picos en fallas de autorización, permitiendo a nuestro equipo identificar y resolver problemas similares antes de que impacten a los clientes.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de julio de 2026 a las 17:17 UTCidentified

   En 7-3-2026 nos dieron cuenta de un problema que afecta a las instancias de Lever con autenticación de Nylas (generalmente utilizado para clientes con servicios de correo electrónico/calendar de Microsoft Exchange on-premise). Sólo la autenticación de Nylas es impactada, no se ha observado ningún comportamiento similar para los clientes autenticando con los servicios de Office 365 o Google. Los usuarios pueden experimentar un mensaje de "500 errores" al intentar restablecer permisos de correo electrónico/calendar y hemos observado varios bucles de correo electrónico inesperados que hacen que los candidatos reciban correos electrónicos duplicados cada 10 a 15 minutos como resultado de este número. 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). La versión de seguridad v24.17.0 (CVE-2026-48931) cambió `http.Agent `manejo de toma de corriente continua para que `node-fetch` lanza `ERR STREAM PREMATURE CLOSE` ("Premature close") en las respuestas a proveedores externos (Nylas/Google). Nuestros servicios lo recogieron a través de la migración Node 18→24 (Ocurrida el 06-30-2026). El fallo fue fijado aguas arriba en Nodo 24.18.0 Esta cuestión debe fijarse en un despliegue hoy (7-8-2026). Proporcionaremos actualizaciones sobre el estado de emisión y el plazo de despliegue lo antes posible.

2. 8 de julio de 2026 a las 20:03 UTCmonitoring

   Una solución se ha implementado a partir de aproximadamente 12:15pm PST/PDT en 7/8/2026. El correo electrónico y la sincronización Calendario ahora son totalmente funcionales para las instancias Lever configuradas con la autenticación de Nylas. Seguimos monitoreando la eficacia de la solución. A Root Cause Analysis (RCA) will be published to this issue within the standard Service Level Agreement.

3. 9 de julio de 2026 a las 16:19 UTCresolved

   Este incidente está resuelto. A Root Cause Analysis (RCA) se publicará en este número dentro de 7-10 días hábiles.

4. 9 de julio de 2026 a las 20:43 UTCpostmortem

   ** Resumen del incidente** Entre el 2 de julio de 2026 y el 8 de julio de 2026, Algunos clientes experimentaron fallos intermitentes que afectan los servicios de correo electrónico y calendario. Los impactos primarios incluyeron errores al enviar o sincronizar correos electrónicos y ocasionalmente "500 errores" durante el inicio de sesión. Estos problemas fueron causados por una regresión técnica en el entorno de tiempo de ejecución subyacente \(Node.js\) que maneja conexiones externas a servicios de terceros. Para un subconjunto de clientes que utilizan ajustes específicos de integración de correo electrónico, la inestabilidad de conexión causó que el sistema percibiera incorrectamente un correo electrónico exitoso enviar como un fracaso. Esto generó un mecanismo automatizado de reingreso, que en algunos casos dio lugar a un "retry loop" donde la misma comunicación fue reenviada a los receptores a intervalos regulares hasta que se estabilitó la conexión. **Detección** La cuestión se identificó tras los informes de interrupciones intermitentes de los servicios. Nuestros equipos de apoyo e ingeniería llevaron a cabo una investigación exhaustiva de estos informes, identificando un patrón específico de fallas de conexión dentro de nuestros registros del sistema. Otros análisis confirmaron que el impacto comenzó aproximadamente el 2 de julio de 2026, tras una actualización rutinaria a nuestra infraestructura de servicio. *Causa real* La causa raíz fue un defecto en una versión específica de Node.js \(versión 24.17.0\), el entorno de software utilizado para ejecutar nuestros servicios. Esta versión contenía un defecto en cómo gestionaba las conexiones "de mantenimiento", conexiones reutilizables para comunicarse con servicios externos. En ciertas condiciones, el software cerraría prematuramente estas conexiones antes de completar una tarea, lo que resulta en envíos de correo electrónico fallidos y errores de sincronización de datos. **Resolución** Para resolver el problema, nuestro equipo de ingeniería realizó los siguientes pasos: * **Identificación:** Correlacionó los errores de "Prematura cercana" a una regresión conocida en el tiempo de ejecución Node.js. * Upgrade* Actualizado nuestras imágenes del sistema base a Node.js versión 24.18.0, que contiene la solución oficial para este problema de conexión. * **Deployment:** Servicios críticos reconstruidos y redistribuidos \(incluyendo componentes de correo electrónico y calendario\) en la versión corregida. * **Verificación** Confirmó que los errores de conexión cesaron y la estabilidad de servicio volvió a niveles normales el 8 de julio de 2026. Medidas preventivas** Para evitar problemas similares en el futuro, estamos implementando las siguientes mejoras: * **Version Pinning:** Hemos actualizado nuestro proceso de construcción para asegurarnos de desplegar sólo versiones que han sido completamente verificadas. * ** Vigilancia mejorada** Estamos agregando alertas específicas para errores de conexión de salida para detectar y responder a fallos de comunicación similares más rápidamente. * ** Pruebas automatizadas* Estamos implementando nuevos cheques sintéticos para la sincronización de correo electrónico y calendario para identificar proactivamente los problemas antes de que impacten a los clientes. * ** Visibilidad mejorada** Estamos actualizando nuestros paneles internos para ofrecer una mejor visibilidad en las versiones exactas de software que se ejecutan en nuestro entorno de producción para acelerar futuros diagnósticos.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 23:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 de abril de 2026 a las 1: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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 17:15 UTCinvestigating

   We are currently investigating this issue.

2. 17 de abril de 2026 a las 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 de abril de 2026 a las 17:36 UTCidentified

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

4. 17 de abril de 2026 a las 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 de abril de 2026 a las 21:11 UTCresolved

   This incident has been resolved.

1. 27 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 14:13 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 26 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 1: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 de febrero de 2026 a las 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 de febrero de 2026 a las 12:33 UTCidentified

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

3. 4 de febrero de 2026 a las 12:37 UTCmonitoring

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

4. 4 de febrero de 2026 a las 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 de enero de 2026 a las 19:04 UTCinvestigating

   We are currently investigating this issue.

2. 30 de enero de 2026 a las 20:38 UTCmonitoring

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

3. 31 de enero de 2026 a las 0:34 UTCresolved

   This incident has been resolved.