Heap: Delayed event-data availability in the US

What to do

Check whether you use Heap App, Session Replay 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 8m it lasted.
Anything that failed between 2026-11-04 04:30 UTC and 2026-11-04 10: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.

investigatingNov 4, 2026, 4:30 AM UTC
We are investigating an higher latency in the data freshness of recent event data in the US and recent events may take longer than usual to appear in analytics results. We will provide another update in 30 minutes. Note that the data collection is not affected.
provider
investigatingNov 4, 2026, 5:08 AM UTC
We are continuing to investigate this issue.
provider
monitoringNov 4, 2026, 5:14 AM UTC
Data freshness latency is recovering, and the team is monitoring it.
provider
resolvedNov 4, 2026, 10:39 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Heap still down?

No, this incident was resolved 2026-11-04 10:39 UTC. For Heap's live state, see https://down.guide/heap.

How long did it last?

6h 8m, from 2026-11-04 04:30 UTC to 2026-11-04 10:39 UTC, by the times Heap posted.

What was affected?

Heap named App, Session Replay 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.