Heap.io Outage History

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

We are continuing to monitor for any further issues.

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

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

Latency is resolving. We are currently monitoring.

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

Queries have resumed. We are monitoring.

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.

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

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.

A fix has been applied. We continue to monitor.

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

Apr 1, 02:30 PDT Completed - The scheduled maintenance has been completed. Apr 1, 00:30 PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 29, 09:45 PDT Scheduled - We will be performing a routine infrastructure upgrade during this window. You may experience brief interruptions in app availability and brief delays in data availability.

Mar 30, 11:05 PDT Resolved - This incident has been resolved. Mar 30, 10:21 PDT Monitoring - A fix has been applied and latency is beginning to recover Mar 30, 07:30 PDT Identified - 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.

Mar 30, 07:09 PDT Resolved - This incident has been resolved. Mar 28, 10:06 PDT Monitoring - A fix has been implemented and we are monitoring the results. Mar 26, 07:17 PDT Identified - The issue has been identified and a fix is being implemented.

Mar 18, 13:35 PDT Resolved - This incident has been resolved. Mar 18, 10:41 PDT Investigating - Data collection is unaffected. Our engineers are currently investigating the issue.

Mar 18, 10:54 PDT Resolved - This incident has been resolved. Mar 18, 10:13 PDT Monitoring - A fix has been implemented and we are monitoring the results. Mar 18, 09:57 PDT Identified - The issue has been identified and a fix is being implemented. Mar 18, 09:34 PDT Investigating - We are currently investigating this issue.

Mar 15, 20:56 PDT Resolved - This incident has been resolved. Mar 15, 17:51 PDT Monitoring - The fix has been applied and latency is starting to recover. We continue to monitor. Mar 15, 17:31 PDT Identified - 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. Mar 15, 12:54 PDT Update - We are continuing with this investigation. We will post an update as soon as one is available. Mar 15, 11:58 PDT Update - We continue to investigate this issue. Mar 15, 10:30 PDT Update - We are continuing to investigate this issue. Mar 15, 09:43 PDT Investigating - 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.

Mar 10, 18:58 PDT Resolved - This incident has been resolved. Mar 9, 01:42 PDT Monitoring - A fix has been implemented and we are monitoring the results. Mar 3, 08:24 PST Update - 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 Mar 3, 08:22 PST Identified - 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

Feb 12, 14:58 PST Resolved - This incident has been resolved. Feb 12, 12:58 PST Monitoring - 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. Feb 12, 12:29 PST Identified - We have identified another issue causing sync delays and are working on a solution. Feb 12, 10:45 PST Monitoring - 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. Feb 12, 10:13 PST Update - We are continuing to work on a fix for this issue. Feb 12, 10:13 PST Identified - 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.