CheckUpstream does not yet run an independent probe against Heap, so no availability figure is published for it — only Heap's own disclosure record below. 22 incidents were recorded in the past 12 months; the most recent resolved 3 days ago after 23 hours. Status signals are polled from Heap's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Heap yet, so we publish no availability figure for it. What follows is Heap's own disclosure record, which is a different thing.
Vendor disclosed: 14 incidents · 83 of 90 days with none posted · 22h 55m of declared impact
Fewer incidents in the last 30 days than 17% of 232 tracked services.
Share of each window with no impact declared by Heap
7d
95.837%
30d
96.817%
90d
98.939%
180d
99.382%
1y
99.695%
Downtime like this can be refundable
If you're a paying Heap customer, outages in these windows may count against Heap's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Heap entitlement →Does Heap actually matter to you?
A Heap outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 14 incidents Heap published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long Heap takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 28, 13:42 UTC · resolved in 23h 18m · Resolved
Aug 15, 14:32 UTC · resolved in 1d 22h · Resolved
Aug 12, 18:42 UTC · resolved in 4h 22m · Resolved
Live Heap status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/heap)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Heap is currently Operational. CheckUpstream tracks Heap in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Heap down" view? See the Heap Live status page.
Aug 12, 04:35 UTC · resolved in 2h 4m · Resolved
Jul 7, 02:37 UTC · resolved in 12h 38m · Resolved
Jul 2, 16:30 UTC · resolved in 25m · Resolved
Jun 20, 17:10 UTC · resolved in 7h 29m · Resolved
Jun 17, 14:45 UTC · resolved in 16h 16m · Resolved
Jun 2, 09:54 UTC · resolved in 9h 55m · Resolved
May 29, 12:26 UTC · resolved in 5h 14m · Resolved
May 5, 12:35 UTC · resolved in 2h 25m · Resolved
Apr 30, 14:11 UTC · resolved in 6h 58m · Resolved
Apr 1, 20:36 UTC · resolved in 2h 6m · Resolved
Mar 30, 14:30 UTC · resolved in 3h 34m · Resolved
Heap's last resolved incident started 3 days ago and lasted 23h 18m (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Heap yet, and the only other figure available would be derived from Heap's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Heap to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Heap's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.