Skip to main content

Is Hotjar Down?

No — Hotjar is up

Reachable from all 8 checked regions

Average response time: 163ms

Last checked · checks run every 6 hours

Official status page: https://status.hotjar.com

Hotjar uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
206ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 11 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

11-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: 100.00% uptime, 16 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 31 checks
Aug 17: 100.00% uptime, 31 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 39 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
55ms
DNS 0ms TCP 1ms TLS 3ms TTFB 55ms
arn
35ms
DNS 0ms TCP 0ms TLS 5ms TTFB 34ms
bom
149ms
DNS 0ms TCP 1ms TLS 5ms TTFB 148ms
cdg
57ms
DNS 0ms TCP 11ms TLS 17ms TTFB 56ms
dfw
35ms
DNS 0ms TCP 1ms TLS 4ms TTFB 35ms
ewr
104ms
DNS 0ms TCP 1ms TLS 6ms TTFB 103ms
syd
825ms
DNS 0ms TCP 1ms TLS 5ms TTFB 824ms
yyz
47ms
DNS 0ms TCP 8ms TLS 10ms TTFB 46ms

What Hotjar does

Hotjar records how visitors behave on a website through heatmaps, session recordings, surveys and feedback widgets. A tracking script on each page sends events to Hotjar's ingestion service, and the results are reviewed in a dashboard at insights.hotjar.com. Because that script runs on your own pages, an outage touches your site's front end as well as Hotjar's dashboard.

What an outage looks like

New session recordings and heatmap data stop appearing, leaving a gap for the incident window. Surveys and feedback widgets fail to render for visitors. The insights.hotjar.com dashboard will not load or shows no recent sessions. In the worst case the tracking script itself is slow to return, which can delay page rendering on sites that load it synchronously.

What to do about it

Check status.hotjar.com, which reports the Application, insights.hotjar.com, Ingestion, Site scripts and the marketing site as separate components. Site scripts is the row that matters if your own pages feel slow, and Ingestion is the one that explains missing recordings. Load the tracking script asynchronously so that a Hotjar incident can never block your page rendering.

Is it down for everyone, or just you?

If this page says Hotjar is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

M
Mixpanel
A
Amplitude
P
PostHog
P
Pendo

Hotjar outage FAQ

Can Hotjar slow down or break my website?
It should not break it, but a third-party script is a third-party dependency. Hotjar lists Site scripts as its own status component precisely because that file is served to your visitors. Loading it asynchronously, which is the standard installation, means a slow response delays only the recording rather than your page. Verify that is how yours is installed before an incident, not during one.
Will I lose recordings from during the outage?
Probably, if Ingestion was the affected component. Recordings are captured by the script and sent to Hotjar, so if ingestion is refusing data then sessions in that window are not stored, and there is no retroactive recovery for them. Note the incident window so that a dip in session counts later is not mistaken for a drop in real traffic.
Is it Hotjar or my ad blocker?
Ad blockers and privacy extensions commonly block analytics scripts including Hotjar, and from a single browser that looks identical to an outage. Test in a private window with extensions disabled, or from another device, before concluding Hotjar is down. Consent tooling also suppresses the script for visitors who declined, which legitimately reduces recording volume.
Does an outage affect surveys already running?
A running survey is delivered by the same script, so while Hotjar is unavailable visitors will not see it and responses during that window are not collected. The survey configuration itself is stored on Hotjar and is not lost. Once the incident clears the survey resumes showing without you needing to recreate it.
Where do I see whether it is actually fixed?
status.hotjar.com publishes 90-day uptime per component alongside the current state, so you can confirm both that the incident is closed and how that component has behaved recently. The more practical confirmation is your own dashboard showing sessions with timestamps after the incident, since that proves ingestion is accepting data again.

How we measure this

  • We request Hotjar's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Hotjar publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Hotjar goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required