Hotjar: Data loss for Cloudflare websites
Cloudflare outage, Jul 17, 2020 · 24 vendors, 24 incidents
Hotjar’s incident blames Cloudflare as the cause. (hop 1, posted +1 h 16 min vs the first vendor naming Cloudflare)
“…Data loss for Cloudflare websites The issue has been resolved. Thank you for your patience!…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>6 vendors, 6 blamed Cloudflare<br/>Sigma Computing, WorkOS, Doppler, Linode (Akamai) +2"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Hotjar"]:::blames
root --> h4
me["Hotjar (this incident)<br/>posted +1 h 16 min"]:::me
h4 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
The issue has been resolved. Thank you for your patience!
From Hotjar’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.hotjar.com (opens in new tab).