Störungsverlauf von Hevo

1. 2. August 2026 um 17:10 UTCidentified

   Das Problem wurde identifiziert und wir arbeiten an einer Lösung. Incident Startzeit: 16:00 Uhr UTC

2. 2. August 2026 um 17:16 UTCmonitoring

   Es wurde ein Fix implementiert, und wir überwachen die Ergebnisse. Wir haben ein Problem identifiziert, das sich auf Datenpipelines und -modelle in der US-Region auswirkt. Wenn sich die Dienste erholen, erwarten wir, dass Datenpipelines bis zu 1 Stunde Verarbeitungsverzögerung aufweisen. Wir werden die Wiederherstellung weiterhin überwachen und bei Bedarf weitere Updates bereitstellen.

3. 3. August 2026 um 02:45 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 30. Juli 2026 um 06:37 UTCidentified

   Wir sehen derzeit Fehler im Google Ads-Connector, die sich auf die Anzeigengruppen- und Kampagnenobjekte auswirken, nachdem kürzlich ein Upgrade von Version 21 auf Version 24 durchgeführt wurde. Unser Engineering-Team hat die Ursache identifiziert und arbeitet aktiv an der Implementierung eines Fixes.

2. 31. Juli 2026 um 00:12 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 31. Juli 2026 um 05:21 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 19. Juli 2026 um 09:43 UTCmonitoring

   Wir haben eine beeinträchtigte Leistung der Meta Ads API von 08:42 - 09:30 UTC beobachtet, was zu einer verzögerten Datenaufnahme für Facebook Ads-Pipelines geführt haben könnte. Das Problem scheint gelöst zu sein, und die Dienste haben sich wieder normalisiert. Wir verfolgen die Situation weiterhin aufmerksam.

2. 19. Juli 2026 um 10:00 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 08:38 UTCinvestigating

   Aktuelle Protokolle zeigen, dass keiner der Backend-Prozesse betroffen ist. Wir untersuchen derzeit das Problem mit UI.

2. 16. Juli 2026 um 09:13 UTCidentified

   AWS untersucht das Problem mit Amazon CloudFront. Weitere Einzelheiten finden Sie auf der AWS STATUS PAGE: https://health.aws.amazon.com/health/status

3. 16. Juli 2026 um 11:19 UTCmonitoring

   Wir beobachten jetzt gesunde Antworten auf Anfragen, die über CloudFront weitergeleitet werden, und die Benutzeroberfläche sollte regionenübergreifend zugänglich sein. Das Team beobachtet dies noch immer. Neues Update von AWS (11:16 Uhr UTC): https://health.aws.amazon.com/health/status

4. 16. Juli 2026 um 11:51 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

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

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

3. 17. Juni 2026 um 18:40 UTCidentified

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

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

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

6. 18. Juni 2026 um 06:38 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 4. Juni 2026 um 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. Mai 2026 um 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 11. Mai 2026 um 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 11. Mai 2026 um 12:36 UTCmonitoring

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

4. 14. Mai 2026 um 11:34 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 23. April 2026 um 02:53 UTCmonitoring

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

4. 23. April 2026 um 02:53 UTCresolved

   This incident has been resolved.

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

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

3. 16. April 2026 um 17:04 UTCmonitoring

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

4. 16. April 2026 um 17:22 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 15. April 2026 um 08:22 UTCresolved

   This incident has been resolved.

1. 5. März 2026 um 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. März 2026 um 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. Februar 2026 um 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. Februar 2026 um 14:47 UTCmonitoring

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

3. 11. Februar 2026 um 17:54 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

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

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

5. 4. Februar 2026 um 17:19 UTCmonitoring

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

6. 4. Februar 2026 um 17:37 UTCresolved

   This incident has been resolved.

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

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

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

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

3. 21. Januar 2026 um 20:52 UTCmonitoring

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

4. 21. Januar 2026 um 20:52 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 22. Dezember 2025 um 17:07 UTCidentified

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

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

   This incident has been resolved.

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

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

3. 16. Dezember 2025 um 16:59 UTCresolved

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

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

   We have patched the fix and are monitoring further.

3. 11. Dezember 2025 um 04:54 UTCmonitoring

   We are continuing to monitor further.

4. 11. Dezember 2025 um 05:10 UTCresolved

   This incident has been resolved.