Skip to main content
Heap

EU customers may be experiencing slightly longer-than-normal query times

Degraded Lasted 9h 55m · started · Heap's page

Level
confirmed
Worst impact
Degraded
Components
S3, ECS
Regions
eu

What to do

  • Check whether you use Heap S3, ECS 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 9h 55m it lasted.

    Anything that failed between 2026-06-02 09:54 UTC and 2026-06-02 19:49 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 4

  1. identified

    The issue has been identified and a fix is being implemented.

    provider

  2. identified

    We are continuing to work on a fix for this issue.

    provider

  3. monitoring

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

    provider

  4. 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-272aee857c

Is Heap still down?

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

How long did it last?

9h 55m, from 2026-06-02 09:54 UTC to 2026-06-02 19:49 UTC, by the times Heap posted.

What was affected?

Heap named S3, ECS 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.