- Level
- confirmed
- Worst impact
- Degraded
- Components
- App, Heap Connect
- Regions
- eu
What to do
Check whether you use Heap App, Heap Connect in eu. 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 1h 27m it lasted.
Anything that failed between 2025-09-19 13:42 UTC and 2025-09-19 15:09 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
Our engineering team has identified the root cause of the delayed ingestion and is working on a solution. Users will see delays in data appearing in the app, and the data synced in Connect during this period will be stale. Data collection is unaffected, and no data has been lost.
provider
- identified
We are actively working on a fix for 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-e2e6701e6f
Is Heap still down?
No, this incident was resolved 2025-09-19 15:09 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
1h 27m, from 2025-09-19 13:42 UTC to 2025-09-19 15:09 UTC, by the times Heap posted.
What was affected?
Heap named App, Heap Connect in eu.
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.