Hevo outage history

Due to an AWS outage that started on Sep 21 at 3:50 PM PDT, some Edge pipelines have been affected, resulting in delayed ingestion. You can refer to the AWS Health status page for the latest updates: https://health.aws.amazon.com/health/status We’re closely monitoring the situation and will keep you posted on the further updates.

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. The AWS incident affecting Hevo Edge has been resolved, and affected pipelines have returned to normal processing. We’ve completed recovery checks and confirmed that the affected services and pipelines are operating as expected. As a precaution, please review your critical pipelines and downstream data. If you notice anything unusual, contact Hevo Support at [email protected].

The issue has been identified and we are working on a fix. Incident start time: 4:00 PM UTC

A fix has been implemented, and we are monitoring the results. We identified an issue impacting data pipelines and models in the US region. As services recover, we expect data pipelines to experience up to 1 hour of processing lag. We will continue to monitor the recovery and provide further updates as needed.

This incident has been resolved.

We are currently seeing failures in the Google Ads connector affecting the Ad Group and Campaign objects following the recent upgrade from version 21 to version 24. Our Engineering team has identified the root cause and is actively working on implementing a fix.

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

This incident has been resolved.

We observed degraded performance affecting the Meta Ads API from 08:42 - 09:30 UTC, which may have resulted in delayed data ingestion for Facebook Ads pipelines. The issue appears to be resolved, and services have returned to normal. We are continuing to monitor the situation closely.

This incident has been resolved.

Current logs show that none of the backend processes are impacted. We are currently investigating the issue with UI.

AWS is investigating the issue with Amazon CloudFront. For further details, please refer to the AWS STATUS PAGE: https://health.aws.amazon.com/health/status

We are now observing healthy responses for requests routed through CloudFront, and the UI should be accessible across regions. The team is still monitoring this. Latest update from AWS (11:16 AM UTC): https://health.aws.amazon.com/health/status

This incident has been resolved.

We are currently observing connection failures for Redshift sources and destinations for some teams across different regions. The issue could potentially impact Redshift connections via SSH tunnel. As a result, affected pipelines may experience delays in data ingestion or loading. Our engineering team is actively investigating the issue, and we will provide further updates.

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

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

The fix is under deployment for the US (us-east-1) region. This should take another 2-3 hours for the pipelines to recover. Thanks for your patience in the meantime.

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

This incident has been resolved.

We are currently investigating an issue affecting Facebook Ads source connectors. Customers may experience ingestion failures or delays. Our engineering team is actively investigating the issue, and we will provide further updates.

We suspect this may have been related to a Meta service disruption. Most of the affected pipelines have recovered and are functioning normally. Reference : https://metastatus.com/

This incident has been resolved.

We observed elevated error rates in the Event Consumption service between 05:02 PM and 05:25 PM IST, which resulted in delays in event processing. Our Engineering team identified the issue, mitigated the impact, and restored normal service. Event processing has resumed, and any backlog generated during the incident has been cleared. Current Status: Resolved. All services are operating normally, and event processing is functioning as expected.

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.

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

This incident has been resolved.

We identified an issue impacting data pipelines in the US-GCP region, which resulted in degraded performance. We are investigating the issue.

We are continuing to investigate this issue.

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/