Historia awarii Hevo

1. 2 sierpnia 2026 17:10 UTCidentified

   Problem został zidentyfikowany i pracujemy nad rozwiązaniem. Czas rozpoczęcia incydentu: 4: 00 PM UTC

2. 2 sierpnia 2026 17:16 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki. Zidentyfikowaliśmy problem wpływający na rurociągi i modele danych w regionie USA. Po odzyskaniu usług oczekujemy, że rurociągi danych będą miały do 1 godziny opóźnienia przetwarzania. Będziemy nadal monitorować ożywienie gospodarcze i w razie potrzeby dostarczać dalsze aktualizacje.

3. 3 sierpnia 2026 02:45 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 30 lipca 2026 06:37 UTCidentified

   Obecnie widzimy awarie w złączu reklamowym Google wpływające na obiekty Ad Group i Campaign po niedawnej aktualizacji z wersji 21 do wersji 24. Nasz zespół inżynieryjny zidentyfikował przyczynę i aktywnie pracuje nad wdrożeniem rozwiązania.

2. 31 lipca 2026 00:12 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 31 lipca 2026 05:21 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 19 lipca 2026 09:43 UTCmonitoring

   Obserwowaliśmy zdegradowaną wydajność wpływającą na API reklam Meta od 08: 42 - 09: 30 UTC, co mogło doprowadzić do opóźnionego spożycia danych dla gazociągów reklamowych na Facebooku. Wydaje się, że problem został rozwiązany, a usługi wróciły do normy. Nadal uważnie monitorujemy sytuację.

2. 19 lipca 2026 10:00 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 16 lipca 2026 08:38 UTCinvestigating

   Obecne dzienniki pokazują, że żaden z procesów backend nie ma wpływu. Obecnie prowadzimy dochodzenie w tej sprawie z UI.

2. 16 lipca 2026 09:13 UTCidentified

   AWS bada sprawę z Amazon CloudFront. Więcej informacji na ten temat znajduje się w dokumencie AWS STATUS PAGE: https: / / health.aws.amazon.com / health / status

3. 16 lipca 2026 11:19 UTCmonitoring

   Obserwujemy teraz zdrowe odpowiedzi na wnioski kierowane przez CloudFront, a Interfejs powinien być dostępny w różnych regionach. Zespół nadal to monitoruje. Ostatnia aktualizacja od AWS (11: 16 AM UTC): https: / / health.aws.amazon.com / health / status

4. 16 lipca 2026 11:51 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 17 czerwca 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 czerwca 2026 17:16 UTCidentified

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

3. 17 czerwca 2026 18:40 UTCidentified

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

4. 17 czerwca 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 czerwca 2026 23:42 UTCmonitoring

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

6. 18 czerwca 2026 06:38 UTCresolved

   This incident has been resolved.

1. 12 czerwca 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 czerwca 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 czerwca 2026 16:09 UTCresolved

   This incident has been resolved.

1. 4 czerwca 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 maja 2026 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 11 maja 2026 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 maja 2026 12:36 UTCmonitoring

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

4. 14 maja 2026 11:34 UTCresolved

   This incident has been resolved.

1. 9 maja 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 maja 2026 12:12 UTCresolved

   This incident has been resolved.

1. 23 kwietnia 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 kwietnia 2026 02:41 UTCidentified

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

3. 23 kwietnia 2026 02:53 UTCmonitoring

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

4. 23 kwietnia 2026 02:53 UTCresolved

   This incident has been resolved.

1. 16 kwietnia 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 kwietnia 2026 17:04 UTCidentified

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

3. 16 kwietnia 2026 17:04 UTCmonitoring

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

4. 16 kwietnia 2026 17:22 UTCresolved

   This incident has been resolved.

1. 15 kwietnia 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 kwietnia 2026 08:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 kwietnia 2026 08:22 UTCresolved

   This incident has been resolved.

1. 5 marca 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 marca 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 lutego 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 lutego 2026 14:47 UTCmonitoring

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

3. 11 lutego 2026 17:54 UTCresolved

   This incident has been resolved.

1. 4 lutego 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 lutego 2026 16:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 lutego 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 lutego 2026 17:02 UTCidentified

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

5. 4 lutego 2026 17:19 UTCmonitoring

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

6. 4 lutego 2026 17:37 UTCresolved

   This incident has been resolved.

1. 28 stycznia 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 stycznia 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 stycznia 2026 17:23 UTCresolved

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

1. 21 stycznia 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 stycznia 2026 19:07 UTCidentified

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

3. 21 stycznia 2026 20:52 UTCmonitoring

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

4. 21 stycznia 2026 20:52 UTCresolved

   This incident has been resolved.

1. 22 grudnia 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 grudnia 2025 17:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 grudnia 2025 17:07 UTCidentified

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

4. 22 grudnia 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 grudnia 2025 17:34 UTCresolved

   This incident has been resolved.

1. 16 grudnia 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 grudnia 2025 16:55 UTCmonitoring

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

3. 16 grudnia 2025 16:59 UTCresolved

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

1. 11 grudnia 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 grudnia 2025 04:45 UTCmonitoring

   We have patched the fix and are monitoring further.

3. 11 grudnia 2025 04:54 UTCmonitoring

   We are continuing to monitor further.

4. 11 grudnia 2025 05:10 UTCresolved

   This incident has been resolved.