- 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
- Down Index
- 24of 100
What to do
Check whether you use Greenhouse Silo 1, Silo 2, Silo 3, Silo 4 and 6 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 6h 54m it lasted.
Anything that failed between 2026-02-14 14:26 UTC and 2026-02-14 21:20 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
- investigating
We are experiencing delays in updates to the Business Intelligence Connector data. Customers using BIC will not have up-to-date data available in these tables. We are currently investigating the issue and will provide updates shortly.
provider
- identified
The issue has been identified and a fix is being implemented.
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-64c7c44186
Is Greenhouse still down?
No, this incident was resolved 2026-02-14 21:20 UTC. For Greenhouse's live state, see https://down.guide/greenhouse.
How long did it last?
6h 54m, from 2026-02-14 14:26 UTC to 2026-02-14 21:20 UTC, by the times Greenhouse posted.
What was affected?
Greenhouse named Silo 1, Silo 2, Silo 3, Silo 4 and 6 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.