Skip to main content
Heap

Heap Connect Syncs: Possibility Of Stale Data

Degraded Lasted 3h 1m · started · Heap's page

Level
confirmed
Worst impact
Degraded
Components
Heap Connect
Down Index
21of 100

What to do

  • Check whether you use Heap Heap Connect. 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 3h 1m it lasted.

    Anything that failed between 2026-08-04 23:39 UTC and 2026-08-05 02: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.

Updates from Heap 3

  1. identified

    We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update within the hour.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-d25f8b8347

Is Heap still down?

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

How long did it last?

3h 1m, from 2026-08-04 23:39 UTC to 2026-08-05 02:39 UTC, by the times Heap posted.

What was affected?

Heap named Heap Connect.

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.