Hotjar: Network issues preventing inbound traffic
Timeline of updates
- resolved
From roughly 12:01 UTC, to 12:05 UTC we had an issue which was preventing traffic from reaching Hotjar servers. This was caused by a network change our engineers were trying and quickly identified and reverted. Due to this absence of traffic, servers were afterwards overwhelmed and service was operating with elevated error rates and latencies for roughly the next 15 minutes. Hotjar is now back up and operating normally.
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-02-08 12:40 UTC, resolved after 0 min, 1 update(s).
- Title
- Network issues preventing inbound traffic
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/tb02cd3zc3vs
Hotjar profileRecent Hotjar incidentsAll outages on February 8, 2018Hotjar in February 2018MarkdownJSON