- Level
- confirmed
- Worst impact
- Degraded
- Components
- Ingestion
- Regions
- us
- Down Index
- 25of 100
What to do
Check whether you use Hotjar Ingestion 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 3h 2m it lasted.
Anything that failed between 2024-03-27 22:25 UTC and 2024-03-28 01:26 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
- monitoring
Our engineers detected an issue where ~25% of visitor sessions failed to process, for approximately 2 hours, starting at 18:25 GMT and ending at 20:25 GMT. This partial gap should be covered gradually by our sampling engine in the next hours. We expect the overall number of sessions for today to remain in line with your Observe plan(s). We've deployed a fix for this issue and are monitoring the situation to ensure everything is back to normal. Thanks for bearing with us!
provider
- resolved
This incident is now resolved. Thanks for your understanding!
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-cd4f260464
Is Hotjar still down?
No, this incident was resolved 2024-03-28 01:26 UTC. For Hotjar's live state, see https://down.guide/hotjar.
How long did it last?
3h 2m, from 2024-03-27 22:25 UTC to 2024-03-28 01:26 UTC, by the times Hotjar posted.
What was affected?
Hotjar named Ingestion 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.