- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Hotjar. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4d 3h it lasted.
Anything that failed between 2025-09-11 11:04 UTC and 2025-09-15 14:22 UTC may need a replay.Subscribe to Hotjar's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=hotjar works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Hotjar 2
- investigating
Investigating - We have identified an issue with Interviews where the selected timezone for a project is not being applied correctly during participant scheduling. Our team is actively investigating the cause and will provide an update as soon as possible.
provider
- resolved
This issue has been resolved. A fix was deployed to ensure interview scheduling now correctly uses the timezone set in the project’s settings. We apologize for the inconvenience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-77f1e597a5
Is Hotjar still down?
No, this incident was resolved 2025-09-15 14:22 UTC. For Hotjar's live state, see https://down.guide/hotjar.
How long did it last?
4d 3h, from 2025-09-11 11:04 UTC to 2025-09-15 14:22 UTC, by the times Hotjar posted.
What caused it?
Hotjar hasn't published a root cause. If it does, it shows here.
Where does this come from?
Hotjar's official status page, https://status.hotjar.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.