Heap: Heap Connect Syncs: Possibility Of Stale Data (US)

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 23h 23m it lasted.
Anything that failed between 2025-08-28 17:48 UTC and 2025-08-29 17:11 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.

identifiedAug 28, 2025, 4:43 PM UTC
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
identifiedAug 28, 2025, 5:48 PM UTC
We are experiencing latency from upstream data lake ingestion. This will cause Connect to sync stale data during this period of latency. We will post an update here when latency is resolved. Reach out to support if help is required.
provider
monitoringAug 28, 2025, 8:29 PM UTC
Latency has recovered at this time. We continue to monitor.
provider
resolvedAug 29, 2025, 5:11 PM UTC
This incident has been resolved. Latency has recovered at this time.
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 2025-08-29 17:11 UTC. For Heap's live state, see https://down.guide/heap.

How long did it last?

23h 23m, from 2025-08-28 17:48 UTC to 2025-08-29 17:11 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.