Heap had 42 outages in the last 2 years totaling 345h 42m of downtime — averaging 1.7 incidents per month.
There were 42 Heap outages since March 19, 2025 totaling 345h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to investigate the issue
Latency is resolving. We are currently monitoring.
This incident has been resolved.
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.
This incident has been resolved
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue causing dashboards and charts to experience loading delays or failures.
This incident has been resolved
This incident has been resolved.
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.
We are continuing to work on a fix.
We are continuing to work on a fix.
This incident has been resolved.
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.
Queries have resumed. We are monitoring.
This incident has been resolved.
No data has been lost. We are working on a fix
We continue to work on a fix for this issue
We are continuing to work on the fix for this issue.
We continue to work on a fix for this issue. We will post an update as soon as one is available.
The fix has been applied and latency is recovering. We continue to monitor.
Latency has recovered for the App. Latency is still recovering for Connect syncs. We continue to monitor.
Latency has recovered for the App. Latency is still recovering for Connect syncs. We continue to monitor.
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.
We are currently investigating this issue.
This incident has been resolved
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to investigate the issue. We will post an update in 2 hours.
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.
This incident has been resolved.
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.
A fix has been applied. We continue to monitor.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been applied and latency is beginning to recover
This incident has been resolved.
Data collection is unaffected. Our engineers are currently investigating the issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to investigate this issue.
We continue to investigate this issue.
We are continuing with this investigation. We will post an update as soon as one is available.
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.
The fix has been applied and latency is starting to recover. We continue to monitor.
This incident has been resolved.
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
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to work on a fix for this issue.
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.
We have identified another issue causing sync delays and are working on a solution.
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.
This incident has been resolved.
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.
This incident has been resolved. Connect syncs will re-sync any missed data at the next regularly scheduled sync.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Some customers may experience query latency. Queries for some customers may take a while to load or return errors. Data collection is not impacted.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Metric alert notifications are currently delayed. We are still investigating and will provide an update in 1 hour.
We are continuing to investigate this issue and will provide an update in 2 hours.
The issue has been identified and we are working on a fix. We will provide an update tomorrow.
This incident has been resolved.
We are investigating an issue impacting Connect syncs to Snowflake in the EU region. Data collection is unaffected, and no data has been lost.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.