55 Hevo incidents · 2024年11月 — official updates, affected components, duration and resolution details.
由于9月21日3:50 PM PDT开始AWS停电,一些Edge管道受到影响,导致摄入延迟. 有关最新消息,请访问AWS健康状况网页: https://health.aws.amazon.com/health/status 页面存档备份,存于互联网档案馆. 我们正密切监测情况.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决。 影响赫沃边缘的AWS事件已得到解决,受影响的管线已恢复正常处理. 我们已完成复原检查, 作为防范,请审查 您的关键管道和下游数据。 如果您发现任何异常情况, 请联系 Hevo Supports at [email protected] .
自动翻译自官方事件更新。
这个问题已经确定,我们正在设法解决问题。 事件开始时间: UTC下午4点
一项固定措施已经执行,我们正在监测结果。 我们确定了影响美国地区数据管道和模型的问题。 随着服务恢复,我们期望数据管道的处理滞后达一小时。 我们将继续监测复苏情况,并视需要提供进一步的最新资料.
这一事件已经得到解决.
自动翻译自官方事件更新。
目前,我们发现Google Ads连接器的故障影响了Ad Group和Campaign对象,这是在最近从21版升级到24版之后发生的. 我们的工程小组已经查明了根源,并正在积极努力执行一个解决办法.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们从协调世界时08:42-09:30观察到了影响Meta Ads API的退化性能,这可能导致Facebook Ads管道的数据摄取延迟. 这个问题似乎已经解决,服务已经恢复正常。 我们正在继续密切监测局势.
这一事件已经得到解决.
自动翻译自官方事件更新。
当前日志显示后端进程没有受到影响. 我们目前正在与内务部调查这个问题.
AWS正与亚马逊CloudFront调查这个问题. 详情请参见AWS现状PAGE:https://health.aws.amazon.com/health/status
我们现在正在观察对通过CloudFront处理的请求作出的健康反应,UI应该能够跨区域访问。 调查组仍在监测此事。 AWS最新消息(协调世界时11:16): https://health.aws.amazon.com/health/status 页面存档备份,存于互联网档案馆
这一事件已经得到解决.
自动翻译自官方事件更新。
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/
