Hevo Outage History

Hevo is up right now

Hevo had 49 outages in the last 2 years totaling 915h 23m of downtime — averaging 2 incidents per month.

There were 49 Hevo outages since October 3, 2024 totaling 915h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.hevodata.com

Minor July 18, 2025

Delayed loading of pipeline and billing metrics in US, US2, and USGCP Regions

Detected by Pingoru
Jul 18, 2025, 11:55 AM UTC
Resolved
Jul 19, 2025, 10:23 AM UTC
Duration
22h 27m
Affected: UI ConsoleUI ConsoleUI console
Timeline · 4 updates
  1. investigating Jul 18, 2025, 11:55 AM UTC

    We are currently investigating this issue.

  2. identified Jul 18, 2025, 01:27 PM UTC

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

  3. monitoring Jul 18, 2025, 05:42 PM UTC

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

  4. resolved Jul 19, 2025, 10:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 15, 2025

UI Metrics Display Issue in US, US2, and USGCP Regions

Detected by Pingoru
Jul 15, 2025, 11:04 AM UTC
Resolved
Jul 15, 2025, 09:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 15, 2025, 11:04 AM UTC

    We identified an intermittent issue that prevented pipeline UI metrics from being displayed on the dashboard between 2025-07-15 09:30:00 GMT and 2025-07-15 10:10:00 GMT. The issue has since been resolved, and the dashboard is now functioning as expected. Please note that this only impacted the visibility of metrics on the dashboard and did not affect the actual functioning of pipelines.

Read the full incident report →

Notice July 8, 2025

Partial connection Outage with PostgreSQL entities - Asia Cluster

Detected by Pingoru
Jul 08, 2025, 04:00 PM UTC
Resolved
Jul 08, 2025, 11:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 08, 2025, 04:00 PM UTC

    Connection requests to the PostgreSQL databases (Sources/destinations) were not going through in the Asia cluster from 2025-07-08 11:00:00 GMT to 2025-07-08 15:30:00 GMT. We have now resolved this, and the connections should automatically be restored. In case this did not happen, test and continue the connection, and it should go through. More information on how to do this is available here: https://docs.hevodata.com/pipelines/working-with-pipelines/modifying-a-pipeline/ Hevo support will reach out individually in cases where there are any further actions necessary for your account.

Read the full incident report →

Minor June 25, 2025

User Login Functionality Impacted

Detected by Pingoru
Jun 25, 2025, 08:03 AM UTC
Resolved
Jun 25, 2025, 08:15 AM UTC
Duration
12m
Affected: UI ConsoleUI ConsoleUI ConsoleUI Console
Timeline · 4 updates
  1. investigating Jun 25, 2025, 08:03 AM UTC

    We are currently experiencing an issue impacting login functionality on our Hevo clusters. Users attempting to log in may be unable to access the platform at this time. For users who are already logged in, the UI may not function as expected and could display glitches or inconsistencies. Our team is actively investigating the issue and working to restore full functionality as soon as possible. We will provide updates as we progress.

  2. identified Jun 25, 2025, 08:13 AM UTC

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

  3. monitoring Jun 25, 2025, 08:13 AM UTC

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

  4. resolved Jun 25, 2025, 08:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 19, 2025

Latency in loading the data - USGCP environment

Detected by Pingoru
Jun 19, 2025, 03:07 PM UTC
Resolved
Jun 19, 2025, 04:25 PM UTC
Duration
1h 18m
Affected: Destinations
Timeline · 4 updates
  1. investigating Jun 19, 2025, 03:07 PM UTC

    We are currently investigating this issue.

  2. identified Jun 19, 2025, 03:55 PM UTC

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

  3. monitoring Jun 19, 2025, 04:14 PM UTC

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

  4. resolved Jun 19, 2025, 04:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 18, 2025

Databricks Destination Loading Issues

Detected by Pingoru
Jun 18, 2025, 10:35 AM UTC
Resolved
Jun 19, 2025, 11:13 AM UTC
Duration
1d
Affected: DestinationsDestinationsDestinationsDestinationsDestinationsDestinationsDestinations
Timeline · 4 updates
  1. investigating Jun 18, 2025, 10:35 AM UTC

    We're currently experiencing issues with data loading to the Databricks Destination. Our team is actively investigating the root cause. We’ll provide updates as we make progress.

  2. identified Jun 18, 2025, 06:28 PM UTC

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

  3. monitoring Jun 18, 2025, 06:29 PM UTC

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

  4. resolved Jun 19, 2025, 11:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2025

Possible replication interruptions from GCP outage

Detected by Pingoru
Jun 12, 2025, 07:27 PM UTC
Resolved
Jun 12, 2025, 11:11 PM UTC
Duration
3h 43m
Affected: SourcesSourcesSourcesSourcesSourcesSourcesSources
Timeline · 6 updates
  1. investigating Jun 12, 2025, 07:27 PM UTC

    We’re seeing some pipeline failures over the past 40 minutes caused by an ongoing Google outage, which can be tracked here: https://status.cloud.google.com/ Our engineering team is actively investigating the impact. We will keep you posted on this.

  2. investigating Jun 12, 2025, 07:30 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 12, 2025, 08:56 PM UTC

    Update: All pipelines except the ones connected from the us-central1 GCS environment have now started to recover. We expect to see some pipelines fail for a short period of time before getting rescheduled and succeeding. If there were any ingestion triggers to run in the past hour, they would have failed. GCS Status page: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  4. monitoring Jun 12, 2025, 09:34 PM UTC

    All sources and Destinations should recover automatically. In case you see any entities that are still failed, please re-authorize them, and it should then recover the entity.

  5. monitoring Jun 12, 2025, 09:45 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jun 12, 2025, 11:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2025

Pipelines created with pipedrive source are Impacted

Detected by Pingoru
Jun 10, 2025, 10:57 AM UTC
Resolved
Jun 10, 2025, 04:59 PM UTC
Duration
6h 1m
Affected: SourcesSourcesSourcesSourcesSourcesSourcesSources
Timeline · 2 updates
  1. monitoring Jun 10, 2025, 10:57 AM UTC

    Pipelines created with the Pipedrive source are impacted. Pipedrive APIs are encountering issues at the moment. We are continuing to monitor the Pipedrive service status. Status of Pipedrive services can be tracked here: https://status.pipedrive.com/

  2. resolved Jun 10, 2025, 04:59 PM UTC

    The incident has been resolved by the Pipedrive team, and data pipelines are now functional. The problem was due to an incident on Pipedrive’s end, which caused Pipedrive connections to fail. The Pipedrive team has applied a fix, and everything is back to normal. You can check their status update here: https://status.pipedrive.com.

Read the full incident report →

Minor June 10, 2025

Degraded performance in EU cluster

Detected by Pingoru
Jun 10, 2025, 09:51 AM UTC
Resolved
Jun 10, 2025, 11:25 AM UTC
Duration
1h 34m
Affected: UI ConsoleData Pipelines
Timeline · 6 updates
  1. investigating Jun 10, 2025, 09:51 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 10, 2025, 10:24 AM UTC

    We are currently investigating the issue.

  3. investigating Jun 10, 2025, 10:29 AM UTC

    We’re currently investigating an issue impacting our EU cluster. Our team is actively working to identify the issue and evaluate the impact. We’ll provide an update as soon as more information is available.

  4. identified Jun 10, 2025, 11:23 AM UTC

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

  5. monitoring Jun 10, 2025, 11:24 AM UTC

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

  6. resolved Jun 10, 2025, 11:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2025

Issue with webhook pipeline in US2 region

Detected by Pingoru
Jun 03, 2025, 06:10 PM UTC
Resolved
Jun 03, 2025, 03:28 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 03, 2025, 06:10 PM UTC

    We experienced an internal service disruption that impacted our webhook connector between 15:25 to 15:55 UTC The issue has been mitigated, and system performance is back to normal. If you suspect any missing data or irregularities in your pipeline during that time, please reach out to our support team.

Read the full incident report →

Minor May 3, 2025

Issue with logging and slowness in reflecting stats on UI for all regions

Detected by Pingoru
May 03, 2025, 05:38 AM UTC
Resolved
May 03, 2025, 07:17 AM UTC
Duration
1h 38m
Affected: UI ConsoleUI ConsoleUI ConsoleUI ConsoleUI ConsoleUI ConsoleUI console
Timeline · 3 updates
  1. investigating May 03, 2025, 05:38 AM UTC

    Due to degraded performance in our internal services, which can cause slowness/or prevent some stats on the UI from loading. We are currently investigating the issue.

  2. monitoring May 03, 2025, 06:23 AM UTC

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

  3. resolved May 03, 2025, 07:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2025

Issue with UI feature - Download Usage Summary

Detected by Pingoru
Apr 28, 2025, 10:31 AM UTC
Resolved
Apr 28, 2025, 12:08 PM UTC
Duration
1h 37m
Affected: UI ConsoleUI ConsoleUI ConsoleUI ConsoleUI ConsoleUI ConsoleUI consoleBillingBillingBillingBillingBillingBillingBilling
Timeline · 4 updates
  1. investigating Apr 28, 2025, 11:11 AM UTC

    We have identified an issue with a UI component on the Billing page: Usage Summary > Download Usage Summary. The reports being delivered through email may not be accessible for some time. Please reach out to Hevo Support (through Live Chat or [email protected]) to get the reports, in case this is blocking you. We will soon post the next update on this incident. Appreciate your patience!

  2. identified Apr 28, 2025, 11:18 AM UTC

    We were able to identify the root cause behind the failing component. A fix is currently being implemented.

  3. monitoring Apr 28, 2025, 11:30 AM UTC

    A fix has been implemented and we're monitoring the results.

  4. resolved Apr 28, 2025, 12:08 PM UTC

    The incident has been resolved.

Read the full incident report →

Major April 9, 2025

Connection Failures with S3 destination.

Detected by Pingoru
Apr 09, 2025, 05:49 AM UTC
Resolved
Apr 10, 2025, 06:02 AM UTC
Duration
1d
Affected: DestinationsDestinationsDestinationsDestinationsDestinationsDestinationsDestinations
Timeline · 4 updates
  1. investigating Apr 09, 2025, 05:49 AM UTC

    We have noticed that IAM-based authorized S3 as a destination are failing across regions. We are investigating this at the moment.

  2. identified Apr 09, 2025, 06:17 AM UTC

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

  3. monitoring Apr 09, 2025, 10:55 AM UTC

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

  4. resolved Apr 10, 2025, 06:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2025

Degraded performance in US cluster

Detected by Pingoru
Mar 19, 2025, 09:28 AM UTC
Resolved
Mar 19, 2025, 10:51 AM UTC
Duration
1h 22m
Affected: UI ConsoleData Pipelines
Timeline · 4 updates
  1. investigating Mar 19, 2025, 09:28 AM UTC

    We are currently investigating the issue. The workspaces are not accessible to users in the US region.

  2. identified Mar 19, 2025, 09:34 AM UTC

    The issue has been identified, and a fix is being implemented. During this time, the US cluster will be in read-only mode temporarily.

  3. monitoring Mar 19, 2025, 09:47 AM UTC

    The US cluster has been moved out of read-only mode, and we are monitoring the changes. You would observe no ingestion/load for the pipelines during the time when the cluster was in read-only mode.

  4. resolved Mar 19, 2025, 10:51 AM UTC

    The incident has been resolved. The issue occurred due to unhealthy API nodes which resolved on restarting the service. All services should now be functioning as expected.

Read the full incident report →

Minor March 7, 2025

Degraded performance across US cluster

Detected by Pingoru
Mar 07, 2025, 02:35 PM UTC
Resolved
Mar 07, 2025, 04:51 PM UTC
Duration
2h 15m
Affected: Data Pipelines
Timeline · 4 updates
  1. investigating Mar 07, 2025, 02:35 PM UTC

    We are currently investigating the issue.

  2. identified Mar 07, 2025, 02:57 PM UTC

    The issue has been identified, and a fix is currently being implemented. During this process, the US cluster will remain in read-only mode for a period of time.

  3. monitoring Mar 07, 2025, 03:24 PM UTC

    The US cluster has been moved out of read-only mode, and we are monitoring the changes.

  4. resolved Mar 07, 2025, 04:51 PM UTC

    Thank you for your patience while we worked on this issue. We encountered an incident where tasks for all entities—Models, Pipeline Ingestion tasks, and Destination Load tasks—were not executing as expected. This incident has come up due to a recent outage on the US cluster. We have now resolved the issue. As a result, you may have noticed delays in ingestion/loading tasks or missed model run triggers. Moving forward, all scheduled tasks will run as expected and will be automatically recovered in the next schedule. Our development team has identified and implemented a fix for this issue. We truly appreciate your patience and understanding while we worked on resolving this. We sincerely apologise for any inconvenience this may have caused. Please note that if there are any pipelines/models where the schedule interval is high (about 3 hours or more) and you need the data on an urgent basis, please trigger these entities manually to make sure they run as expected.

Read the full incident report →

Major March 4, 2025

Outreach source - Issue with Existing pipelines and new pipeline creation

Detected by Pingoru
Mar 04, 2025, 09:38 PM UTC
Resolved
Mar 05, 2025, 02:28 PM UTC
Duration
16h 49m
Affected: SourcesSourcesSourcesSourcesSourcesSourcesSources
Timeline · 2 updates
  1. investigating Mar 04, 2025, 09:38 PM UTC

    We are facing an issue with the ingestion jobs of existing Outreach pipelines and the creation of new pipelines with the Outreach source. We are actively working on this.

  2. resolved Mar 05, 2025, 02:28 PM UTC

    This incident has been resolved, all outreach pipelines are now fully operational.

Read the full incident report →

Major February 15, 2025

Data Ingestion Failure in AWS ElasticSearch Pipelines

Detected by Pingoru
Feb 15, 2025, 05:57 PM UTC
Resolved
Feb 21, 2025, 02:09 PM UTC
Duration
5d 20h
Affected: Data PipelinesData PipelinesData PipelinesData PipelinesData PipelinesData PipelinesData Pipelines
Timeline · 2 updates
  1. identified Feb 15, 2025, 05:57 PM UTC

    We are currently experiencing an issue affecting data ingestion in AWS Elasticsearch pipelines (version 7.10.x and higher). The root cause has been identified, and our team is actively working on implementing a fix.

  2. resolved Feb 21, 2025, 02:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 13, 2025

Pipedrive Source - Issue with Reauthorization/ New pipeline creation

Detected by Pingoru
Feb 13, 2025, 12:09 PM UTC
Resolved
Mar 08, 2025, 07:11 AM UTC
Duration
22d 19h
Affected: SourcesSourcesSourcesSourcesSourcesSourcesSources
Timeline · 4 updates
  1. identified Feb 13, 2025, 12:09 PM UTC

    We are facing an issue with the re-authorisation of Existing Pipedrive pipelines and new pipeline creation with Pipedrive source, we are actively working on this and have reached out to the Pipedrive team. Existing pipelines will continue to work until reauthorization is required.

  2. identified Mar 05, 2025, 02:29 PM UTC

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

  3. monitoring Mar 08, 2025, 07:11 AM UTC

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

  4. resolved Mar 08, 2025, 07:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 16, 2025

Issue with Linkedin Ads Pipelines

Detected by Pingoru
Jan 16, 2025, 11:38 AM UTC
Resolved
Jan 16, 2025, 09:27 PM UTC
Duration
9h 49m
Affected: SourcesSourcesSourcesSourcesSourcesData PipelinesData PipelinesData PipelinesSourcesSourcesData PipelinesData PipelinesData PipelinesData Pipelines
Timeline · 6 updates
  1. identified Jan 16, 2025, 11:38 AM UTC

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

  2. identified Jan 16, 2025, 05:55 PM UTC

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

  3. identified Jan 16, 2025, 07:04 PM UTC

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

  4. identified Jan 16, 2025, 07:26 PM UTC

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

  5. identified Jan 16, 2025, 08:41 PM UTC

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

  6. resolved Jan 16, 2025, 09:27 PM UTC

    The incident has been resolved, and all pipelines should now be functional.

Read the full incident report →

Minor November 8, 2024

Emergency Maintenance in US2 cluster

Detected by Pingoru
Nov 08, 2024, 04:04 PM UTC
Resolved
Nov 08, 2024, 05:01 PM UTC
Duration
57m
Affected: SourcesData PipelinesDestinations
Timeline · 3 updates
  1. investigating Nov 08, 2024, 04:04 PM UTC

    We are upgrading the network bandwidth on one of our service nodes to better accommodate heavy data loads. This activity will not affect data integrity, though minor performance impact can be noticed during the process.

  2. monitoring Nov 08, 2024, 04:25 PM UTC

    We have successfully completed the maintenance and normal services should resume soon. We will continue to monitor the performance for some time.

  3. resolved Nov 08, 2024, 05:01 PM UTC

    The maintenance window is now closed following steady monitoring to confirm stability.

Read the full incident report →

Minor November 7, 2024

Emergency maintenance: Bug Fix deployment for JDBC sources

Detected by Pingoru
Nov 07, 2024, 01:01 PM UTC
Resolved
Nov 07, 2024, 07:43 PM UTC
Duration
6h 41m
Affected: SourcesSourcesSources
Timeline · 4 updates
  1. identified Nov 07, 2024, 01:01 PM UTC

    We have identified a bug affecting objects' historical ingestion if the primary keys are of byte[] arrays. Our team is actively working on deploying a fix for the same.

  2. identified Nov 07, 2024, 05:27 PM UTC

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

  3. identified Nov 07, 2024, 05:41 PM UTC

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

  4. resolved Nov 07, 2024, 07:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 5, 2024

Emergency maintenance: Bug Fix deployment for MySQL source

Detected by Pingoru
Nov 05, 2024, 03:41 PM UTC
Resolved
Nov 05, 2024, 07:48 PM UTC
Duration
4h 7m
Affected: SourcesSources
Timeline · 3 updates
  1. identified Nov 05, 2024, 03:41 PM UTC

    We have identified a bug in the MySQL connector affecting objects that use byte[] arrays as primary keys, which has been preventing data ingestion for these objects. Our team is actively working on deploying a fix for the same.

  2. monitoring Nov 05, 2024, 07:23 PM UTC

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

  3. resolved Nov 05, 2024, 07:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 16, 2024

Degraded Performance in US cluster

Detected by Pingoru
Oct 16, 2024, 09:15 PM UTC
Resolved
Oct 17, 2024, 02:25 AM UTC
Duration
5h 9m
Affected: SourcesDestinationsData PipelinesModels
Timeline · 7 updates
  1. investigating Oct 16, 2024, 09:15 PM UTC

    We are currently investigating the issue.

  2. investigating Oct 16, 2024, 09:24 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 16, 2024, 09:52 PM UTC

    We have identified the issue and are actively working on a fix. The cluster has been moved to read-only mode which might affect data ingestion for some time. We will provide further updates shortly.

  4. identified Oct 16, 2024, 09:53 PM UTC

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

  5. monitoring Oct 16, 2024, 10:50 PM UTC

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

  6. monitoring Oct 16, 2024, 10:51 PM UTC

    The cluster is moved out of read-only and the ingestion should resume soon. We are monitoring the results after deploying a fix.

  7. resolved Oct 17, 2024, 02:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 3, 2024

Intermittent Connection failures/ New Pipeline Creation Failure with Google Ads Source

Detected by Pingoru
Oct 03, 2024, 06:07 AM UTC
Resolved
Oct 07, 2024, 03:39 AM UTC
Duration
3d 21h
Affected: SourcesSourcesSourcesSourcesSourcesSourcesSources
Timeline · 4 updates
  1. investigating Oct 03, 2024, 06:07 AM UTC

    We are actively investigating the issue. Please note that the ingestion process is continuing without any disruption

  2. investigating Oct 03, 2024, 07:52 AM UTC

    We are actively investigating the issue. Existing Pipelines: Functioning normally with intermittent connection failures. New pipeline: The creation of new Google Ads pipelines is impacted.

  3. monitoring Oct 04, 2024, 05:32 AM UTC

    A fix has been implemented in all of the regions except US2. We are continuing to monitor the results in all other regions. For the US2 region, the fix is scheduled to be deployed on Monday, October 7, 2024, between 1:30 AM and 2:30 AM UTC.

  4. resolved Oct 07, 2024, 03:39 AM UTC

    This incident has been resolved.

Read the full incident report →