- Detected by Pingoru
- Oct 06, 2026, 06:55 PM UTC
- Resolved
- Oct 06, 2026, 07:02 PM UTC
- Duration
- 6m
Affected: Greenhouse Voice AI
Timeline · 2 updates
-
investigating Oct 06, 2026, 06:55 PM 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.
-
resolved Oct 06, 2026, 07:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 02:25 PM UTC
- Resolved
- Sep 25, 2026, 03:17 PM UTC
- Duration
- 51m
Affected: Silo 101Silo 201
Timeline · 5 updates
-
investigating Sep 25, 2026, 02:25 PM 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.
-
monitoring Sep 25, 2026, 02:42 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Sep 25, 2026, 02:55 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Sep 25, 2026, 03:09 PM UTC
We are continuing to monitor for any further issues.
-
resolved Sep 25, 2026, 03:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2026, 11:19 AM UTC
- Resolved
- Sep 22, 2026, 02:05 PM UTC
- Duration
- 2h 45m
Affected: Greenhouse Job Boards
Timeline · 3 updates
-
investigating Sep 22, 2026, 11:19 AM 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.
-
monitoring Sep 22, 2026, 12:01 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 22, 2026, 02:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 05:55 PM UTC
- Resolved
- Sep 22, 2026, 12:03 PM UTC
- Duration
- 18h 7m
Affected: Greenhouse Job Boards
Timeline · 2 updates
-
identified Sep 21, 2026, 05:55 PM 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.
-
resolved Sep 22, 2026, 12:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 04:37 PM UTC
- Resolved
- Sep 21, 2026, 05:15 PM UTC
- Duration
- 38m
Affected: MyGreenhouse
Timeline · 3 updates
-
investigating Sep 21, 2026, 04:37 PM UTC
Job search is not currently for job seekers on MyGreenhouse.
-
identified Sep 21, 2026, 04:50 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Sep 21, 2026, 05:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2026, 11:21 AM UTC
- Resolved
- Sep 08, 2026, 01:50 PM UTC
- Duration
- 2h 29m
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 4 updates
-
investigating Sep 08, 2026, 11:21 AM UTC
We are currently investigating this issue.
-
identified Sep 08, 2026, 11:48 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 08, 2026, 01:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 08, 2026, 01:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 12:43 PM UTC
- Resolved
- Sep 04, 2026, 01:29 PM UTC
- Duration
- 46m
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 3 updates
-
identified Sep 04, 2026, 12:43 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 04, 2026, 12:43 PM UTC
The errors coming from Outlook servers appear to have resolved. We will continue to monitor.
-
resolved Sep 04, 2026, 01:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 11:57 PM UTC
- Resolved
- Sep 04, 2026, 02:01 PM UTC
- Duration
- 14h 3m
Affected: Greenhouse Job Boards
Timeline · 3 updates
-
investigating Sep 03, 2026, 11:57 PM UTC
Security code emails for Greenhouse Job Applications have been temporarily disabled for candidates who fail CAPTCHA.
-
monitoring Sep 04, 2026, 01:33 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 04, 2026, 02:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 09:20 AM UTC
- Resolved
- Sep 03, 2026, 11:50 AM UTC
- Duration
- 2h 29m
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 4 updates
-
investigating Sep 03, 2026, 09:20 AM UTC
We are currently investigating this issue.
-
identified Sep 03, 2026, 09:39 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 03, 2026, 10:54 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 03, 2026, 11:50 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 08:06 AM UTC
- Resolved
- Sep 02, 2026, 08:32 AM UTC
- Duration
- 26m
Affected: Silo 201
Timeline · 2 updates
-
investigating Sep 02, 2026, 08:06 AM 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 have more information.
-
resolved Sep 02, 2026, 08:32 AM UTC
A fix has been implemented. All services are returned to normal.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 06:58 PM UTC
- Resolved
- Sep 03, 2026, 08:00 PM UTC
- Duration
- 43d 1h
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Outlook 365Silo 101Silo 201
Timeline · 4 updates
-
investigating Jul 22, 2026, 06:58 PM 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.
-
identified Aug 07, 2026, 02:30 PM 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.
-
identified Sep 02, 2026, 06:37 PM 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 with a small group of affected customers, and we are working to make it available more broadly. We will share an update as soon as it is ready. Thank you for your patience.
-
resolved Sep 03, 2026, 08:00 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 08:29 PM UTC
- Resolved
- Jul 10, 2026, 09:25 PM UTC
- Duration
- 56m
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 3 updates
-
investigating Jul 10, 2026, 08:29 PM 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.
-
monitoring Jul 10, 2026, 09:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 10, 2026, 09:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 10:13 PM UTC
- Resolved
- Jul 06, 2026, 10:28 PM UTC
- Duration
- 15m
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 3 updates
-
investigating Jul 06, 2026, 10:13 PM UTC
We are currently investigating this issue.
-
monitoring Jul 06, 2026, 10:22 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 06, 2026, 10:28 PM UTC
The token refresh server has been repaired.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 05:00 PM UTC
- Resolved
- Jul 06, 2026, 08:35 PM UTC
- Duration
- 4d 3h
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 2 updates
-
investigating Jul 02, 2026, 05:00 PM 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.
-
resolved Jul 06, 2026, 08:35 PM UTC
We appreciate your patients. Sterling background checks are now fully functional.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 05:16 PM UTC
- Resolved
- Jun 29, 2026, 08:44 PM UTC
- Duration
- 3h 27m
Affected: HRIS Link - Workday
Timeline · 4 updates
-
investigating Jun 29, 2026, 05:16 PM UTC
We are currently investigating this issue.
-
identified Jun 29, 2026, 05:28 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 29, 2026, 08:16 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 29, 2026, 08:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 01:24 PM UTC
- Resolved
- Jun 26, 2026, 03:25 PM UTC
- Duration
- 2h
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 4 updates
-
investigating Jun 26, 2026, 01:24 PM UTC
We are currently investigating this issue.
-
identified Jun 26, 2026, 01:30 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 26, 2026, 02:58 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 26, 2026, 03:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 05:24 PM UTC
- Resolved
- Jun 19, 2026, 10:24 PM UTC
- Duration
- 4h 59m
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 5 updates
-
investigating Jun 19, 2026, 05:24 PM UTC
We are currently investigating an issue where emails may not be sent for customers using custom SMTP routes with Microsoft 365.
-
identified Jun 19, 2026, 06:39 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 19, 2026, 09:49 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 19, 2026, 10:23 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 19, 2026, 10:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 12:35 PM UTC
- Resolved
- Jun 18, 2026, 01:02 PM UTC
- Duration
- 27m
Affected: Silo 1
Timeline · 2 updates
-
investigating Jun 18, 2026, 12:35 PM UTC
We are currently experiencing a delay for Silo 1 in BIC data delivery.
-
resolved Jun 18, 2026, 01:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 12:55 PM UTC
- Resolved
- Jun 18, 2026, 07:57 AM UTC
- Duration
- 19h 2m
Affected: Silo 1Silo 2Silo 3Silo 4Silo 5Silo 6Silo 7Silo 8Silo 9Silo 101Silo 201
Timeline · 5 updates
-
investigating Jun 17, 2026, 12:55 PM UTC
We are currently experiencing a delay across all silos in BIC data delivery.
-
identified Jun 17, 2026, 02:10 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Jun 17, 2026, 09:03 PM UTC
We are continuing to work on a fix for this issue.
-
identified Jun 18, 2026, 07:57 AM UTC
We are continuing to work on a fix for this issue.
-
resolved Jun 18, 2026, 07:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 07:47 PM UTC
- Resolved
- Jun 12, 2026, 12:40 AM UTC
- Duration
- 4h 52m
Affected: Greenhouse - Other
Timeline · 2 updates
-
monitoring Jun 11, 2026, 07:47 PM 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 incident and will share updates as we learn more.
-
resolved Jun 12, 2026, 12:40 AM UTC
DocuSign has marked the incident as resolved. If you experienced issues with DocuSign-related workflows earlier, please retry the affected action.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 09:57 PM UTC
- Resolved
- Jun 05, 2026, 10:00 PM UTC
- Duration
- 3m
Affected: Greenhouse Onboarding
Timeline · 2 updates
-
monitoring Jun 05, 2026, 09:57 PM 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.
-
resolved Jun 05, 2026, 10:00 PM UTC
ADP has reverted their change. All exports should now work as normal.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 04:23 PM UTC
- Resolved
- May 28, 2026, 06:29 PM UTC
- Duration
- 2h 5m
Affected: Adobe Acrobat Sign
Timeline · 2 updates
-
investigating May 28, 2026, 04:23 PM 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.
-
resolved May 28, 2026, 06:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 03:08 PM UTC
- Resolved
- May 28, 2026, 11:34 AM UTC
- Duration
- 20h 26m
Affected: ReadMe ReadMe Hubs - Harvest API docs hosting
Timeline · 3 updates
-
investigating May 27, 2026, 03:08 PM UTC
Harvest API documentation site is currently experiencing an outage. Our documentation vendor is currently working to fix the issue.
-
investigating May 27, 2026, 09:16 PM UTC
We are continuing to investigate this issue.
-
resolved May 28, 2026, 11:34 AM UTC
Their outage has been resolved
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 03:49 PM UTC
- Resolved
- May 22, 2026, 04:25 PM UTC
- Duration
- 36m
Affected: Silo 7Silo 8Silo 9
Timeline · 3 updates
-
investigating May 22, 2026, 03:49 PM 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.
-
resolved May 22, 2026, 04:25 PM 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.
-
postmortem May 27, 2026, 02:39 PM 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 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.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 03:05 PM UTC
- Resolved
- May 20, 2026, 03:41 PM UTC
- Duration
- 35m
Affected: Silo 1
Timeline · 2 updates
-
investigating May 20, 2026, 03:05 PM UTC
Some customers are experiencing timeouts and errors when making requests to Harvest v3 on Silo 1. We are currently investigating this issue.
-
resolved May 20, 2026, 03:41 PM UTC
This incident has been resolved.
Read the full incident report →