Hotjar: Incident Report - Degraded Performance.
Timeline of updates
- resolved
On 2nd August 2016 at 09:03 CEST, our engineers identified an issue which was causing Hotjar's performance to degrade drastically. The issue was once again caused by our primary Amazon Web Service database instance. The issue was solved at 09:30 CEST and service was immediately restored. Our engineers have upgraded the database instance to one which has 4x the memory and CPU to ensure the same issue cannot happen in the near 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-02 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/mg1km67491rt
Hotjar profileRecent Hotjar incidentsAll outages on August 2, 2016Hotjar in August 2016MarkdownJSON