Greenhouse

Affected: HRIS Link - UKG

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 22:44 UTC

   We are investigating an issue with the HRIS Link UKG Pro Onboarding Integration

2. identified 2026-10-17 00:05 UTC

   Some customers using the UKG integration may see new hires fail to sync to UKG. Our team has identified the cause and is working on a solution. We are restoring the affected UKG connections and will resend pending hires to UKG. No action is needed from customers at this time.

3. monitoring 2026-10-17 02:01 UTC

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

4. resolved 2026-10-17 04:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 15:32 UTC

   We are currently experiencing a partial disruption affecting 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. monitoring 2026-10-13 15:58 UTC

   A fix has been implemented and we are monitoring the results

3. resolved 2026-10-13 19:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Voice AI

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 18:55 UTC

   We are currently experiencing issues with Voice AI. Users may notice delayed processing of interview evaluations. Our team is actively investigating the issue and working to restore full functionality as quickly as possible.

2. resolved 2026-10-06 19:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Voice AI

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 17:12 UTC

   We are currently experiencing issues with Voice AI. Users may notice delayed processing of interview evaluations. Our team is actively investigating the issue and working to restore full functionality as quickly as possible.

2. resolved 2026-10-01 19:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 101, Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 14:25 UTC

   We are currently experiencing an outage affecting Greenhouse Report Connector. Our team is actively investigating the issue and working to restore full functionality as quickly as possible.

2. monitoring 2026-09-25 14:42 UTC

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

3. monitoring 2026-09-25 14:55 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-09-25 15:09 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-09-25 15:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Job Boards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 11:19 UTC

   We are currently experiencing a partial disruption affecting Indeed applications in Greenhouse Job Boards. 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. monitoring 2026-09-22 12:01 UTC

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

3. resolved 2026-09-22 14:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Job Boards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-21 17:55 UTC

   We are currently experiencing a partial disruption affecting job board updates and tracking links. 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. resolved 2026-09-22 12:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: MyGreenhouse

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 16:37 UTC

   Job search is not currently for job seekers on MyGreenhouse.

2. identified 2026-09-21 16:50 UTC

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

3. resolved 2026-09-21 17:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 11:21 UTC

   We are currently investigating this issue.

2. identified 2026-09-08 11:48 UTC

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

3. monitoring 2026-09-08 13:09 UTC

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

4. resolved 2026-09-08 13:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-04 12:43 UTC

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

2. monitoring 2026-09-04 12:43 UTC

   The errors coming from Outlook servers appear to have resolved. We will continue to monitor.

3. resolved 2026-09-04 13:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Job Boards

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 23:57 UTC

   Security code emails for Greenhouse Job Applications have been temporarily disabled for candidates who fail CAPTCHA.

2. monitoring 2026-09-04 13:33 UTC

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

3. resolved 2026-09-04 14:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 09:20 UTC

   We are currently investigating this issue.

2. identified 2026-09-03 09:39 UTC

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

3. monitoring 2026-09-03 10:54 UTC

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

4. resolved 2026-09-03 11:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 08:06 UTC

   We are currently experiencing a partial disruption affecting Job creation and multiple confirmation emails being sent to candidates. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will provide updates as we...

2. resolved 2026-09-02 08:32 UTC

   A fix has been implemented. All services are returned to normal.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-05 02:18 UTC

   We are currently experiencing a partial disruption affecting searching for a user, processing candidate unhire actions, sending emails and availability requests, submitting referrals, generating offer letters, submitting scorecards, adding candidate notes, and editing interview...

2. identified 2026-08-05 02:40 UTC

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

3. monitoring 2026-08-05 03:56 UTC

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

4. resolved 2026-08-05 13:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Outlook 365, Silo 101, Silo 201

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-22 18:58 UTC

   We are currently experiencing an issue with the Microsoft Teams integration that affects scheduling interviews on shared calendars. Our Engineering team is actively investigating the root cause. We will continue to provide updates as more information becomes available.

2. identified 2026-08-07 14:30 UTC

   It appears that the issue is related to the Graph API. Our engineering team is in contact with Microsoft Support to help them diagnose the problem.

3. identified 2026-09-02 18:37 UTC

   Microsoft has confirmed the root cause is on their side and continues to investigate. While we await a fix from Microsoft, our engineering team has developed a workaround that restores Teams meeting links when scheduling on shared calendars. It has been validated successfully...

4. resolved 2026-09-03 20:00 UTC

   Our engineering team has released a workaround that restores Microsoft Teams links when scheduling on shared calendars. Affected customers have been contacted by Support with next steps. If you continue to experience this issue, please contact Greenhouse Support.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-10 20:29 UTC

   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. monitoring 2026-07-10 21:07 UTC

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

3. resolved 2026-07-10 21:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-06 22:13 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-06 22:22 UTC

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

3. resolved 2026-07-06 22:28 UTC

   The token refresh server has been repaired.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-02 17:00 UTC

   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. resolved 2026-07-06 20:35 UTC

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

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: HRIS Link - Workday

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-29 17:16 UTC

   We are currently investigating this issue.

2. identified 2026-06-29 17:28 UTC

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

3. monitoring 2026-06-29 20:16 UTC

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

4. resolved 2026-06-29 20:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-26 13:24 UTC

   We are currently investigating this issue.

2. identified 2026-06-26 13:30 UTC

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

3. monitoring 2026-06-26 14:58 UTC

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

4. resolved 2026-06-26 15:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-19 17:24 UTC

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

2. identified 2026-06-19 18:39 UTC

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

3. monitoring 2026-06-19 21:49 UTC

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

4. monitoring 2026-06-19 22:23 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-06-19 22:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 12:35 UTC

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

2. resolved 2026-06-18 13:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-17 12:55 UTC

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

2. identified 2026-06-17 14:10 UTC

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

3. identified 2026-06-17 21:03 UTC

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

4. identified 2026-06-18 07:57 UTC

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

5. resolved 2026-06-18 07:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse - Other

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-06-11 19:47 UTC

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

2. resolved 2026-06-12 00:40 UTC

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

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Onboarding

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-06-05 21:57 UTC

   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. resolved 2026-06-05 22:00 UTC

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

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Adobe Acrobat Sign

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-28 16:23 UTC

   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. resolved 2026-05-28 18:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: ReadMe ReadMe Hubs - Harvest API docs hosting

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-27 15:08 UTC

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

2. investigating 2026-05-27 21:16 UTC

   We are continuing to investigate this issue.

3. resolved 2026-05-28 11:34 UTC

   Their outage has been resolved

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 7, Silo 8, Silo 9

Failure mode: A schema or data migration caused the failure. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 15:49 UTC

   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. resolved 2026-05-22 16:25 UTC

   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. postmortem 2026-05-27 14:39 UTC

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

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-20 15:05 UTC

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

2. resolved 2026-05-20 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 19:18 UTC

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

2. investigating 2026-05-19 21:22 UTC

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

3. identified 2026-05-19 21:23 UTC

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

4. monitoring 2026-05-19 22:43 UTC

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

5. resolved 2026-05-19 22:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-15 09:00 UTC

   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.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-11 19:03 UTC

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

2. monitoring 2026-05-11 21:20 UTC

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

3. monitoring 2026-05-11 21:26 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-05-11 21:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-11 19:01 UTC

   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. identified 2026-05-11 19:01 UTC

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

3. monitoring 2026-05-11 20:23 UTC

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

4. resolved 2026-05-11 20:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-07 22:23 UTC

   We are currently experiencing issues with Greenhouse. Users may notice delays posting jobs, scheduling, on webhooks, imports/sync, reports and other async workflows. Our team is actively investigating the issue and working to restore full functionality as quickly as possible.

2. investigating 2026-05-07 22:23 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-05-07 22:51 UTC

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

4. resolved 2026-05-07 23:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-07 15:20 UTC

   We experienced an outage affecting Greenhouse silo 7, 9 and anz. Our team investigated the issue and restored full functionality within 8 minutes.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-05 20:21 UTC

   We are currently experiencing a partial disruption affecting audit log of Greenhouse Harvest API v1 and v2 and BIC. 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...

2. identified 2026-05-05 20:22 UTC

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

3. monitoring 2026-05-05 20:27 UTC

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

4. resolved 2026-05-05 20:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Resume parsing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-31 22:03 UTC

   Talent Matching is experiencing performance degradation. We are currently implementing a fix.

2. resolved 2026-03-31 23:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-31 19:14 UTC

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

2. resolved 2026-04-01 16:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-31 16:23 UTC

   We are investigating reports of errors when using AI features.

2. monitoring 2026-03-31 16:44 UTC

   A fix has been implemented for AI features and we are monitoring the results

3. resolved 2026-03-31 18:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Job Boards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 00:04 UTC

   We are investigating an issue where some live job posts in Greenhouse are not appearing correctly on external job boards and may show as closed or offline.

2. identified 2026-03-25 00:25 UTC

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

3. resolved 2026-03-25 01:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 101

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-23 19:38 UTC

   We have identified an issue where some customers on Silo 101 are unable to connect to the Greenhouse Harvest API.

2. monitoring 2026-03-23 19:42 UTC

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

3. resolved 2026-03-23 21:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-18 15:19 UTC

   Some users are experiencing errors when scheduling interviews. Our team is actively investigating the issue.

2. identified 2026-03-18 15:26 UTC

   The issue has been identified, and the team is working to apply a fix.

3. monitoring 2026-03-18 15:44 UTC

   A fix was applied, and the team is actively monitoring the results.

4. resolved 2026-03-18 17:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Job Boards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-11 14:48 UTC

   We are currently investigating this issue.

2. identified 2026-03-11 14:53 UTC

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

3. monitoring 2026-03-11 14:54 UTC

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

4. resolved 2026-03-11 14:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-10 13:42 UTC

   Data from today's BIC run is stale. We've identified the issue and are in the process of providing the newest set of data.

2. identified 2026-03-10 21:27 UTC

   At this point, all silos besides 1, 2, and 3 have completed their sync.

3. resolved 2026-03-11 00:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Greenhouse Job Boards, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-17 23:33 UTC

   We are investigating an issue causing degraded performance with job boards and errors with search-related requests. Some customers may see slow or incomplete search results.

2. investigating 2026-02-17 23:34 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-02-18 00:05 UTC

   A fix has been implemented, performance and search results should be operating normally . We are closely monitoring performance and will provide a final update once the issue is fully resolved.

4. resolved 2026-02-18 00:18 UTC

   The issue has been resolved and we are no longer seeing any issues with degraded performance.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-14 14:26 UTC

   We are experiencing delays in updates to the Business Intelligence Connector data. Customers using BIC will not have up-to-date data available in these tables. We are currently investigating the issue and will provide updates shortly.

2. identified 2026-02-14 16:26 UTC

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

3. resolved 2026-02-14 21:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: LinkedIn Apply Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-12 18:25 UTC

   We are aware of an issue causing a partial disruption in ingesting job applications where candidate location is required from LinkedIn Apply Connect. Our team is currently investigating.

2. investigating 2026-02-14 14:21 UTC

   We are continuing to investigate this issue.

3. investigating 2026-02-14 15:52 UTC

   We are continuing to investigate this issue. We have engaged LinkedIn to identify the root cause.

4. monitoring 2026-02-17 15:57 UTC

   We are successfully ingesting candidates from LinkedIn, including location information, but are waiting to hear confirmation on a fix from LinkedIn.

5. resolved 2026-02-18 15:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Greenhouse Onboarding

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-10 15:06 UTC

   We are currently experiencing a partial disruption affecting Greenhouse Onboarding, which is impacting some emails sent through the system. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will provide updates...

2. resolved 2026-02-11 15:49 UTC

   This incident has been resolved. We will continue to monitor it closely.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-02 22:23 UTC

   We are currently experiencing a partial disruption affecting the sending of scheduled take home tests. Manually sent take home tests are not impacted. Our team is investigating the issue and working to restore full functionality. We apologize for any inconvenience and will...

2. identified 2026-02-02 23:13 UTC

   Scheduled take-home tests are now functional. Scheduled take-home tests that failed due to this incident are currently being processed.

3. resolved 2026-02-02 23:23 UTC

   This incident has been resolved. All scheduled take-home tests that failed have been successfully delivered.

Excerpts are shortened. Read the full incident on Greenhouse's status page.

Affected: Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Outlook 365, Silo 101, Silo 201

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-23 17:30 UTC

   We are currently experiencing a partial disruption affecting Microsoft Teams as a video conferencing option 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...

2. investigating 2026-01-23 17:31 UTC

   We are continuing to investigate this issue.

3. investigating 2026-01-23 18:15 UTC

   We are continuing to investigate this issue.

4. resolved 2026-01-28 16:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Greenhouse's status page.