rewindex

CompaniesHotjarIncidents

Hotjar: Recording number sequence showing incorrect number

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

Timeline of updates

  1. resolved

    The sites affected by the recording sequence being incorrect have now been corrected and all investigations shows this was a one-off event that should be prevented to occur again.

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 2018-11-06 19:37 UTC, resolved after 3 d, 1 update(s).

Title
Recording number sequence showing incorrect number
Vendor
Hotjar
Date
URL
https://rewindex.com/company/hotjar/incidents/r1nlyz2f0tt7

Hotjar profileRecent Hotjar incidentsAll outages on November 6, 2018Hotjar in November 2018MarkdownJSON