Hotjar: Incident Report - Hotjar unavailable
Timeline of updates
- resolved
On 20th February, 2017 at 01:48 (CEST) the Hotjar service went unavailable for approximately 3 minutes. This was determined to be caused by our application servers not being able to reach our main database due to a network issue. Connectivity was restored shortly after (~3mins) and we've since monitored it and can report that it has been behaving nominally since.
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 2017-02-20 01:24 UTC, resolved after 0 min, 1 update(s).
- Title
- Incident Report - Hotjar unavailable
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/vx3kfqqcvmlp
Hotjar profileRecent Hotjar incidentsAll outages on February 20, 2017Hotjar in February 2017MarkdownJSON