Skip to main content
Heap

Heap Connect Syncs EU only: Possibility Of Stale Data

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

Level
confirmed
Worst impact
Degraded
Components
Heap Connect
Regions
eu

What to do

  • Check whether you use Heap 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 2m it lasted.

    Anything that failed between 2026-01-28 19:31 UTC and 2026-01-28 20:34 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

  1. investigating

    We are experiencing latency in our upstream data source in EU only. Syncs running during this period may have stale data. We will post an update within the hour. No data has been lost and data is still being collected.

    provider

  2. resolved

    This incident has been resolved. Connect syncs will re-sync any missed data at the next regularly scheduled sync.

    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-36cdec4518

Is Heap still down?

No, this incident was resolved 2026-01-28 20:34 UTC. For Heap's live state, see https://down.guide/heap.

How long did it last?

1h 2m, from 2026-01-28 19:31 UTC to 2026-01-28 20:34 UTC, by the times Heap posted.

What was affected?

Heap named 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.