Greenhouse outage on 12 November 2026
An email when it goes down, and when it’s back.
“Emails sent from Greenhouse may not have been logged to the Activity Feed”
From 12 November at 18:13 UTC until 16 November at 11:53 UTC (about 89 hours 40 minutes), Greenhouse had problems with its Outlook calendar integrations for scheduling, with error rates of 10–15%. Affected features included loading calendars and free/busy times, creating, cancelling and rescheduling interviews, candidate self-scheduling, and syncing changes from Outlook. Emails sent from Greenhouse may also not have been logged to the Activity Feed. The status page said errors were decreasing by 13 November at 12:59 UTC, and it attributed the problem to an issue Microsoft was working through. Claude, Litmus, U-Haul, GoDaddy, OpenAI and GitHub also reported problems at the same time.
Greenhouse’s own incident page ↗- When
- 18:13–11:53 UTC
- How long
- 3 days
- Incident open on its page
- 18:12–11:52 UTC
- Components affected
- 1
- Greenhouse, 30 days before
- 1 other outage
What broke when
From Greenhouse’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 1793 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Cause identified
- Third-Party Dependencies - Outlook 365: degraded performance
- Resolved
- Third-Party Dependencies - Outlook 365: back to normal
Where this comes from
Stackpulse reads Greenhouse’s official status page at status.greenhouse.io every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with Greenhouse. Names and logos belong to their owners.