- Level
- confirmed
- Worst impact
- Degraded
- Components
- Heap Connect
- Down Index
- 24of 100
What to do
Check whether you use Heap Heap Connect. 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 17h 27m it lasted.
Anything that failed between 2025-10-10 15:28 UTC and 2025-10-11 08:55 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 5
- identified
Our engineering team has identified the root cause of the delayed syncs and is working on a solution. Data is still being collected and no data has been lost. We will post an update in one hour.
provider
- identified
We are continuing to work on a fix for this issue
provider
- identified
We continue to work on a fix for this issue.
provider
- monitoring
A fix has been applied, and impacted connect syncs are recovering. Upcoming syncs will be processed on their usual schedule. We continue to monitor during this recovery period.
provider
- resolved
This incident has been resolved.
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-700a4c32fa
Is Heap still down?
No, this incident was resolved 2025-10-11 08:55 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
17h 27m, from 2025-10-10 15:28 UTC to 2025-10-11 08:55 UTC, by the times Heap posted.
What was affected?
Heap named Heap Connect.
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.