- Level
- confirmed
- Worst impact
- Degraded
- Components
- Heap Connect
- Regions
- us
- Down Index
- 27of 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 1d 22h it lasted.
Anything that failed between 2026-08-15 14:32 UTC and 2026-08-17 13:03 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
- identified
We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update in 2 hours.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
US Data Lake ingestion latency is now back within nominal values. Some US Connect customers may still see stale data, but all customers will see fresh data upon their next 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-102aea4c9d
Is Heap still down?
No, this incident was resolved 2026-08-17 13:03 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
1d 22h, from 2026-08-15 14:32 UTC to 2026-08-17 13:03 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.