Hotjar: Some users run into "Something went wrong. please try again later." error

What to do

Check whether you use Hotjar insights.hotjar.com in us. 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 1h 37m it lasted.
Anything that failed between 2024-03-11 20:09 UTC and 2024-03-11 21:46 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.

investigatingMar 11, 2024, 8:09 PM UTC
We're investigating an issue in Insights where some user accounts run into a "Something went wrong. please try again later." error. Our engineers are working to fix the issue ASAP, we will post updates to status.hotjar.com. Thanks for bearing with us while we look into this!
provider
identifiedMar 11, 2024, 8:19 PM UTC
We've identified the root cause of this incident, and a fix is being developed. We'll post an update to let you know once we move on to monitoring the fix. Thanks again for bearing with us!
provider
resolvedMar 11, 2024, 9:46 PM UTC
This incident has been resolved. Thanks for bearing with us!
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Hotjar still down?

No, this incident was resolved 2024-03-11 21:46 UTC. For Hotjar's live state, see https://down.guide/hotjar.

How long did it last?

1h 37m, from 2024-03-11 20:09 UTC to 2024-03-11 21:46 UTC, by the times Hotjar posted.

What was affected?

Hotjar named insights.hotjar.com 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.