Heap

Affected: App, Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 13:03 UTC

   We are investigating delays in user property updates appearing in the Heap connect syncs for some customers. Our engineering team is working to identify the cause and restore normal processing. Data continues to be collected and no data has been lost.

2. resolved 2026-10-14 19:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App, Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 23:20 UTC

   We are investigating delays in user property updates appearing in the Heap connect syncs for some customers. Our engineering team is working to identify the cause and restore normal processing. Data continues to be collected and no data has been lost.

2. investigating 2026-10-08 00:56 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-08 03:50 UTC

   A fix has been implemented, and latency is recovering. We continue to monitor.

4. resolved 2026-10-08 15:33 UTC

   This incident has been resolved. Latency is back to normal levels. Connect data will catch up on the next regularly scheduled sync.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Integrations - Sources

1. identified 2026-10-02 21:49 UTC

   Salesforce data isn't syncing into Heap, and new connections or reconnections are failing. We've identified the root cause and are working on a fix. Please don't try to reconnect until we post an update. Thank you for your patience!

2. identified 2026-10-02 21:57 UTC

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

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-23 22:15 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update within the hour.

2. monitoring 2026-09-24 00:38 UTC

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

3. resolved 2026-09-24 00:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App, Integrations - Sources

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-22 22:43 UTC

   We have identified an issue where users may see delays in 3rd party integration events getting to the app, and potentially split users.

2. identified 2026-09-23 02:54 UTC

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

3. resolved 2026-09-23 14:35 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 03:39 UTC

   We are currently experiencing delays for Connect Syncs. Our engineering team is currently working to identify a root cause and implement a solution. We will post an update in 30 minutes.

2. monitoring 2026-09-11 03:53 UTC

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

3. monitoring 2026-09-11 04:07 UTC

   A fix has been deployed and we are monitoring. Latency is starting to recover.

4. resolved 2026-09-11 04:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-28 13:42 UTC

   We have identified and resolved an issue affecting upstream data sources for connect syncs. While many syncs have automatically retried, some customers may still be observing stale data. Upcoming scheduled syncs should resolve the staleness issue, and we expect complete...

2. resolved 2026-08-29 12:56 UTC

   Our monitoring shows that all syncs are still operating normally, and no remaining customer should observe staleness issues at this time.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-15 14:32 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update in 2 hours.

2. identified 2026-08-15 16:26 UTC

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

3. monitoring 2026-08-16 14:59 UTC

   US Data Lake ingestion latency is now back within nominal values. Some US Connect customers may still see stale data, but all customers will see fresh data upon their next sync

4. resolved 2026-08-17 13:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-12 18:42 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update within the hour.

2. identified 2026-08-12 19:49 UTC

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

3. identified 2026-08-12 20:43 UTC

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

4. monitoring 2026-08-12 21:33 UTC

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

5. monitoring 2026-08-12 22:39 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-08-12 22:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-12 04:35 UTC

   We are experiencing latency in data getting to connect syncs. Any syncs running during this time may get stale data.

2. monitoring 2026-08-12 05:47 UTC

   Latency is recovered, we continue to monitor. Your data will automatically catch up during the next regularly scheduled sync.

3. resolved 2026-08-12 06:39 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-10 10:34 UTC

   We are currently investigating this issue.

2. resolved 2026-08-10 14:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-04 23:39 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update within the hour.

2. monitoring 2026-08-04 23:47 UTC

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

3. resolved 2026-08-05 02:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Data Collection, App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 18:12 UTC

   We are currently experiencing delays in data being available in the app for a subset of customers. You may notice missing data in your reports. Data collection is unaffected, and no data has been lost. Our engineers are currently investigating the issue.

2. investigating 2026-07-27 19:09 UTC

   We are continuing to investigate the issue

3. monitoring 2026-07-27 19:45 UTC

   Latency is resolving. We are currently monitoring.

4. resolved 2026-07-27 22:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-26 14:06 UTC

   Some US customers using HFT syncs may experience delays in data processing or availability. The issue has been identified, and our teams are working on a resolution.

2. resolved 2026-07-26 17:06 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 06:34 UTC

   We are currently investigating this issue.

2. identified 2026-07-21 06:36 UTC

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

3. resolved 2026-07-21 09:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-20 17:44 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-20 18:05 UTC

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

3. resolved 2026-07-21 05:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-12 13:54 UTC

   We are currently investigating an issue causing dashboards and charts to experience loading delays or failures.

2. identified 2026-07-13 12:49 UTC

   This incident has been resolved

3. resolved 2026-07-13 12:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Data Collection, App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-07 02:37 UTC

   We are currently experiencing delays in data being available in the app. You may notice missing data in your reports. Data collection is unaffected, and no data has been lost. Our engineers are currently investigating the issue. We'll be posting another update in 2 hours.

2. identified 2026-07-07 04:36 UTC

   We are continuing to work on a fix.

3. identified 2026-07-07 06:17 UTC

   We are continuing to work on a fix.

4. resolved 2026-07-07 15:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-02 16:30 UTC

   We are current investigating an issue with slow/unresponsive queries for a subset of customers. No data is lost. We will post an update in 2 hours.

2. monitoring 2026-07-02 16:40 UTC

   Queries have resumed. We are monitoring.

3. resolved 2026-07-02 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App, Heap Connect, Integrations - Destinations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-20 17:10 UTC

   No data has been lost. We are working on a fix

2. identified 2026-06-20 18:06 UTC

   We continue to work on a fix for this issue

3. identified 2026-06-20 18:59 UTC

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

4. identified 2026-06-20 20:54 UTC

   We continue to work on a fix for this issue. We will post an update as soon as one is available.

5. monitoring 2026-06-20 21:22 UTC

   The fix has been applied and latency is recovering. We continue to monitor.

6. monitoring 2026-06-20 23:03 UTC

   Latency has recovered for the App. Latency is still recovering for Connect syncs. We continue to monitor.

7. monitoring 2026-06-21 00:10 UTC

   Latency has recovered for the App. Latency is still recovering for Connect syncs. We continue to monitor.

8. resolved 2026-06-21 00:36 UTC

   Latency has recovered for all components. No data was lost. Connect syncs will sync the latest data on the next regularly scheduled sync. We will continue to monitor.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-17 14:45 UTC

   We are currently investigating this issue.

2. resolved 2026-06-18 06:58 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: S3, ECS

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-02 09:54 UTC

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

2. identified 2026-06-02 09:55 UTC

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

3. monitoring 2026-06-02 15:33 UTC

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

4. resolved 2026-06-02 19:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-29 12:26 UTC

   We are currently experiencing delays for Connect Syncs. Bigquery environments appear to be affected. Our engineering team is currently working to identify a root cause and implement a solution. We will post an update in 2 hours.

2. investigating 2026-05-29 14:38 UTC

   We are continuing to investigate the issue. We will post an update in 2 hours.

3. monitoring 2026-05-29 15:05 UTC

   We have deployed a fix and are beginning to catchup delayed environments. We will post an update in two hours, or resolve the incident if all environments have recovered.

4. resolved 2026-05-29 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-05 12:35 UTC

   We have identified an connectivity issue in the app which is impacting a subset of customers in the EU. We are working on the fix.

2. monitoring 2026-05-05 13:42 UTC

   A fix has been applied. We continue to monitor.

3. resolved 2026-05-05 14:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Integrations - Sources

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-30 14:11 UTC

   We are currently investigating this issue.

2. monitoring 2026-04-30 17:57 UTC

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

3. resolved 2026-04-30 21:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Data Collection, App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-01 20:36 UTC

   We are currently experiencing delays in data being available in the app for subset of customers. You may notice missing data in your reports. Data collection is unaffected, and no data has been lost. Our engineers are currently investigating the issue. We'll be posting another...

2. monitoring 2026-04-01 21:31 UTC

   We are continuing to monitor this issue. We will post another update in 2 hours.

3. monitoring 2026-04-01 22:28 UTC

   We have implemented a fix and monitoring recovery

4. resolved 2026-04-01 22:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-30 14:30 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period in the EU may have stale data. We will post an update within the hour.

2. monitoring 2026-03-30 17:21 UTC

   A fix has been applied and latency is beginning to recover

3. resolved 2026-03-30 18:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-26 14:17 UTC

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

2. monitoring 2026-03-28 17:06 UTC

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

3. resolved 2026-03-30 14:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Integrations - Destinations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-18 17:41 UTC

   Data collection is unaffected. Our engineers are currently investigating the issue.

2. resolved 2026-03-18 20:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-18 16:34 UTC

   We are currently investigating this issue.

2. identified 2026-03-18 16:57 UTC

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

3. monitoring 2026-03-18 17:13 UTC

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

4. resolved 2026-03-18 17:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-15 16:43 UTC

   Some of our customers will see stale data in the app, and may experience queries timing out or failing. We are currently investigating. Data continues to be collected and no data has been lost. We will post an update within an hour.

2. investigating 2026-03-15 17:30 UTC

   We are continuing to investigate this issue.

3. investigating 2026-03-15 18:58 UTC

   We continue to investigate this issue.

4. investigating 2026-03-15 19:54 UTC

   We are continuing with this investigation. We will post an update as soon as one is available.

5. identified 2026-03-16 00:31 UTC

   The issue has been identified and a fix is being implemented. We are still experiencing data latency at this time. Data is still being collected and no data has been lost.

6. monitoring 2026-03-16 00:51 UTC

   The fix has been applied and latency is starting to recover. We continue to monitor.

7. resolved 2026-03-16 03:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Data Collection, App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-03 16:22 UTC

   The issue has been identified and a fix is being implemented. We are currently working to backfill the data and update customers as soon as possible

2. identified 2026-03-03 16:24 UTC

   The issue has been identified and a fix is being implemented. We are currently working to backfill the data and update customers as soon as possible

3. monitoring 2026-03-09 08:42 UTC

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

4. resolved 2026-03-11 01:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-12 18:13 UTC

   Our engineering team has identified the root cause of the delayed syncs and is working on a solution. There is no data loss. We will post an update in one hour.

2. identified 2026-02-12 18:13 UTC

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

3. monitoring 2026-02-12 18:45 UTC

   We have deployed a fix and are beginning to catchup delayed environments. We will post an update in two hours, or resolve the incident if all environments have recovered.

4. identified 2026-02-12 20:29 UTC

   We have identified another issue causing sync delays and are working on a solution.

5. monitoring 2026-02-12 20:58 UTC

   We have deployed a fix and are beginning to catchup delayed environments. We will post an update in two hours, or resolve the incident if all environments have recovered.

6. resolved 2026-02-12 22:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-28 19:31 UTC

   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.

2. resolved 2026-01-28 20:34 UTC

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

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-27 10:48 UTC

   Some customers using Sense AI may experience degraded performance when accessing the Heap application. Data collection remains unaffected. Our engineering team is actively investigating and working to resolve the issue as quickly as possible.

2. identified 2026-01-27 13:50 UTC

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

3. resolved 2026-01-27 15:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-25 11:38 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update within the hour.

2. resolved 2026-01-25 13:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-05 21:47 UTC

   Some customers may experience query latency. Queries for some customers may take a while to load or return errors. Data collection is not impacted.

2. monitoring 2026-01-05 22:31 UTC

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

3. resolved 2026-01-05 22:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Notifications and Alerts

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-01 17:38 UTC

   Metric alert notifications are currently delayed. We are still investigating and will provide an update in 1 hour.

2. investigating 2025-12-01 18:37 UTC

   We are continuing to investigate this issue and will provide an update in 2 hours.

3. identified 2025-12-01 22:00 UTC

   The issue has been identified and we are working on a fix. We will provide an update tomorrow.

4. resolved 2025-12-02 11:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-27 16:36 UTC

   We are investigating an issue impacting Connect syncs to Snowflake in the EU region. Data collection is unaffected, and no data has been lost.

2. monitoring 2025-11-28 02:55 UTC

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

3. resolved 2025-11-28 04:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-20 01:21 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update within the hour.

2. identified 2025-11-20 01:21 UTC

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

3. monitoring 2025-11-20 02:19 UTC

   A fix has been implemented and we are monitoring results.

4. resolved 2025-11-20 04:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-19 17:04 UTC

   We are currently investigating this issue.

2. investigating 2025-11-19 17:06 UTC

   Some customers experiencing query latency. Queries for some customers may take a while to load or return errors. Data collection is not impacted.

3. monitoring 2025-11-19 20:51 UTC

   All systems are now working and we are actively monitoring

4. resolved 2025-11-20 04:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-14 20:49 UTC

   We are experiencing loading issues with Heatmaps & Z onings when creating new screenshots or when providing screenshot suggestions. Our team is currently investigating. Manual screenshots can be used as workaround for both Heatmaps and Zonings while we are fixing the issue.

2. monitoring 2025-11-15 20:46 UTC

   We’ve identified the issue and deployed a fix. We’re currently monitoring the results to ensure everything is stable.

3. resolved 2025-11-17 08:35 UTC

   This incident is resolved, and Heatmaps are working as normal.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect, Integrations - Sources, Integrations - Destinations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 11:52 UTC

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

2. identified 2025-10-20 20:52 UTC

   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.

3. monitoring 2025-10-21 02:23 UTC

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

4. monitoring 2025-10-21 02:41 UTC

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

5. monitoring 2025-10-21 11:57 UTC

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

6. resolved 2025-10-21 14:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-10 15:28 UTC

   Our engineering team has identified the root cause of the delayed syncs and is working on a solution. Data is still being collected and no data has been lost. We will post an update in one hour.

2. identified 2025-10-10 16:50 UTC

   We are continuing to work on a fix for this issue

3. identified 2025-10-10 18:43 UTC

   We continue to work on a fix for this issue.

4. monitoring 2025-10-10 21:17 UTC

   A fix has been applied, and impacted connect syncs are recovering. Upcoming syncs will be processed on their usual schedule. We continue to monitor during this recovery period.

5. resolved 2025-10-11 08:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: App, Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-19 13:42 UTC

   Our engineering team has identified the root cause of the delayed ingestion and is working on a solution. Users will see delays in data appearing in the app, and the data synced in Connect during this period will be stale. Data collection is unaffected, and no data has been lost.

2. identified 2025-09-19 14:31 UTC

   We are actively working on a fix for this issue.

3. resolved 2025-09-19 15:09 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-17 19:12 UTC

   We are experiencing slightly evelated latency in our upstream data source, which will impact customers in the US. Syncs running during this period, especially high frequency syncs, may have stale data. We will post an update within the hour.

2. identified 2025-09-17 20:53 UTC

   We are continuing to work on this issue.

3. resolved 2025-09-18 01:27 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Heap Connect

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-28 16:43 UTC

   We are experiencing latency in our upstream data source. Syncs running during this period may have stale data. We will post an update within the hour.

2. identified 2025-08-28 17:48 UTC

   We are experiencing latency from upstream data lake ingestion. This will cause Connect to sync stale data during this period of latency. We will post an update here when latency is resolved. Reach out to support if help is required.

3. monitoring 2025-08-28 20:29 UTC

   Latency has recovered at this time. We continue to monitor.

4. resolved 2025-08-29 17:11 UTC

   This incident has been resolved. Latency has recovered at this time.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Integrations - Sources

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-08-25 23:45 UTC

   We are rolling out a fix for the latency that is currently impacting integration events. New events from third-party sources may take longer to appear in Heap at this time. No data has been lost.

2. monitoring 2025-08-26 00:14 UTC

   A fix has been implemented and we are monitoring latency as it begins to recover.

3. resolved 2025-08-26 00:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Integrations - Sources

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-11 14:02 UTC

   We are currently investigating an issue reported with the Shopify integration. Some data from Shopify may not be available in customer accounts.

2. investigating 2025-08-11 16:59 UTC

   Our integration ingestion pipeline is currently experiencing higher than normal latency. No data will be lost. Customers may not see up to date data for source integrations. We will post an update in an hour.

3. investigating 2025-08-11 17:57 UTC

   We are continuing to investigate the issue. We will post an update in an hour.

4. investigating 2025-08-11 19:01 UTC

   We are continuing to investigate the issue. We will post an update in an hour.

5. monitoring 2025-08-11 20:31 UTC

   A fix has been implemented and we are monitoring results.

6. resolved 2025-08-11 23:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Heap's status page.

Affected: Session Replay

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-18 17:11 UTC

   We've identified an issue preventing session replays from loading correctly and are actively investigating the cause. Our team is working to resolve this as quickly as possible. We appreciate your patience.

2. identified 2025-07-18 17:28 UTC

   Update: Fix for Session Replays Underway We've identified the root cause of the session replay loading issues and our team is actively implementing a fix. We're working quickly to restore full functionality. We'll provide another update once the fix is deployed and replays are...

3. monitoring 2025-07-18 18:58 UTC

   The fix for the session replay loading issues has been deployed. We are now actively monitoring the system to confirm full resolution and stable performance. We expect to confirm full restoration shortly.

4. resolved 2025-07-18 19:10 UTC

   Resolved: Session Replays Fully Restored We're happy to report that the issues preventing session replays from loading have been fully resolved. Our monitoring confirms that all session replays are now loading and functioning as expected. Thank you for your patience and...

Excerpts are shortened. Read the full incident on Heap's status page.