Live / Heap / Incident
Heap: User property data delayed in Heap connect syncs (US customers only)
Heap · heapanalytics.comMinor incidentResolved2026-10-08 15:33 UTC
Public — what happened
Summary
Heap reported that changes to user properties were reaching Heap Connect syncs late for some customers, and its title noted that only US customers were affected. The company began looking into the problem at 23:20 UTC on October 7, 2026, and said incoming data was still being captured with nothing lost. Heap did not say what caused the delays, but by 03:50 UTC on October 8 it said a fix was in place and processing times were improving. The incident was marked resolved at 15:33 on October 8.
Affected
App, Heap Connect
Timeline
- Started — 2026-10-07 23:20 UTC
- Investigating — 2026-10-07 23:20 UTC (2 updates)
- Monitoring — 2026-10-08 03:50 UTC
- Resolved — 2026-10-08 15:33 UTC · 16h 14m 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 42, 2026, our weekly internet health report.