Historial de interrupciones de Greenhouse

1. 5 de agosto de 2026 a las 2:18 UTCinvestigating

   Actualmente estamos experimentando una perturbación parcial que afecta a la búsqueda de un usuario, procesando acciones sin trabas candidatas, enviando correos electrónicos y solicitudes de disponibilidad, enviando referencias, generando cartas de oferta, presentando tarjetas de puntuación, agregando notas de candidatos y editando planes de entrevista en Greenhouse. Nuestro equipo está investigando el tema y trabajando para restaurar la funcionalidad completa. Nos disculpamos por cualquier inconveniente y proporcionaremos actualizaciones ya que tenemos más información.

2. 5 de agosto de 2026 a las 2:40 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 5 de agosto de 2026 a las 3:56 UTCmonitoring

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

4. 5 de agosto de 2026 a las 13:29 UTCresolved

   This incident has been resolved.

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

1. 22 de julio de 2026 a las 18:58 UTCinvestigating

   Actualmente estamos experimentando un problema con la integración de Microsoft Teams que afecta la programación de entrevistas en calendarios compartidos. Nuestro equipo de Ingeniería está investigando activamente la causa raíz. Seguiremos proporcionando actualizaciones a medida que se disponga de más información.

2. 7 de agosto de 2026 a las 14:30 UTCidentified

   Parece que el problema está relacionado con la API de Gráficos. Nuestro equipo de ingeniería está en contacto con Microsoft Support para ayudarles a diagnosticar el problema.

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

1. 10 de julio de 2026 a las 20:29 UTCinvestigating

   We are currently experiencing a partial disruption affecting Take Home Tests in Greenhouse Recruiting. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will provide updates as we have more information.

2. 10 de julio de 2026 a las 21:07 UTCmonitoring

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

3. 10 de julio de 2026 a las 21:25 UTCresolved

   This incident has been resolved.

1. 6 de julio de 2026 a las 22:13 UTCinvestigating

   We are currently investigating this issue.

2. 6 de julio de 2026 a las 22:22 UTCmonitoring

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

3. 6 de julio de 2026 a las 22:28 UTCresolved

   The token refresh server has been repaired.

1. 2 de julio de 2026 a las 17:00 UTCinvestigating

   We are currently experiencing a partial disruption affecting Sterling background checks. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will provide updates as we have more information.

2. 6 de julio de 2026 a las 20:35 UTCresolved

   We appreciate your patients. Sterling background checks are now fully functional.

1. 29 de junio de 2026 a las 17:16 UTCinvestigating

   We are currently investigating this issue.

2. 29 de junio de 2026 a las 17:28 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 29 de junio de 2026 a las 20:16 UTCmonitoring

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

4. 29 de junio de 2026 a las 20:44 UTCresolved

   This incident has been resolved.

1. 26 de junio de 2026 a las 13:24 UTCinvestigating

   We are currently investigating this issue.

2. 26 de junio de 2026 a las 13:30 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 26 de junio de 2026 a las 14:58 UTCmonitoring

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

4. 26 de junio de 2026 a las 15:25 UTCresolved

   This incident has been resolved.

1. 19 de junio de 2026 a las 17:24 UTCinvestigating

   We are currently investigating an issue where emails may not be sent for customers using custom SMTP routes with Microsoft 365.

2. 19 de junio de 2026 a las 18:39 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 19 de junio de 2026 a las 21:49 UTCmonitoring

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

4. 19 de junio de 2026 a las 22:23 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 19 de junio de 2026 a las 22:24 UTCresolved

   This incident has been resolved.

1. 18 de junio de 2026 a las 12:35 UTCinvestigating

   We are currently experiencing a delay for Silo 1 in BIC data delivery.

2. 18 de junio de 2026 a las 13:02 UTCresolved

   This incident has been resolved.

1. 17 de junio de 2026 a las 12:55 UTCinvestigating

   We are currently experiencing a delay across all silos in BIC data delivery.

2. 17 de junio de 2026 a las 14:10 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 18 de junio de 2026 a las 7:57 UTCidentified

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

4. 18 de junio de 2026 a las 7:57 UTCresolved

   This incident has been resolved.

1. 11 de junio de 2026 a las 19:47 UTCmonitoring

   We are currently investigating an issue affecting offer workflows that rely on DocuSign. This appears to be related to an outage reported by DocuSign. Customers may experience delays or errors when completing DocuSign-backed offer signing workflows. We are monitoring the vendor incident and will share updates as we learn more.

2. 12 de junio de 2026 a las 0:40 UTCresolved

   DocuSign has marked the incident as resolved. If you experienced issues with DocuSign-related workflows earlier, please retry the affected action.

1. 5 de junio de 2026 a las 21:57 UTCmonitoring

   ADP added some additional validation logic around the State Tax / State Unemployment Insurance (SUI) Tax Code field for New Hire Exports from Greenhouse Onboarding. Exports without this field may be rejected by ADP. They are working on reverting the change.

2. 5 de junio de 2026 a las 22:00 UTCresolved

   ADP has reverted their change. All exports should now work as normal.

1. 28 de mayo de 2026 a las 16:23 UTCinvestigating

   Some customers are experiencing errors while trying to send offers for signature. Adobe is currently experiencing an issue and they are investigating. We will continue to monitor the situation from our side.

2. 28 de mayo de 2026 a las 18:29 UTCresolved

   This incident has been resolved.

1. 27 de mayo de 2026 a las 15:08 UTCinvestigating

   Harvest API documentation site is currently experiencing an outage. Our documentation vendor is currently working to fix the issue.

2. 27 de mayo de 2026 a las 21:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 de mayo de 2026 a las 11:34 UTCresolved

   Their outage has been resolved

1. 22 de mayo de 2026 a las 15:49 UTCinvestigating

   We are currently experiencing an outage affecting Greenhouse Recruiting on silos 7, 8, and 9. Our team is actively investigating the issue and working to restore full functionality as quickly as possible.

2. 22 de mayo de 2026 a las 16:25 UTCresolved

   An issue was identified in testing a new ingress configuration to route traffic into Greenhouse. We have restored the previous configuration and the issue appears to have been resolved.

3. 27 de mayo de 2026 a las 14:39 UTCpostmortem

   **What happened:** During a planned migration process, we hit a scaling limit on a core infrastructure component which impacted certain customer traffic. **Impact:** A portion of customer traffic was dropped causing a full outage for customers on Silos 7, 8, and 9. **Fix:** The migration was rolled back in all customer environments. **Prevention:** The migration has not been reapplied and is on hold, pending further investigation by the team to establish a safe migration path.

1. 20 de mayo de 2026 a las 15:05 UTCinvestigating

   Some customers are experiencing timeouts and errors when making requests to Harvest v3 on Silo 1. We are currently investigating this issue.

2. 20 de mayo de 2026 a las 15:41 UTCresolved

   This incident has been resolved.

1. 19 de mayo de 2026 a las 19:18 UTCinvestigating

   We are currently experiencing a partial disruption affecting Calendly interviews within Greenhouse Recruiting where the "Reschedule" and "Cancel" buttons are not appearing. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will provide updates as we have more information.

2. 19 de mayo de 2026 a las 21:22 UTCinvestigating

   Greenhouse engineers have identified the source of the issue and are currently working on releasing a fix.

3. 19 de mayo de 2026 a las 21:23 UTCidentified

   Greenhouse engineers have identified the source of the issue and are currently working on releasing a fix.

4. 19 de mayo de 2026 a las 22:43 UTCmonitoring

   A fix was released and we are confirming that customer-reported issues have been resolved.

5. 19 de mayo de 2026 a las 22:57 UTCresolved

   This incident has been resolved.

1. 15 de mayo de 2026 a las 19:08 UTCresolved

   This morning, some third-party vendors received task reminder emails for tasks they had already been notified about. This was a one-time occurrence — we expect no additional emails to be sent as a result of this issue.

1. 11 de mayo de 2026 a las 19:03 UTCidentified

   We are currently experiencing a partial disruption affecting job creation with approval custom fields in Greenhouse. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will provide updates as we have more information.

2. 11 de mayo de 2026 a las 21:20 UTCmonitoring

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

3. 11 de mayo de 2026 a las 21:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 11 de mayo de 2026 a las 21:42 UTCresolved

   This incident has been resolved.

1. 11 de mayo de 2026 a las 19:01 UTCinvestigating

   We are currently experiencing a partial disruption affecting offer creation. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will provide updates as we have more information.

2. 11 de mayo de 2026 a las 19:01 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 de mayo de 2026 a las 20:23 UTCmonitoring

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

4. 11 de mayo de 2026 a las 20:50 UTCresolved

   This incident has been resolved.