Hotjar: Incident Report - Degraded Performance.
Timeline of updates
- resolved
On 1st August 2016 at 20:40 CEST, our engineers identified an error which caused Hotjar's performance to degrade drastically. The issue was caused by our primary Amazon Web Service database instance failing which caused our web instances to overload and our Hotjar interface to slow down drastically. The issue was fixed at 20:56 CEST (16 minutes later) after the failover database had been automatically triggered. Whilst database failures can occasionally occur, we have automatic failovers in place to minimise disruption in such events. However, we will be researching and discussing the events that led up to the issue over the next few days and working on a plan to reduce the chances of this re-occurring in the future.
From Hotjar’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.hotjar.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Hotjar, started 2016-08-01 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Incident Report - Degraded Performance.
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/mjxp89rpyqk5
Hotjar profileRecent Hotjar incidentsAll outages on August 1, 2016Hotjar in August 2016MarkdownJSON