- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Greenhouse. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-05-15 19:08 UTC and 2026-05-15 09:00 UTC may need a replay.Subscribe to Greenhouse's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=greenhouse works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Greenhouse 1
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-6ca321594c
Is Greenhouse still down?
No, this incident was resolved 2026-05-15 09:00 UTC. For Greenhouse's live state, see https://down.guide/greenhouse.
How long did it last?
0m, from 2026-05-15 19:08 UTC to 2026-05-15 09:00 UTC, by the times Greenhouse posted.
What caused it?
Greenhouse hasn't published a root cause. If it does, it shows here.
Where does this come from?
Greenhouse's official status page, https://status.greenhouse.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.