Hotjar: Incident Report - Users unable to create / edit items in Hotjar.
Timeline of updates
- resolved
This has now been resolved. Our engineers made a deployment to the live servers which caused an incorrect hostname to be set for our memcached service. The memcached service is used to cache the settings for websites, to ensure they can be retrieved as efficiently as possible. Since the hostname was incorrect, our servers were not able to communicate with the memcached service, resulting in errors when changes were made to the tools used on site. A policy document for deployments have already been updated to ensure hostnames aren't changed and are retained for all instances. Furthermore, we have created a story for our backlog to have a more secure and robust storage for settings and credentials, ensuring they are enforced at a higher level.
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-11-02 11:02 UTC, resolved after 42 min, 1 update(s).
- Title
- Incident Report - Users unable to create / edit items in Hotjar.
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/x39tlmzvx8jm
Hotjar profileRecent Hotjar incidentsAll outages on November 2, 2016Hotjar in November 2016MarkdownJSON