- Level
- confirmed
- Worst impact
- Degraded
- Components
- Heap Connect
- Regions
- us
- Down Index
- 26of 100
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 6h 16m it lasted.
Anything that failed between 2025-09-17 19:12 UTC and 2025-09-18 01:27 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 slightly evelated latency in our upstream data source, which will impact customers in the US. Syncs running during this period, especially high frequency syncs, may have stale data. We will post an update within the hour.
provider
- identified
We are continuing to work on this issue.
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-e062602a6a
Is Heap still down?
No, this incident was resolved 2025-09-18 01:27 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
6h 16m, from 2025-09-17 19:12 UTC to 2025-09-18 01:27 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.