- Level
- confirmed
- Worst impact
- Degraded
- Components
- App
- Regions
- us
What to do
Check whether you use Heap App 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 12m it lasted.
Anything that failed between 2026-11-03 05:24 UTC and 2026-11-03 05:36 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 2
- identified
We have identified ingestion latency affecting some customers in the US region. Data collection is not affected, and no data has been lost. Ingestion is making progress, but the backlog has not yet cleared. We are monitoring recovery and will provide further updates.
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-c16465e1c3
Is Heap still down?
No, this incident was resolved 2026-11-03 05:36 UTC. For Heap's live state, see https://down.guide/heap.
How long did it last?
12m, from 2026-11-03 05:24 UTC to 2026-11-03 05:36 UTC, by the times Heap posted.
What was affected?
Heap named App 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.