Skip to main content
Vendor reliability

Vendor record

Heap

Vendor reports Degraded

Checked

Front door check counts and Heap’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against Heap in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Heap product, region or your app worked.

How we count front door checks

Heap says

Incident posts from Heap’s status page, with its titles, impact levels and times. They say what Heap chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

5

incidents Heap posted, last 30 days

All vendors’ incidents

Most recent records · all dates

  • User property data delayed in Heap connect syncs (US customers only)

    Minor

    Started, per Heap

    Closed in our record(6h 41m)

    Heap’s post

  • User property data delayed in Heap connect syncs (US customers only)

    Minor

    Started, per Heap

    Closed in our record(16h 20m)

    Heap’s post

  • Salesforce integration: data-in not syncing

    Major

    Started, per Heap

    Latest status Heap postedIdentified. No resolution posted.

    Heap’s post

  • Heap Connect Syncs: Possibility Of Stale Data

    Minor

    Started, per Heap

    Closed in our record(2h 44m)

    Heap’s post

  • Third party integration events latency impacting some customers

    Minor

    Started, per Heap

    Closed in our record(15h 56m)

    Heap’s post
15 older records

  • Heap Connect Sync Delays

    Not specified

    Started, per Heap

    Closed in our record(40m)

    Heap’s post

  • Heap Connect Syncs: Possibility Of Stale Data

    Minor

    Started, per Heap

    Closed in our record(23h 18m)

    Heap’s post

  • Heap Connect Syncs: Possibility Of Stale Data

    Minor

    Started, per Heap

    Closed in our record(1d 22h)

    Heap’s post

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

    Minor

    Started, per Heap

    Closed in our record(4h 22m)

    Heap’s post

  • US connect customers: possibility of stale data

    Minor

    Started, per Heap

    Closed in our record(2h 4m)

    Heap’s post

  • EU hosted | Heap Charts and Dashboards results not loading

    Not specified

    Started, per Heap

    Closed in our record(4h 15m)

    Heap’s post

  • Heap Connect Syncs: Possibility Of Stale Data

    Minor

    Started, per Heap

    Closed in our record(3h 1m)

    Heap’s post

  • Temporary Data Latency - Investigating

    Minor

    Started, per Heap

    Closed in our record(4h 22m)

    Heap’s post

  • Connect Sync Delays

    Major

    Started, per Heap

    Closed in our record(3h 3m)

    Heap’s post

  • Some US Connect customers may be impacted by delays in data lake ingestion

    Major

    Started, per Heap

    Closed in our record(2h 35m)

    Heap’s post

  • Some US customers may experience PA query failures in the app.

    Minor

    Started, per Heap

    Closed in our record(12h 17m)

    Heap’s post

  • Dahboard and Chart loading issues

    Minor

    Started, per Heap

    Closed in our record(22h 55m)

    Heap’s post

  • Temporary Data Latency

    Minor

    Started, per Heap

    Closed in our record(12h 38m)

    Heap’s post

  • Slow Queries

    Minor

    Started, per Heap

    Closed in our record(25m)

    Heap’s post

  • Incoming data is delayed for customers in US. Both the Heap app and Connect are impacted.

    Minor

    Started, per Heap

    Closed in our record(7h 29m)

    Heap’s post

Your code, your dependencies

See which of your code paths call Heap

Connect GitHub or GitLab to find where your public or private repository uses Heap. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Heap status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · HeapStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/heap?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Heap status badge"></iframe>

Frequently Asked Questions

Is Heap currently down?

Heap's latest recorded status is Degraded. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Heap last have an outage?

The most recent closed incident record began 2 days ago and spans 6h 41m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Heap?

No. CheckUpstream does not run front door checks against Heap. The incident history on this page is what Heap reported, not a measure of how often it was available.

How do I monitor Heap in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Heap?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors