Hotjar: Decrease in ingested Sessions
Timeline of updates
- resolved
On 07/12/2021 at 13:46 UTC our engineers identified an issue with WebSocket Data Ingestion. What happened? We detected a decrease in Sessions ingested through our WebSocket servers, however, within 1 minute of this issue being logged, Sessions were back to being ingested as normal. It's possible that 20-40% of Recordings during this time window might have failed to be processed correctly. Why did this issue occur? A batch deployment at the infrastructure level recreated some DNS entries, which caused a temporary disconnection for some services. Within 1 minute, these services were reconnected, back up and running. What will we do to prevent this from happening in the future? If this is clear at time of resolution. It is fine to say “We will hold an internal postmortem to establish any relevant follow-up actions.”
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 2021-12-07 03:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Decrease in ingested Sessions
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/1qk0pd2ckrxb
Hotjar profileRecent Hotjar incidentsAll outages on December 7, 2021Hotjar in December 2021MarkdownJSON