- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Silo 1
- Down Index
- 28of 100
What to do
Check whether you use Greenhouse Silo 1. 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 1h 19m it lasted.
Anything that failed between 2026-05-07 22:23 UTC and 2026-05-07 23:42 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 4
- investigating
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.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-b90f632d2f
Is Greenhouse still down?
No, this incident was resolved 2026-05-07 23:42 UTC. For Greenhouse's live state, see https://down.guide/greenhouse.
How long did it last?
1h 19m, from 2026-05-07 22:23 UTC to 2026-05-07 23:42 UTC, by the times Greenhouse posted.
What was affected?
Greenhouse named Silo 1.
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.