Hotjar: Performance degradation
Timeline of updates
- resolved
On the 27th February 2020 at 21:54 UTC our engineers identified that the performance of the Hotjar Tracking Code was degraded. The performance degradation lasted 13 minutes and was fully resolved by 22:07 UTC. What happened? An issue with our Content Delivery Network (CDN) provider caused increased latency on Hotjar infrastructure. This meant that the Hotjar Tracking Code might have loaded slowly or timed out (failed to load). We believe this only affected a small percentage of users in the EMEA region. Upon recognizing this issue, our engineers immediately reached out to the CDN provider to work on restoring service for those affected users. Why did this issue occur? We are working with our CDN provider to determine the root cause of this incident and will update with further information once we have conducted an internal postmortem with our provider.
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: minor) posted by Hotjar, started 2020-02-27 21:28 UTC, resolved after 0 min, 1 update(s).
- Title
- Performance degradation
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/29d17rb5v7yl
Hotjar profileRecent Hotjar incidentsAll outages on February 27, 2020Hotjar in February 2020MarkdownJSON