Skip to main content
down.guideby Sazabi
Heap
DWN-f33b6a4f21HeapResolved

Latency due to a global Amazon Web Services (AWS) issue

Degraded Lasted 12h 18m · started · Heap's page

Level
confirmed
Worst impact
Degraded
Components
Heap Connect, Integrations - Sources, Integrations - Destinations
Regions
us
Down Index
27of 100

What to do

  • Check whether you use Heap Heap Connect, Integrations - Sources, Integrations - Destinations 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 12h 18m it lasted.

    Anything that failed between 2025-10-21 02:23 UTC and 2025-10-21 14:41 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 6

  1. identified

    You may experience some latency to a global Amazon Web Services (AWS) issue, we are working to resolve this.

    provider

  2. identified

    We are continuing to work on restoring full connect sync functionality for our US customers. No data has been lost. Once all upstream issues have been resolved, data will sync automatically on the next scheduled sync run.

    provider

  3. monitoring

    Connect Syncs: - Upstream issues have been resolved. - Expect to see some further delays as we work through the backlog of syncs that were impacted. - We will post an update when this has been processed and we have returned to regularly scheduled sync processing. Other Integrations: - Some of our partner integrations are still impacted by the AWS outage, but will catch up once those services are completely resolved.

    provider

  4. monitoring

    Connect Syncs: - Upstream issues have been resolved. - Expect to see some further delays as we work through the backlog of syncs that were impacted. - We will post an update when this has been processed and we have returned to regularly scheduled sync processing. Other Integrations: - Some of our partner integrations are still impacted by the AWS outage, but will catch up once those services are completely resolved.

    provider

  5. monitoring

    Other Integrations: - Some of our partner integrations are still impacted by the AWS outage, but will catch up once those services are completely resolved.

    provider

  6. 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-f33b6a4f21

Is Heap still down?

No, this incident was resolved 2025-10-21 14:41 UTC. For Heap's live state, see https://down.guide/heap.

How long did it last?

12h 18m, from 2025-10-21 02:23 UTC to 2025-10-21 14:41 UTC, by the times Heap posted.

What was affected?

Heap named Heap Connect, Integrations - Sources, Integrations - Destinations 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.

Sources

More from Heap

Feed