Hevo had 49 outages in the last 2 years totaling 740h 10m of downtime — averaging 2 incidents per month.
There were 49 Hevo outages since October 3, 2024 totaling 740h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We experienced a Kafka connection issue triggered due to an AWS outage, which impacted processing between approximately 5:30 PM and 11:00 PM IST. The necessary corrective actions have been taken to resolve the issue, and the pipelines are expected to resume normal ingestion. We are currently moving the incident to a Monitoring state and are actively observing the system to ensure stability. A detailed RCA will be shared as soon as it is available.
This incident has been resolved.
We are investigating an issue impacting data pipelines in the US-GCP region, leading to degraded performance. Our engineering team is actively working on identifying the cause and restoring normal performance. Further updates will be shared shortly.
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.
We are currently observing failures in few of the Redshift destinations created after July 2025. Our team is actively investigating the issue and will keep you informed with the latest updates
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
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 identified an issue impacting data pipelines and models in the US region, which resulted in degraded performance. we are investigating the issue.
We identified an issue impacting data pipelines and models in the US region, which resulted in degraded performance. Our engineering team investigated the root cause and has now resolved the issue. All services are currently operating normally.
We have identified an issue where Job Monitoring in the US region is currently impacted, and users may not see jobs or their proper statuses from the past two days until the issue is resolved. Rest assured, our engineering team is actively investigating the cause, and we will share updates as we make progress.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified lag buildups across pipelines for some of the teams in the US2 cluster. If you're facing some lag with data delivery, kindly rest assured that we're working on it as our topmost priority. Apologies for any inconvenience. We will share further updates here in some time.
We are continuing to investigate this issue.
The issue has been identified, and we're working on the fix. We want to ensure all the impacted users that this will be mitigated very soon.
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 issues retrieving data for the Charge and Refund objects from Stripe. Our team is actively investigating the issue.
The issue has been identified on Stripe's end, and our team is checking with Stripe's support regarding a concrete root cause. To fix any Stripe pipelines with failing objects like Charge, Refund, or Dispute, please generate a new restricted API key and configure the same in the source settings. Steps mentioned here: https://docs.hevodata.com/sources/fna-analytics/stripe/#obtaining-the-api-key
We're closing this incident as it has been resolved at our end.
Some Snowflake destinations are currently failing with the following error: “Passphrase is required for encrypted private key.” The root cause has been identified, and a fix is actively being implemented. We will provide further updates as progress continues.
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 have identified some failures in our backend across AWS regions. Users might experience slowness with pipeline operations. Any inconvenience is deeply regretted.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We have deployed some changes at our end to mitigate the issue. We have observed the volume of errors getting reduced after the same and we will be further monitoring the results.
This incident has been resolved.
Snowflake is experiencing an outage in the US-West, AWS Europe, and AWS Asia Pacific Regions. This is impacting our Loading Job.
A fix has been implemented and we are monitoring the results.
The issue has been resolved Reference : https://status.snowflake.com/
Cluster has moved to read-only mode and ingestion is halted. We have identified the cause of the issue and working on the fix
We have patched the fix and are monitoring further.
We are continuing to monitor further.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified, and we are implementing a fix. For the next 10–15 minutes, the cluster will operate in read-only mode.
The fix has been implemented, and the cluster is now out of read-only mode. We are actively monitoring to ensure full stability.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring.
The issue persists in the US region, and we have identified ingestion and processing lags across a few pipelines. We are trying to minimize the impact as much as possible.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
The issue has been identified and a fix is being implemented by the engineering team.
The fix has been implemented, and this incident is now fully resolved. Quick Alerts are now accessible and functioning as expected.
We are currently experiencing an issue where the Test Connection and Save & Continue buttons are unresponsive while creating a pipeline configured with a BigQuery destination, or when setting up a new standalone BigQuery destination across all regions. Impact: 1. Affects users creating new BigQuery destinations or configuring a new pipelines that use BigQuery as the destination. 2. Existing BigQuery destinations continue to work normally. 3. Other destinations (e.g., Snowflake, Redshift) are not impacted. Workaround: Click on the GCS Bucket field once to auto-populate the bucket. After this, both Test Connection and Save & Continue become responsive. Current Status: Our engineering team is actively working on the issue, and the investigation is currently in progress. A fix will be deployed as soon as possible, and we will share further updates here as we make progress.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently facing issues while retrieving "Campaign" reports with the help of Google Ads API. The team is actively investigating the issue along with Google Ads support.
We are continuing to investigate 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.
Start Time: October 20, 2025 at 07:10 UTC End Time: October 20, 2025 at 10:53 PM UTC Summary: Some customers may have experienced slow sync performance and intermittent errors during the global AWS outage on October 20, 2025. Cause: The issue was caused by an incident in the AWS us-east-1 region, impacting several dependent services and resulting in temporary sync delays and connection timeouts. Resolution: After AWS restored stability across their services, Hevo systems automatically recovered, and all sync operations have returned to normal. Next Steps: We continue to monitor platform performance closely and are taking measures to further strengthen resilience against third-party service disruptions.
We are currently experiencing an observability issue in our job monitoring feature, which is enabled for the team(s). This is resulting in delays in job monitoring details and affecting ingestion and loading observability. Our engineering team is actively investigating the cause.
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.
We are currently investigating this issue.
The incident has been resolved, and all UI metrics and views should now be functional.
The issue has been identified, and we are working on the fix.
This incident has been resolved.
We are currently investigating this issue as a priority. Apologies for any inconvenience.
The issue that was occurring from QuickBooks' end has been fixed, and we are in discussions about this for future mitigation. Meanwhile, we will continue monitoring the fix from our end. Thank you for your continued support!
The issue causing QuickBooks Online pipeline failures has been fixed by Intuit. It originated on their end and blocked their API access. We are working with them to help prevent such issues in the future.
We are currently investigating this issue.
We are continuing to investigate this issue.
Facebook Ads pipelines are currently failing due to API access being disrupted. Our engineering team is actively investigating the issue and we will keep you posted on this.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing degraded performance for US Cluster. Our engineering team is actively looking into the issue and working to restore full performance as quickly as possible. Users may experience buffering when attempting to access the platform.
We have moved the US cluster to read-only mode. Data ingestion is impacted at the moment. Data already ingested would continue to be loaded into destinations. Our engineering team is actively looking into the issue and working to restore full performance as quickly as possible.
Our team has been monitoring the nodes for the past 15 minutes, and we can confirm that the US cluster nodes are healthy and functioning as expected.
All impacted nodes in the US cluster are now functioning as expected. This incident will be marked as Resolved.
We're currently experiencing ingestion issues in the MongoDB pipelines. Our engineering team is actively investigating the issue to resolve it as soon as possible.
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.