- Level
- confirmed
- Worst impact
- Degraded
- Components
- App, Heap Connect
- Regions
- us
What to do
Check whether you use Heap App, Heap Connect in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 16h 14m it lasted.
Anything that failed between 2026-10-07 23:20 UTC and 2026-10-08 15:33 UTC may need a replay.Subscribe to Heap's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=heap works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Heap 4
- investigating
We are investigating delays in user property updates appearing in the Heap connect syncs for some customers. Our engineering team is working to identify the cause and restore normal processing. Data continues to be collected and no data has been lost.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been implemented, and latency is recovering. We continue to monitor.
provider
- resolved
This incident has been resolved. Latency is back to normal levels. Connect data will catch up on the next regularly scheduled sync.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9bb835c781
Is Heap still down?
No, this incident was resolved 2026-10-08 15:33 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
16h 14m, from 2026-10-07 23:20 UTC to 2026-10-08 15:33 UTC, by the times Heap posted.
What was affected?
Heap named App, Heap Connect in us.
What caused it?
Heap hasn't published a root cause. If it does, it shows here.
Where does this come from?
Heap's official status page, https://status.heap.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.