Hotjar: Incident Report - Hotjar currently slow or unresponsive.
Timeline of updates
- resolved
A temporary issue with one of our data stores caused Hotjar to stop collecting heatmap data between 11:30 UTC and 12:30 UTC. The issue has now been fully resolved and the engineering team will be doing a postmortem to analyse why the issue occurred and take the necessary actions to avoid the issue reoccurring.
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-11-21 11:30 UTC, resolved after 1.3 h, 1 update(s).
- Title
- Incident Report - Hotjar currently slow or unresponsive.
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/t2w7mt5nwqpq
Hotjar profileRecent Hotjar incidentsAll outages on November 21, 2017Hotjar in November 2017MarkdownJSON