Live / Heap / Incident
Heap: Temporary Data Latency
Heap · heapanalytics.comMinor incidentResolved2026-11-05 06:57 UTC
Public — what happened
Summary
Heap reported a minor incident it called Temporary Data Latency, starting at 03:38 UTC on 2026-11-05. The company said data was showing up late in the app, so some reports might appear to be missing information. Heap stated that data collection was not affected and that no data was lost. Its engineers were investigating through the updates at 04:26 and 05:53 UTC, and the incident was marked resolved at 06:57 UTC; no cause was given in the text.
Affected
Data Collection, App
Timeline
- Started — 2026-11-05 03:38 UTC
- Identified — 2026-11-05 03:38 UTC (3 updates)
- Resolved — 2026-11-05 06:57 UTC · 3h 19m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Heap against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Heap: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Heap report →
More from Heap
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.