- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Integrations - Sources
- Down Index
- 34of 100
What to do
Check whether you use Heap Integrations - Sources. 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 8m it lasted.
Anything that failed between 2026-10-02 21:49 UTC and 2026-10-02 21:57 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.
Root cause
We've identified the root cause and are working on a fix.Read the postmortem
Updates from Heap 2
- identified
Salesforce data isn't syncing into Heap, and new connections or reconnections are failing. We've identified the root cause and are working on a fix. Please don't try to reconnect until we post an update. Thank you for your patience!
provider
- identified
We are continuing to work on a fix for this issue.
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-59ab8de093
Is Heap still down?
No, this incident was resolved 2026-10-02 21:57 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
8m, from 2026-10-02 21:49 UTC to 2026-10-02 21:57 UTC, by the times Heap posted.
What was affected?
Heap named Integrations - Sources.
What caused it?
Heap wrote: "We've identified the root cause and are working on a fix." The postmortem: https://stspg.io/mlrxbt4wqj4g
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.