- Level
- confirmed
- Worst impact
- Operational
- Regions
- us
What to do
Check whether you use Hotjar in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 3m it lasted.
Anything that failed between 2024-03-11 10:54 UTC and 2024-03-11 13:57 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 3
- investigating
We're investigating an issue with elevated latency in our database, which may cause longer load times, slower processing of sessions, and other delays in Hotjar functions. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!
provider
- monitoring
The database performance has returned to the expected levels. Our engineers will monitor the situation to ensure that everything is back to normal.
provider
- resolved
This incident is now resolved. Thanks for bearing with us!
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-c4b2725a47
Is Hotjar still down?
No, this incident was resolved 2024-03-11 13:57 UTC. For Hotjar's live state, see https://down.guide/providers/hotjar.
How long did it last?
3h 3m, from 2024-03-11 10:54 UTC to 2024-03-11 13:57 UTC, by the times Hotjar posted.
What was affected?
Hotjar named in us.
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.