Greenhouse: Downtime Postmortem - 11:43-11:45AM (ET)
Timeline of updates
- resolved
Our hosting provider Heroku accidentally triggered a database restart on our systems at 11:43AM ET earlier today. This caused a period of unavailability lasting approximately two minutes as our systems automatically cut over to our backup database. No data was lost or changed as a result of the failover to our backup. This restart was triggered without any coordination between Heroku and Greenhouse staff--a state of affairs which is obviously unacceptable for both us and for our customers. We are working closely with Heroku's senior leadership team to ensure this sort of thing does not happen again. Longer-term, we will be moving our database services out of Heroku and onto AWS where we will maintain more control. We apologize for any issues this brief downtime may have precipitated, and deeply appreciate your understanding and your business.
From Greenhouse’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.greenhouse.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Greenhouse, started 2015-01-27 18:25 UTC, resolved after 0 min, 1 update(s).
- Title
- Downtime Postmortem - 11:43-11:45AM (ET)
- Vendor
- Greenhouse
- Date
- URL
- https://rewindex.com/company/greenhouse/incidents/fpd82c46gtlp
Greenhouse profileRecent Greenhouse incidentsAll outages on January 27, 2015Greenhouse in January 2015MarkdownJSON