Historique des pannes de Hevo

1. 2 août 2026 à 17:10 UTCidentified

   Le problème a été identifié et nous travaillons sur une solution. Heure de début de l'incident: 16:00 UTC

2. 2 août 2026 à 17:16 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats. Nous avons identifié un problème touchant les pipelines de données et les modèles dans la région des États-Unis. À mesure que les services se rétablissent, nous nous attendons à ce que les pipelines de données connaissent jusqu'à 1 heure de retard de traitement. Nous continuerons de surveiller le rétablissement et de fournir d'autres mises à jour au besoin.

3. 3 août 2026 à 02:45 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 30 juillet 2026 à 06:37 UTCidentified

   Nous voyons actuellement des défaillances dans le connecteur Google Ads affectant les objets Ad Group et Campaign suite à la récente mise à niveau de la version 21 à la version 24. Notre équipe d'ingénierie a identifié la cause profonde et travaille activement à la mise en œuvre d'un correctif.

2. 31 juillet 2026 à 00:12 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 31 juillet 2026 à 05:21 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 19 juillet 2026 à 09:43 UTCmonitoring

   Nous avons observé des performances dégradées affectant l'API de Meta Ads de 08:42 à 09:30 UTC, ce qui peut avoir entraîné une ingestion tardive de données pour les pipelines Facebook Ads. Le problème semble résolu et les services sont revenus à la normale. Nous continuons de suivre de près la situation.

2. 19 juillet 2026 à 10:00 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juillet 2026 à 08:38 UTCinvestigating

   Les journaux actuels montrent qu'aucun des processus de backend n'est touché. Nous enquêtons actuellement sur la question avec l'assurance-chômage.

2. 16 juillet 2026 à 09:13 UTCidentified

   AWS enquête sur le problème avec Amazon CloudFront. Pour de plus amples renseignements, veuillez consulter la PAGE DE L'ÉTAT DU SAF : https://health.aws.amazon.com/health/status

3. 16 juillet 2026 à 11:19 UTCmonitoring

   Nous observons maintenant des réponses saines aux demandes acheminées par CloudFront, et l'interface utilisateur devrait être accessible dans toutes les régions. L'équipe continue de surveiller cela. Dernière mise à jour de AWS (11:16 UTC): https://health.aws.amazon.com/health/status

4. 16 juillet 2026 à 11:51 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

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

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

3. 17 juin 2026 à 18:40 UTCidentified

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

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

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

6. 18 juin 2026 à 06:38 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 4 juin 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 mai 2026 à 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 11 mai 2026 à 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 mai 2026 à 12:36 UTCmonitoring

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

4. 14 mai 2026 à 11:34 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 23 avril 2026 à 02:53 UTCmonitoring

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

4. 23 avril 2026 à 02:53 UTCresolved

   This incident has been resolved.

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

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

3. 16 avril 2026 à 17:04 UTCmonitoring

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

4. 16 avril 2026 à 17:22 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 15 avril 2026 à 08:22 UTCresolved

   This incident has been resolved.

1. 5 mars 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 mars 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 février 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 février 2026 à 14:47 UTCmonitoring

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

3. 11 février 2026 à 17:54 UTCresolved

   This incident has been resolved.

1. 4 février 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 février 2026 à 16:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 février 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 février 2026 à 17:02 UTCidentified

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

5. 4 février 2026 à 17:19 UTCmonitoring

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

6. 4 février 2026 à 17:37 UTCresolved

   This incident has been resolved.

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

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

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

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

3. 21 janvier 2026 à 20:52 UTCmonitoring

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

4. 21 janvier 2026 à 20:52 UTCresolved

   This incident has been resolved.

1. 22 décembre 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 décembre 2025 à 17:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 décembre 2025 à 17:07 UTCidentified

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

4. 22 décembre 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 décembre 2025 à 17:34 UTCresolved

   This incident has been resolved.

1. 16 décembre 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 décembre 2025 à 16:55 UTCmonitoring

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

3. 16 décembre 2025 à 16:59 UTCresolved

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

1. 11 décembre 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 décembre 2025 à 04:45 UTCmonitoring

   We have patched the fix and are monitoring further.

3. 11 décembre 2025 à 04:54 UTCmonitoring

   We are continuing to monitor further.

4. 11 décembre 2025 à 05:10 UTCresolved

   This incident has been resolved.