- Level
- confirmed
- Worst impact
- Degraded
- Components
- Heap Connect
- Regions
- us
What to do
Check whether you use Heap 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 2h 4m it lasted.
Anything that failed between 2026-08-12 04:35 UTC and 2026-08-12 06:39 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 3
- identified
We are experiencing latency in data getting to connect syncs. Any syncs running during this time may get stale data.
provider
- monitoring
Latency is recovered, we continue to monitor. Your data will automatically catch up during the next regularly scheduled sync.
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-0e9d3cebe8
Is Heap still down?
No, this incident was resolved 2026-08-12 06:39 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
2h 4m, from 2026-08-12 04:35 UTC to 2026-08-12 06:39 UTC, by the times Heap posted.
What was affected?
Heap named 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.