Hevo 장애 기록

1. 2026년 8월 2일 PM 5:10 UTCidentified

   문제는 확인되었습니다. 우리는 수정 작업을하고 있습니다. 근무 시간: 4:00 PM UTC

2. 2026년 8월 2일 PM 5:16 UTCmonitoring

   수정이 시행되고, 결과를 모니터링하고 있습니다. 우리는 미국 지역의 데이터 파이프라인 및 모델에 영향을 미치는 문제를 발견했습니다. 서비스 복구로, 우리는 1 시간의 처리 지연을 경험하기 위해 데이터 파이프라인을 기대합니다. 복구를 계속 모니터링하고 필요한대로 더 많은 업데이트를 제공합니다.

3. 2026년 8월 3일 AM 2:45 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 30일 AM 6:37 UTCidentified

   우리는 현재 버전 21에서 버전 24에 최신 업그레이드를 따르는 Ad Group 및 Campaign 개체에 영향을 미치는 Google Ads 커넥터의 실패를보고 있습니다. 우리의 엔지니어링 팀은 뿌리 원인을 확인하고 해결을 구현하는 데 적극적으로 노력하고 있습니다.

2. 2026년 7월 31일 AM 12:12 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 31일 AM 5:21 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 19일 AM 9:43 UTCmonitoring

   우리는 08:42 - 09:30 UTC에서 Meta Ads API에 영향을 미치는 성능, 이는 Facebook Ads 파이프라인에 대한 지연 된 데이터 ingestion에서 발생할 수 있습니다. 문제는 해결되고 서비스가 정상으로 반환됩니다. 우리는 상황을 밀접하게 감시하기 위하여 계속됩니다.

2. 2026년 7월 19일 AM 10:00 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 16일 AM 8:38 UTCinvestigating

   현재 로그는 백엔드 프로세스가 영향을 미칩니다. 우리는 현재 UI를 가진 문제점을 조사하고 있습니다.

2. 2026년 7월 16일 AM 9:13 UTCidentified

   AWS는 Amazon CloudFront의 문제점을 조사하고 있습니다. 자세한 내용은 AWS STATUS PAGE를 참조하십시오. https://health.aws.amazon.com/health/status

3. 2026년 7월 16일 AM 11:19 UTCmonitoring

   우리는 이제 CloudFront를 통해 경로를 요청하는 건강한 응답을 관찰하고, UI는 지역 전체에 접근해야합니다. 팀은 아직도 이것을 감시하고 있습니다. AWS의 최신 업데이트 (11:16 AM UTC): https://health.aws.amazon.com/health/status를 방문하십시오

4. 2026년 7월 16일 AM 11:51 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 17일 PM 2: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일 PM 5:16 UTCidentified

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

3. 2026년 6월 17일 PM 6:40 UTCidentified

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

4. 2026년 6월 17일 PM 10: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일 PM 11:42 UTCmonitoring

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

6. 2026년 6월 18일 AM 6:38 UTCresolved

   This incident has been resolved.

1. 2026년 6월 12일 PM 2: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일 PM 4: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일 PM 4:09 UTCresolved

   This incident has been resolved.

1. 2026년 6월 4일 PM 1: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일 PM 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 5월 11일 PM 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 5월 11일 PM 12:36 UTCmonitoring

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

4. 2026년 5월 14일 AM 11:34 UTCresolved

   This incident has been resolved.

1. 2026년 5월 9일 PM 6: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일 PM 12:12 UTCresolved

   This incident has been resolved.

1. 2026년 4월 23일 AM 12: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일 AM 2:41 UTCidentified

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

3. 2026년 4월 23일 AM 2:53 UTCmonitoring

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

4. 2026년 4월 23일 AM 2:53 UTCresolved

   This incident has been resolved.

1. 2026년 4월 16일 PM 2: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일 PM 5:04 UTCidentified

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

3. 2026년 4월 16일 PM 5:04 UTCmonitoring

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

4. 2026년 4월 16일 PM 5:22 UTCresolved

   This incident has been resolved.

1. 2026년 4월 15일 AM 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일 AM 8:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 4월 15일 AM 8:22 UTCresolved

   This incident has been resolved.

1. 2026년 3월 5일 AM 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일 AM 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일 AM 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일 PM 2:47 UTCmonitoring

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

3. 2026년 2월 11일 PM 5:54 UTCresolved

   This incident has been resolved.

1. 2026년 2월 4일 PM 4: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일 PM 4:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 2월 4일 PM 5: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일 PM 5:02 UTCidentified

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

5. 2026년 2월 4일 PM 5:19 UTCmonitoring

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

6. 2026년 2월 4일 PM 5:37 UTCresolved

   This incident has been resolved.

1. 2026년 1월 28일 AM 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일 PM 5: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일 PM 5:23 UTCresolved

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

1. 2026년 1월 21일 AM 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일 PM 7:07 UTCidentified

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

3. 2026년 1월 21일 PM 8:52 UTCmonitoring

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

4. 2026년 1월 21일 PM 8:52 UTCresolved

   This incident has been resolved.

1. 2025년 12월 22일 PM 4: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일 PM 5:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 12월 22일 PM 5:07 UTCidentified

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

4. 2025년 12월 22일 PM 5: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일 PM 5:34 UTCresolved

   This incident has been resolved.

1. 2025년 12월 16일 AM 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일 PM 4:55 UTCmonitoring

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

3. 2025년 12월 16일 PM 4:59 UTCresolved

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

1. 2025년 12월 11일 AM 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일 AM 4:45 UTCmonitoring

   We have patched the fix and are monitoring further.

3. 2025년 12월 11일 AM 4:54 UTCmonitoring

   We are continuing to monitor further.

4. 2025년 12월 11일 AM 5:10 UTCresolved

   This incident has been resolved.