- Level
- confirmed
- Worst impact
- Degraded
- Components
- Heap Connect
- Down Index
- 22of 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 5h 6m it lasted.
Anything that failed between 2026-05-29 12:26 UTC and 2026-05-29 17:32 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 currently experiencing delays for Connect Syncs. Bigquery environments appear to be affected. Our engineering team is currently working to identify a root cause and implement a solution. We will post an update in 2 hours.
provider
- investigating
We are continuing to investigate the issue. We will post an update in 2 hours.
provider
- monitoring
We have deployed a fix and are beginning to catchup delayed environments. We will post an update in two hours, or resolve the incident if all environments have recovered.
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-3a8c04d207
Is Heap still down?
No, this incident was resolved 2026-05-29 17:32 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
5h 6m, from 2026-05-29 12:26 UTC to 2026-05-29 17:32 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.