rewindex

CompaniesHotjarIncidents

Hotjar: Incident Report - Recordings not being saved.

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.hotjar.com (opens in new tab)

Timeline of updates

  1. resolved

    Our engineers identified an issue which caused recordings not to be saved. This issue was resolved at approximately 07:00 CEST.

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-10-20 12:00 UTC, resolved after 0 min, 1 update(s).

Title
Incident Report - Recordings not being saved.
Vendor
Hotjar
Date
URL
https://rewindex.com/company/hotjar/incidents/mzwqv9ghq9gr

Hotjar profileRecent Hotjar incidentsAll outages on October 20, 2016Hotjar in October 2016MarkdownJSON