Hotjar: Unavailability event due to database updates
Timeline of updates
- resolved
While performing some database updates this morning we inadvertently caused some increased locking on one of our most accessed tables which caused a short 4 minute downtime from 8:04 to 8:08 UTC. No customer data was affected during the incident and operations resumed to normal immediately.
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-05-26 14:45 UTC, resolved after 0 min, 1 update(s).
- Title
- Unavailability event due to database updates
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/n3xgkf9pfxqt
Hotjar profileRecent Hotjar incidentsAll outages on May 26, 2017Hotjar in May 2017MarkdownJSON