Hotjar Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Hotjar Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 4, 2026 | Data collection paused for some customersThis incident has been resolved, and data is collecting as normal. | 3h 40m | Resolved |
| Aug 13, 2026 | Growth customers not renewed on 12 Aug for one dayThis incident has been resolved. | 0 min | Resolved |
| Aug 3, 2026 | Potentially all hotjar accounts with varying degrees of limited service.This incident has been resolved. | -4852 min | Resolved |
| Jun 10, 2026 | Missing VOC ResponsesWe experienced a temporary issue where some VOC responses may not have been captured between 12:00 UTC and 14:20 UTC on June 10th. System performance has since returned to normal. | 0 min | Resolved |
| Jan 27, 2026 | Potential login issues to HotjarThis incident has been resolved. | 16h 18m | Resolved |
| Jan 20, 2026 | Surveys not opening in Hotjar applicationThis incident has been resolved. | 59 min | Resolved |
| Nov 14, 2025 | Heatmaps: Issues Generating New ScreenshotsThis incident is resolved, and Heatmaps are working as normal. | 59h 48m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Hotjar incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Hotjar Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Hotjar acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Hotjar outage in this window ran 2d 11h, against a mean recovery of 13h 28m. If you depend on Hotjar in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.