История сбоев Hevo

1. 2 августа 2026 г. в 17:10 UTCidentified

   Проблема была выявлена, и мы работаем над исправлением. Время начала инцидента: 4:00 PM UTC

2. 2 августа 2026 г. в 17:16 UTCmonitoring

   Реализовано исправление, и мы следим за результатами. Мы выявили проблему, затрагивающую каналы передачи данных и модели в регионе США. По мере восстановления услуг мы ожидаем, что конвейеры данных будут испытывать задержку обработки до 1 часа. Мы будем продолжать следить за восстановлением и предоставлять дополнительные обновления по мере необходимости.

3. 3 августа 2026 г. в 02:45 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 30 июля 2026 г. в 06:37 UTCidentified

   В настоящее время мы наблюдаем сбои в разъеме Google Ads, влияющие на объекты Ad Group и Campaign после недавнего обновления с версии 21 до версии 24. Наша инженерная команда определила первопричину и активно работает над внедрением исправления.

2. 31 июля 2026 г. в 00:12 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 31 июля 2026 г. в 05:21 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 19 июля 2026 г. в 09:43 UTCmonitoring

   Мы наблюдали ухудшение производительности, влияющее на API Meta Ads с 08:42 до 09:30 UTC, что, возможно, привело к задержке приема данных для конвейеров рекламы Facebook. Проблема, похоже, решена, и службы вернулись к нормальной жизни. Мы продолжаем внимательно следить за ситуацией.

2. 19 июля 2026 г. в 10:00 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 16 июля 2026 г. в 08:38 UTCinvestigating

   Текущие журналы показывают, что ни один из фоновых процессов не затронут. В настоящее время мы изучаем этот вопрос с помощью UI.

2. 16 июля 2026 г. в 09:13 UTCidentified

   AWS изучает проблему с Amazon CloudFront. Для получения дополнительной информации, пожалуйста, обратитесь к AWS STATUS PAGE: https://health.aws.amazon.com/health/status

3. 16 июля 2026 г. в 11:19 UTCmonitoring

   В настоящее время мы наблюдаем здоровые ответы на запросы, направляемые через CloudFront, и пользовательский интерфейс должен быть доступен в разных регионах. Команда продолжает следить за этим. Последнее обновление AWS (11:16 AM UTC): https://health.aws.amazon.com/health/status

4. 16 июля 2026 г. в 11:51 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 17 июня 2026 г. в 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. 17 июня 2026 г. в 17:16 UTCidentified

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

3. 17 июня 2026 г. в 18:40 UTCidentified

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

4. 17 июня 2026 г. в 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. 17 июня 2026 г. в 23:42 UTCmonitoring

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

6. 18 июня 2026 г. в 06:38 UTCresolved

   This incident has been resolved.

1. 12 июня 2026 г. в 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. 12 июня 2026 г. в 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. 12 июня 2026 г. в 16:09 UTCresolved

   This incident has been resolved.

1. 4 июня 2026 г. в 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. 11 мая 2026 г. в 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 11 мая 2026 г. в 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 мая 2026 г. в 12:36 UTCmonitoring

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

4. 14 мая 2026 г. в 11:34 UTCresolved

   This incident has been resolved.

1. 9 мая 2026 г. в 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. 15 мая 2026 г. в 12:12 UTCresolved

   This incident has been resolved.

1. 23 апреля 2026 г. в 00: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. 23 апреля 2026 г. в 02:41 UTCidentified

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

3. 23 апреля 2026 г. в 02:53 UTCmonitoring

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

4. 23 апреля 2026 г. в 02:53 UTCresolved

   This incident has been resolved.

1. 16 апреля 2026 г. в 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. 16 апреля 2026 г. в 17:04 UTCidentified

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

3. 16 апреля 2026 г. в 17:04 UTCmonitoring

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

4. 16 апреля 2026 г. в 17:22 UTCresolved

   This incident has been resolved.

1. 15 апреля 2026 г. в 03: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. 15 апреля 2026 г. в 08:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 апреля 2026 г. в 08:22 UTCresolved

   This incident has been resolved.

1. 5 марта 2026 г. в 07: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. 5 марта 2026 г. в 07: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. 11 февраля 2026 г. в 09: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. 11 февраля 2026 г. в 14:47 UTCmonitoring

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

3. 11 февраля 2026 г. в 17:54 UTCresolved

   This incident has been resolved.

1. 4 февраля 2026 г. в 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. 4 февраля 2026 г. в 16:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 февраля 2026 г. в 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. 4 февраля 2026 г. в 17:02 UTCidentified

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

5. 4 февраля 2026 г. в 17:19 UTCmonitoring

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

6. 4 февраля 2026 г. в 17:37 UTCresolved

   This incident has been resolved.

1. 28 января 2026 г. в 07: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. 28 января 2026 г. в 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. 28 января 2026 г. в 17:23 UTCresolved

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

1. 21 января 2026 г. в 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. 21 января 2026 г. в 19:07 UTCidentified

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

3. 21 января 2026 г. в 20:52 UTCmonitoring

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

4. 21 января 2026 г. в 20:52 UTCresolved

   This incident has been resolved.

1. 22 декабря 2025 г. в 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. 22 декабря 2025 г. в 17:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 декабря 2025 г. в 17:07 UTCidentified

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

4. 22 декабря 2025 г. в 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. 22 декабря 2025 г. в 17:34 UTCresolved

   This incident has been resolved.

1. 16 декабря 2025 г. в 07: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. 16 декабря 2025 г. в 16:55 UTCmonitoring

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

3. 16 декабря 2025 г. в 16:59 UTCresolved

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

1. 11 декабря 2025 г. в 04: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. 11 декабря 2025 г. в 04:45 UTCmonitoring

   We have patched the fix and are monitoring further.

3. 11 декабря 2025 г. в 04:54 UTCmonitoring

   We are continuing to monitor further.

4. 11 декабря 2025 г. в 05:10 UTCresolved

   This incident has been resolved.