Hevo の障害履歴

1. 2026年8月2日 17:10 UTCidentified

   問題は特定され、修正に取り組んでいます。 開始時刻: 4:00 PM UTC

2. 2026年8月2日 17:16 UTCmonitoring

   修正を実施し、結果を監視しています。 米国地域でのデータパイプラインやモデルに影響を及ぼす問題を特定しました。 サービスが回復するにつれて、データパイプラインは最大1時間の処理ラグを体験する見込みです。 今後も回復を監視し、さらなるアップデートを随時提供してまいります.

3. 2026年8月3日 2:45 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月30日 6:37 UTCidentified

   現在、バージョン21からバージョン24へのアップグレード後の広告グループやキャンペーンオブジェクトに影響を及ぼすGoogle Adsのコネクターで不具合が起きています。 当社のエンジニアリングチームは、根本的な原因を特定し、修正の実施に積極的に取り組んでいます.

2. 2026年7月31日 0:12 UTCmonitoring

   修正を実装し、結果を監視しています.

3. 2026年7月31日 5:21 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月19日 9:43 UTCmonitoring

   当社は、Facebook Ads パイプラインの遅延データインジェクションに起因する可能性のある 08:42 - 09:30 UTC から Meta Ads API に影響を与える劣化したパフォーマンスを観察しました。 問題は解決され、サービスは正常に戻りました。 今後も状況を監視し続けます.

2. 2026年7月19日 10:00 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月16日 8:38 UTCinvestigating

   現在のログは、バックエンドのプロセスが影響されていないことを示しています。 現在、UIで課題を調査中です.

2. 2026年7月16日 9:13 UTCidentified

   AWS は Amazon CloudFront での問題を調べています。 詳細はAWS STATUS PAGE: https://health.aws.amazon.com/health/status をご覧ください

3. 2026年7月16日 11:19 UTCmonitoring

   CloudFront を経由したリクエストに対して、ヘルシーなレスポンスを保ち、UI は地域を横断してアクセスできるはずです。 チームはまだこれを監視しています。 AWS(11:16 AM UTC)の最新バージョン: https://health.aws.amazon.com/health/status

4. 2026年7月16日 11:51 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月17日 14:30 UTCinvestigating

   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.

2. 2026年6月17日 17:16 UTCidentified

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

3. 2026年6月17日 18:40 UTCidentified

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

4. 2026年6月17日 22:37 UTCidentified

   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.

5. 2026年6月17日 23:42 UTCmonitoring

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

6. 2026年6月18日 6:38 UTCresolved

   This incident has been resolved.

1. 2026年6月12日 14:31 UTCidentified

   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.

2. 2026年6月12日 16:09 UTCmonitoring

   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/

3. 2026年6月12日 16:09 UTCresolved

   This incident has been resolved.

1. 2026年6月4日 13:15 UTCresolved

   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.

1. 2026年5月11日 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 2026年5月11日 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年5月11日 12:36 UTCmonitoring

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

4. 2026年5月14日 11:34 UTCresolved

   This incident has been resolved.

1. 2026年5月9日 18:48 UTCmonitoring

   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.

2. 2026年5月15日 12:12 UTCresolved

   This incident has been resolved.

1. 2026年4月23日 0:52 UTCinvestigating

   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.

2. 2026年4月23日 2:41 UTCidentified

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

3. 2026年4月23日 2:53 UTCmonitoring

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

4. 2026年4月23日 2:53 UTCresolved

   This incident has been resolved.

1. 2026年4月16日 14:23 UTCidentified

   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

2. 2026年4月16日 17:04 UTCidentified

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

3. 2026年4月16日 17:04 UTCmonitoring

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

4. 2026年4月16日 17:22 UTCresolved

   This incident has been resolved.

1. 2026年4月15日 3:42 UTCinvestigating

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

2. 2026年4月15日 8:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年4月15日 8:22 UTCresolved

   This incident has been resolved.

1. 2026年3月5日 7:29 UTCinvestigating

   We identified an issue impacting data pipelines and models in the US region, which resulted in degraded performance. we are investigating the issue.

2. 2026年3月5日 7:33 UTCresolved

   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.

1. 2026年2月11日 9:40 UTCinvestigating

   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.

2. 2026年2月11日 14:47 UTCmonitoring

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

3. 2026年2月11日 17:54 UTCresolved

   This incident has been resolved.

1. 2026年2月4日 16:44 UTCinvestigating

   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.

2. 2026年2月4日 16:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年2月4日 17:02 UTCidentified

   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.

4. 2026年2月4日 17:02 UTCidentified

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

5. 2026年2月4日 17:19 UTCmonitoring

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

6. 2026年2月4日 17:37 UTCresolved

   This incident has been resolved.

1. 2026年1月28日 7:56 UTCinvestigating

   We are currently experiencing issues retrieving data for the Charge and Refund objects from Stripe. Our team is actively investigating the issue.

2. 2026年1月28日 17:22 UTCidentified

   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

3. 2026年1月28日 17:23 UTCresolved

   We're closing this incident as it has been resolved at our end.

1. 2026年1月21日 11:57 UTCidentified

   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.

2. 2026年1月21日 19:07 UTCidentified

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

3. 2026年1月21日 20:52 UTCmonitoring

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

4. 2026年1月21日 20:52 UTCresolved

   This incident has been resolved.

1. 2025年12月22日 16:17 UTCinvestigating

   We have identified some failures in our backend across AWS regions. Users might experience slowness with pipeline operations. Any inconvenience is deeply regretted.

2. 2025年12月22日 17:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年12月22日 17:07 UTCidentified

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

4. 2025年12月22日 17:30 UTCmonitoring

   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.

5. 2025年12月22日 17:34 UTCresolved

   This incident has been resolved.

1. 2025年12月16日 7:31 UTCidentified

   Snowflake is experiencing an outage in the US-West, AWS Europe, and AWS Asia Pacific Regions. This is impacting our Loading Job.

2. 2025年12月16日 16:55 UTCmonitoring

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

3. 2025年12月16日 16:59 UTCresolved

   The issue has been resolved Reference : https://status.snowflake.com/

1. 2025年12月11日 4:23 UTCidentified

   Cluster has moved to read-only mode and ingestion is halted. We have identified the cause of the issue and working on the fix

2. 2025年12月11日 4:45 UTCmonitoring

   We have patched the fix and are monitoring further.

3. 2025年12月11日 4:54 UTCmonitoring

   We are continuing to monitor further.

4. 2025年12月11日 5:10 UTCresolved

   This incident has been resolved.