# Hotjar in February 2017: incidents, uptime and changes

> Hotjar in February 2017: 3 incidents on its status page (2 major or critical), 99.12% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Hotjar’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/hotjar/2017/02
Last updated: 2017-03-01T16:25:00Z

- Incidents posted: 3 (major/critical: 2) · Maintenance: 0
- By vendor impact label: major 2, none 1
- Uptime (vendor-reported): 99.12% free of major/critical incidents, 99.12% free of any incident; outage time 5 h 51 min, incident time 5 h 51 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [January 2017](https://rewindex.com/company/hotjar/2017/01.md) · Next: [March 2017](https://rewindex.com/company/hotjar/2017/03.md) · [All months](https://rewindex.com/company/hotjar/reports.md) · [Hotjar](https://rewindex.com/company/hotjar.md)

_Uptime: Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Problems serving assets from upstream provider (AWS S3)](https://rewindex.com/company/hotjar/incidents/zvz6n360l90h.md) | major | 2017-02-28 18:09 UTC | 2017-02-28 22:48 UTC | 4.7 h | resolved |
| [A number of email invites and notifications are not reaching our users.](https://rewindex.com/company/hotjar/incidents/73b3x5tlfc0k.md) | major | 2017-02-28 22:09 UTC | 2017-03-01 16:25 UTC | 18 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Incident Report - Hotjar unavailable](https://rewindex.com/company/hotjar/incidents/vx3kfqqcvmlp.md) | none | 2017-02-20 01:24 UTC | 2017-02-20 01:24 UTC | 0 min | resolved |
| [Problems serving assets from upstream provider (AWS S3)](https://rewindex.com/company/hotjar/incidents/zvz6n360l90h.md) | major | 2017-02-28 18:09 UTC | 2017-02-28 22:48 UTC | 4.7 h | resolved |
| [A number of email invites and notifications are not reaching our users.](https://rewindex.com/company/hotjar/incidents/73b3x5tlfc0k.md) | major | 2017-02-28 22:09 UTC | 2017-03-01 16:25 UTC | 18 h | resolved |

## Cite this

Hotjar posted 3 status incidents in February 2017 (2 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/hotjar/2017/02
- Citation: Hotjar, “Hotjar in February 2017” (2017-02-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/hotjar/2017/02 (CC BY 4.0).
- Markdown link: `[Hotjar: Hotjar in February 2017 (2017-02-01)](https://rewindex.com/company/hotjar/2017/02)`


---
Canonical: https://rewindex.com/company/hotjar/2017/02 · Markdown: https://rewindex.com/company/hotjar/2017/02.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:10:36.186Z