Hotjar

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-04 14:23 UTC

   Some accounts may experience a temporary pause in Hotjar Session Recordings and see tag verification warnings. The issue has been identified and a fix is being implemented.

2. monitoring 2026-09-04 15:42 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-04 18:03 UTC

   This incident has been resolved, and data is collecting as normal.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-13 10:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-07-30 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-10 09:07 UTC

   We 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.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-01-27 20:53 UTC

   On 22nd January 9.30am UTC we deployed a change that meant users who: - Created a Contentsquare Account - Were then invited to a Hotjar Account Would be unable to login to the Hotjar Account due to a bug on the login process. On 27th January 5pm UTC, we deployed a change to undo...

2. resolved 2026-01-28 13:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 08:07 UTC

   We are currently investigating this issue.

2. resolved 2026-01-20 09:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-14 20:46 UTC

   We are experiencing loading issues with Heatmaps & Z onings when creating new screenshots or when providing screenshot suggestions. Our team is currently investigating. Manual screenshots can be used as workaround for both Heatmaps and Zonings while we are fixing the issue.

2. monitoring 2025-11-15 20:46 UTC

   We’ve identified the issue and deployed a fix. We’re currently monitoring the results to ensure everything is stable.

3. resolved 2025-11-17 08:34 UTC

   This incident is resolved, and Heatmaps are working as normal.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-09-19 11:30 UTC

   Our website, Hotjar.com was briefly inaccessible, but service has been restored. Thanks for bearing with us, and we apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-09-18 12:00 UTC

   We have identified and resolved the cause of the issue. If you experience any further problems, please contact Support.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-11 11:04 UTC

   Investigating - We have identified an issue with Interviews where the selected timezone for a project is not being applied correctly during participant scheduling. Our team is actively investigating the cause and will provide an update as soon as possible.

2. resolved 2025-09-15 14:22 UTC

   This issue has been resolved. A fix was deployed to ensure interview scheduling now correctly uses the timezone set in the project’s settings. We apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-26 20:26 UTC

   We're currently investigating an issue where User Attributes can't be accessed in Insights Site Settings, as well an “Error when fetching User Attributes” message preventing the use of Session Filters. Our engineers are working to fix the issue ASAP and will post updates to...

2. resolved 2025-08-27 20:50 UTC

   We have identified the cause of the issue and resolved it. Thanks so much for bearing with us while we investigated and resolved this! We’re sorry for the trouble as well. If you experience any further issues, please raise a ticket through our Help Center. Thanks!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-08 15:26 UTC

   We’ve declared an incident to investigate reports of Surveys not activating/deactivating, and other changes to the Survey settings not being reflected on customer websites. We’ve formed an incident response team and they’re investigating this together. We’ll post further updates...

2. identified 2025-04-08 15:27 UTC

   We’ve identified the root cause of the incident. We’re working on developing a fix and hope to share more news soon. We’ll post another update to this page once we’ve deployed the fix, and we move on to monitoring it to check it’s resolved the fault. Thanks for bearing with us.

3. resolved 2025-04-08 16:56 UTC

   We’ve validated the deployed fix has worked, and we’re closing this incident. Thanks so much for bearing with us while we investigated and resolved this! We’re sorry for the trouble as well. If you don’t think the incident is resolved, or you’re still seeing problems on your end...

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: Website (www.hotjar.com)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-03-17 14:13 UTC

   We've resolved an issue where hotjar.com was down for some users. This did not affect Insights nor data collection. hotjar.com is back up and running. Thank you for your patience! If you’re still seeing problems on your end please raise a ticket through our Help Center:...

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-02-28 15:05 UTC

   We've resolved an issue! hotjar.com is back up and running. Thank you for your patience! If you’re still seeing problems on your end please raise a ticket through our Help Center: https://help.hotjar.com/hc/en-us/requests/new. Thanks!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-19 16:58 UTC

   We’ve declared an incident to investigate reports of surveys not recording the impressions metric, which, in turn, affects the other Overview metrics. We’ve formed an incident response team and they’re investigating this together. We’ll post further updates to this incident...

2. identified 2025-02-19 17:38 UTC

   We’ve identified the root cause for the incident! We’re working on developing a fix and hope to share more news soon. We’ll post another update to this page once we’ve deployed the fix, and we’re monitoring it to check it’s resolved the fault. Thanks for bearing with us!

3. resolved 2025-02-19 18:01 UTC

   We’ve deployed the fix we mentioned earlier, and we’re closing this incident. Thanks so much for bearing with us while we investigated and resolved this! We’re sorry for the trouble as well. If you don’t think the incident is resolved, or you’re still seeing problems on your end...

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-21 11:34 UTC

   We're investigating an issue with being unable to verify tag installation. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. resolved 2025-01-21 15:24 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-01-20 07:44 UTC

   We've identified an issue that causes the Surveys to be temporarily unavailable. Our engineers are working to fix the issue ASAP. Thanks for bearing with us!

2. investigating 2025-01-20 09:18 UTC

   We've deployed a fix for this issue and are monitoring the situation to ensure everything is back to normal.

3. monitoring 2025-01-20 14:30 UTC

   After further investigation, our team detected the following impact: - Survey screenshots were not captured - User attributes in Survey responses were not captured - Sentiment analysis could not run (it can be re-ran now) - Automated tags did not run (they can be re-ran now) -...

4. resolved 2025-01-21 11:31 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-12 16:42 UTC

   We’ve declared an incident to investigate reports of some users being unable to access survey-specific pages from the survey list. We’ve formed an incident response team and they’re investigating this together. We’ll post further updates to this incident report when we have...

2. resolved 2024-12-12 18:04 UTC

   We’ve identified the root cause, deployed, and validated the fix has worked. We’re closing this incident. Thanks so much for bearing with us while we investigated and resolved this! We’re sorry for the trouble as well. If you don’t think the incident is resolved, or you’re still...

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-28 09:48 UTC

   We’re investigating an issue with a failing system that is causing sporadic maintenance mode messages to appear. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. identified 2024-11-28 10:05 UTC

   The external service has recovered and normal operations have returned. We are monitoring the situation to ensure that everything is stable.

3. monitoring 2024-11-28 10:07 UTC

   The external service has recovered and normal operations have returned. We are monitoring the situation to ensure that everything is stable.

4. resolved 2024-11-28 10:24 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-25 11:31 UTC

   The Engage product is currently down. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. resolved 2024-11-25 12:35 UTC

   This incident is now resolved. Thank you for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: Ingestion

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-14 19:09 UTC

   We're investigating an issue with lagging session ingestion. Sessions may take longer to appear in your account. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. investigating 2024-11-14 19:13 UTC

   While working on mitigating this incident, our ingestion pipeline was made to drop all active sessions around 18:00 UTC. The lost sessions are compensated by increasing session capture for the following hours.

3. investigating 2024-11-14 19:18 UTC

   While working on mitigating this incident, our ingestion pipeline was made to drop all active sessions around 18:00 UTC. We're sorry for the sessions that couldn't be captured. These will be compensated by increasing session capture for the following hours.

4. resolved 2024-11-15 16:28 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-27 09:14 UTC

   Some users are experiencing issues logging in. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com.

2. identified 2024-09-27 09:56 UTC

   Some users are experiencing issues logging in. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com.

3. identified 2024-09-27 09:58 UTC

   We’ve identified the root cause for the incident! We’re working on developing a fix and hope to share more news soon. We’ll post another update to this page once we’ve deployed the fix, and we’re monitoring it to check it’s resolved the fault. Thanks for bearing with us!

4. monitoring 2024-09-27 10:10 UTC

   We’ve deployed the fix we mentioned earlier - we’re now monitoring the deployment to check it’s resolved the fault! We’ll check in again to let you know when the incident’s resolved.

5. resolved 2024-09-27 10:41 UTC

   We’ve validated the deployed fix has worked, and we’re closing this incident. Thanks so much for bearing with us while we investigated and resolved this! We’re sorry for the trouble as well. If you don’t think the incident is resolved, or you’re still seeing problems on your end...

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-25 11:16 UTC

   We're investigating an issue with the Survey templates being temporarily unavailable. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com.

2. resolved 2024-09-25 11:45 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-11 12:42 UTC

   We’re investigating an issue with reactivation for a small number of Hotjar accounts. Our engineers are working to fix the issue. We’ll post a further update once the issue is resolved.

2. monitoring 2024-09-11 15:02 UTC

   Our engineering team have deployed a fix and we are now monitoring the issue.

3. resolved 2024-09-12 08:13 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-03 11:29 UTC

   You may experience some translation issues if you use Hotjar in another language. We're working on a resolution!

2. monitoring 2024-09-03 13:42 UTC

   A fix has been implemented and the situation is being monitored.

3. resolved 2024-09-03 13:55 UTC

   This incident is resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-30 09:20 UTC

   We're investigating an issue with Survey creation. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. resolved 2024-08-30 10:00 UTC

   Our engineers have deployed a fix, and this incident is resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-22 13:32 UTC

   We've received reports that customers are unable to modify their subscription. Our team is investigating this issue and plan to get this resolved as soon as possible.

2. identified 2024-08-22 13:38 UTC

   Our engineers have identified the issue and are working on a fix.

3. monitoring 2024-08-22 13:49 UTC

   Our engineers have implemented a fix for this issue and customers should now be able to manage their subscriptions without error. We will continue to monitor this situation to confirm that the fix was successful.

4. resolved 2024-08-22 14:21 UTC

   This incident is resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-07-17 08:55 UTC

   Our engineers have identified an issue that means you may see an error when trying to access your Insights account. We have identified the source of the issue and are working on a fix. Thanks for bearing with us!

2. monitoring 2024-07-17 09:13 UTC

   We've deployed a fix for this issue and are monitoring the situation to ensure everything is back to normal.

3. resolved 2024-07-17 11:59 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-06-07 10:37 UTC

   The Bundle Discount has been applied incorrectly to a small number of accounts

2. investigating 2024-06-07 10:38 UTC

   Our engineers have identified the cause, and are working on a solution

3. resolved 2024-06-10 16:07 UTC

   Our engineers have resolved the issue and customers got back the proper discount

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-03 17:24 UTC

   We're investigating an issue with session data being ingested. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. investigating 2024-06-03 21:25 UTC

   Our engineers are still actively investigating the problem, and working directly with our cloud provider to help us resolve it. We understand that this is impacting your use of Hotjar, so thank you for bearing with us while we work on a fix.

3. investigating 2024-06-04 08:27 UTC

   Our engineers have deployed temporary changes to improve session capture handling while they continue to work with our cloud provider to find the root cause of this issue. Thank you for bearing with us while we work on a resolution.

4. monitoring 2024-06-04 12:26 UTC

   Our engineers have returned data ingestion to regular levels and will be monitoring the situation for several hours to ensure there is no regression. Thanks for bearing with us!

5. resolved 2024-06-05 09:22 UTC

   This incident is now resolved. Our engineers have resolved the issue with session data ingestion and will continue to work with our cloud provider to ensure continued success. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-06-03 09:31 UTC

   From approximately 7:26 to 7:42 UTC, an internal change caused Ask product responses to be rejected instead of saved. Our monitoring system alerted us to this issue and we reverted the change immediately and everything is working as expected again.

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-05-30 14:16 UTC

   We are investigating an issue where the plans for a small number of accounts are not correctly activated

2. investigating 2024-05-30 15:22 UTC

   Our engineers have identified the cause of the issue, and are working on a solution

3. resolved 2024-06-07 10:27 UTC

   Our engineers have resolved the issue and all plans are now correctly activated

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-05-15 11:54 UTC

   We're investigating an issue where some upgrades from an Observe Business Plan to an Observe Scale Plan since 30 Apr 2024 may not have been billed correctly

2. identified 2024-05-16 11:27 UTC

   Our engineers have identified the issue that led to this incident and are now working on a solution.

3. identified 2024-05-17 10:32 UTC

   Invoices for upgrades from an Observe Business Plan to an Observe Scale Plan since 30 Apr 2024 will be processed with a delay

4. resolved 2024-05-28 10:03 UTC

   The delayed invoices for upgrades from an Observe Business Plan to an Observe Scale Plan will be processed by the end of today, 28 May 2024

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-05-06 08:50 UTC

   From approximately 10:20 to 10:40 am CET, the Hotjar.com website and careers pages were inaccessible. This issue has been resolved, thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-24 20:20 UTC

   We're investigating an issue with new survey responses, which are not triggering Zaps in Zapier. Our engineers are working to fix the issue ASAP, we will post updates to status.hotjar.com as we have them. Thanks for bearing with us!

2. identified 2024-04-25 10:20 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 when we're deploying and monitoring the fix. Thanks again for bearing with us!

3. resolved 2024-04-25 14:53 UTC

   This incident is now resolved. Thank you for your patience!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-18 14:13 UTC

   We're investigating an issue where users will enter the Survey creation flow after signing up for a new account. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. identified 2024-04-18 15:14 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 when we're deploying and monitoring the fix. Thanks again for bearing with us!

3. resolved 2024-04-18 17:11 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-04-08 11:37 UTC

   We're investigating an issue where Hotjar's Slack integration cannot be enabled. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. resolved 2024-04-08 13:29 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-02 15:02 UTC

   We’re investigating an issue with our billing system. We have temporarily deactivated access to it whilst we investigate. Thanks for your patience whilst we look into this.

2. investigating 2024-04-02 15:12 UTC

   We have temporarily disabled access to the checkout process and invoices while we investigate this issue. We'll be sure to post an update as soon as these features are back available again. Thanks for you patience while we look into this!

3. investigating 2024-04-02 17:39 UTC

   This incident is now resolved. Thanks for bearing with us!

4. resolved 2024-04-02 17:41 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-02 12:10 UTC

   We're investigating an issue where some trials have been deactivated. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. investigating 2024-04-03 08:27 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 when we're deploying and monitoring the fix. Thanks again for bearing with us!

3. resolved 2024-04-03 12:59 UTC

   This incident is now resolved. All of the affected trials have now been reactivated. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: Ingestion

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-03-27 22:25 UTC

   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...

2. resolved 2024-03-28 01:26 UTC

   This incident is now resolved. Thanks for your understanding!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-22 19:34 UTC

   We're investigating an issue where heatmap screenshots time out and display a "Something went wrong" message. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. monitoring 2024-03-22 21:10 UTC

   We've deployed a fix for this issue and are monitoring the situation to ensure everything is back to normal.

3. monitoring 2024-03-22 21:25 UTC

   This incident is now resolved. Thanks for bearing with us!

4. resolved 2024-03-22 21:27 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-11 20:09 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!

2. identified 2024-03-11 20:19 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!

3. resolved 2024-03-11 21:46 UTC

   This incident has been resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-11 10:54 UTC

   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...

2. monitoring 2024-03-11 11:28 UTC

   The database performance has returned to the expected levels. Our engineers will monitor the situation to ensure that everything is back to normal.

3. resolved 2024-03-11 13:57 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-03-06 10:08 UTC

   We're investigating an issue that causes delays in the sampling calculations. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. monitoring 2024-03-06 10:49 UTC

   We've deployed a fix for this issue and are monitoring the situation to ensure everything is back to normal.

3. resolved 2024-03-06 12:12 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-03-05 15:54 UTC

   Our team has detected an issue on Google's end, where their Single Sign On service is not working at the moment. We're keeping an eye on the situation, and will share updates as Google provides them. Thanks for bearing with us!

2. resolved 2024-03-05 16:35 UTC

   While Google is yet to share any public update on this incident, our team is now able to sign in to Hotjar using the 'Sign in with Google' option. Thanks for bearing with us while this was happening!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-04 10:28 UTC

   We're investigating an issue that caused a delay in offering new trials between 02:00 - 11:00 UTC.

2. resolved 2024-03-04 10:49 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-28 16:10 UTC

   We're investigating an issue with custom colors not working for full-screen surveys. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. investigating 2024-02-28 16:31 UTC

   We're investigating an issue with custom colors not working for full-screen surveys in the survey wizard. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

3. identified 2024-02-28 16:32 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 when we're deploying and monitoring the fix. Thanks again for bearing with us!

4. resolved 2024-02-28 17:17 UTC

   This incident is now resolved. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-23 10:39 UTC

   We're investigating an issue where some users may see a delay in Feedback screenshots being processed. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. identified 2024-02-23 10:53 UTC

   We've identified the issue and are working on a fix!

3. monitoring 2024-02-23 11:17 UTC

   We have deployed the fix for this issue, and we are monitoring things to make sure everything is looking good!

4. resolved 2024-02-23 11:20 UTC

   This incident has been resolved, the pending screenshots for Feedback responses have been processed. Thank you for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Affected: insights.hotjar.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-02-21 14:05 UTC

   We've identified an issue affecting Engage Interviews that is impacting new project creation flows.

2. resolved 2024-02-21 14:54 UTC

   This incident is now resolved, and new project creations in 'Interviews' are loading as expected. Thanks for bearing with us!

Excerpts are shortened. Read the full incident on Hotjar's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-14 14:11 UTC

   We're investigating an issue where some users of Microsoft email (Outlook, etc.) are not receiving registration emails from us. Our engineers are working to fix the issue ASAP and will post updates to status.hotjar.com. Thanks for bearing with us!

2. identified 2024-02-19 16:52 UTC

   We've identified the issue and are working on a fix. For some context, some Microsoft mail servers are discarding emails after accepting their delivery.

3. resolved 2024-02-28 13:33 UTC

   This incident is now resolved. Thanks for bearing with us.

Excerpts are shortened. Read the full incident on Hotjar's status page.