What happened?
On January 25 at 16:09 UTC, we identified that there was high latency and elevated error rates in the Hotjar Tracking Script, and hotjar.com was inaccessible. Why did this issue occur?
This was caused by an issue with DNS resolution. Once diagnosed, the issue was fixed immediately and services brought back to normal. What will we do to prevent this from happening in the future?
We will hold an internal postmortem to establish any relevant follow-up actions.
Posted Jan 28, 2022 - 18:18 UTC
Resolved
The issue has been resolved. Thank you for your patience!
Posted Jan 25, 2022 - 19:07 UTC
Monitoring
Both hotjar.com and client-script are back up and running. Our engineers have fixed the issue and are monitoring the situation to make sure everything is working smoothly again.
Posted Jan 25, 2022 - 18:41 UTC
Update
Our engineers are still investigating the issue and it affects both client-script and hotjar.com.
Posted Jan 25, 2022 - 17:43 UTC
Investigating
We’re currently investigating an issue with elevated latency that may be impacting access to Hotjar.com and the client script. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!