- 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 23h 14m it lasted.
Anything that failed between 2026-08-28 13:42 UTC and 2026-08-29 12:56 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 2
- monitoring
We have identified and resolved an issue affecting upstream data sources for connect syncs. While many syncs have automatically retried, some customers may still be observing stale data. Upcoming scheduled syncs should resolve the staleness issue, and we expect complete resolution within 24 hours.
provider
- resolved
Our monitoring shows that all syncs are still operating normally, and no remaining customer should observe staleness issues at this time.
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-471da22fab
Is Heap still down?
No, this incident was resolved 2026-08-29 12:56 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
23h 14m, from 2026-08-28 13:42 UTC to 2026-08-29 12:56 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.