- Level
- confirmed
- Worst impact
- Degraded
- Components
- Silo 1, Silo 2, Silo 3, Silo 4, Silo 5, Silo 6, Silo 7, Silo 8, Silo 9, Silo 101, Silo 201
- Down Index
- 25of 100
What to do
Check whether you use Greenhouse Silo 1, Silo 2, Silo 3, Silo 4 and 7 more. 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 10h 27m it lasted.
Anything that failed between 2026-03-10 13:42 UTC and 2026-03-11 00:09 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 3
- identified
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.
provider
- identified
At this point, all silos besides 1, 2, and 3 have completed their sync.
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-3babd4479a
Is Greenhouse still down?
No, this incident was resolved 2026-03-11 00:09 UTC. For Greenhouse's live state, see https://down.guide/greenhouse.
How long did it last?
10h 27m, from 2026-03-10 13:42 UTC to 2026-03-11 00:09 UTC, by the times Greenhouse posted.
What was affected?
Greenhouse named Silo 1, Silo 2, Silo 3, Silo 4 and 7 more.
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.