Historial de interrupciones de Hevo

1. 2 de agosto de 2026 a las 17:10 UTCidentified

   La cuestión ha sido identificada y estamos trabajando en una solución. Hora de inicio de incidentes: 4:00 PM UTC

2. 2 de agosto de 2026 a las 17:16 UTCmonitoring

   Se ha aplicado una solución, y estamos monitoreando los resultados. Identificamos un problema que impacta las tuberías y modelos de datos en la región de Estados Unidos. A medida que los servicios se recuperan, esperamos que los oleoductos de datos experimenten hasta 1 hora de retraso de procesamiento. Seguiremos vigilando la recuperación y proporcionaremos nuevas actualizaciones según sea necesario.

3. 3 de agosto de 2026 a las 2:45 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de julio de 2026 a las 6:37 UTCidentified

   Actualmente estamos viendo fallos en el conector Google Ads que afectan a los objetos Ad Group y Campaign tras la actualización reciente de la versión 21 a la versión 24. Nuestro equipo de Ingeniería ha identificado la causa raíz y está trabajando activamente en la implementación de una solución.

2. 31 de julio de 2026 a las 0:12 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 31 de julio de 2026 a las 5:21 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 19 de julio de 2026 a las 9:43 UTCmonitoring

   Observamos el rendimiento degradado que afecta a la Meta Ads API de 08:42 - 09:30 UTC, lo que puede haber dado lugar a la ingestión de datos retardada para los oleoductos de Facebook Ads. La cuestión parece resolverse y los servicios han regresado a la normalidad. Seguimos vigilando de cerca la situación.

2. 19 de julio de 2026 a las 10:00 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de julio de 2026 a las 8:38 UTCinvestigating

   Los registros actuales muestran que ninguno de los procesos de backend son impactados. Actualmente estamos investigando el tema con la UI.

2. 16 de julio de 2026 a las 9:13 UTCidentified

   AWS está investigando el problema con Amazon CloudFront. Quienes deseen más información pueden consultar el AWS STATUS PAGE: https://health.aws.amazon.com/health/status

3. 16 de julio de 2026 a las 11:19 UTCmonitoring

   Actualmente estamos observando respuestas saludables para solicitudes enrutadas a través de CloudFront, y la interfaz de usuario debe ser accesible en todas las regiones. El equipo sigue vigilando esto. Última actualización de AWS (11:16 AM UTC): https://health.aws.amazon.com/health/status

4. 16 de julio de 2026 a las 11:51 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de junio de 2026 a las 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 de junio de 2026 a las 17:16 UTCidentified

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

3. 17 de junio de 2026 a las 18:40 UTCidentified

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

4. 17 de junio de 2026 a las 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 de junio de 2026 a las 23:42 UTCmonitoring

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

6. 18 de junio de 2026 a las 6:38 UTCresolved

   This incident has been resolved.

1. 12 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 16:09 UTCresolved

   This incident has been resolved.

1. 4 de junio de 2026 a las 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 de mayo de 2026 a las 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 11 de mayo de 2026 a las 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 de mayo de 2026 a las 12:36 UTCmonitoring

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

4. 14 de mayo de 2026 a las 11:34 UTCresolved

   This incident has been resolved.

1. 9 de mayo de 2026 a las 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 de mayo de 2026 a las 12:12 UTCresolved

   This incident has been resolved.

1. 23 de abril de 2026 a las 0: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 de abril de 2026 a las 2:41 UTCidentified

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

3. 23 de abril de 2026 a las 2:53 UTCmonitoring

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

4. 23 de abril de 2026 a las 2:53 UTCresolved

   This incident has been resolved.

1. 16 de abril de 2026 a las 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 de abril de 2026 a las 17:04 UTCidentified

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

3. 16 de abril de 2026 a las 17:04 UTCmonitoring

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

4. 16 de abril de 2026 a las 17:22 UTCresolved

   This incident has been resolved.

1. 15 de abril de 2026 a las 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. 15 de abril de 2026 a las 8:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 de abril de 2026 a las 8:22 UTCresolved

   This incident has been resolved.

1. 5 de marzo de 2026 a las 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. 5 de marzo de 2026 a las 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. 11 de febrero de 2026 a las 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. 11 de febrero de 2026 a las 14:47 UTCmonitoring

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

3. 11 de febrero de 2026 a las 17:54 UTCresolved

   This incident has been resolved.

1. 4 de febrero de 2026 a las 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 de febrero de 2026 a las 16:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 de febrero de 2026 a las 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 de febrero de 2026 a las 17:02 UTCidentified

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

5. 4 de febrero de 2026 a las 17:19 UTCmonitoring

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

6. 4 de febrero de 2026 a las 17:37 UTCresolved

   This incident has been resolved.

1. 28 de enero de 2026 a las 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. 28 de enero de 2026 a las 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 de enero de 2026 a las 17:23 UTCresolved

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

1. 21 de enero de 2026 a las 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 de enero de 2026 a las 19:07 UTCidentified

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

3. 21 de enero de 2026 a las 20:52 UTCmonitoring

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

4. 21 de enero de 2026 a las 20:52 UTCresolved

   This incident has been resolved.

1. 22 de diciembre de 2025 a las 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 de diciembre de 2025 a las 17:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 de diciembre de 2025 a las 17:07 UTCidentified

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

4. 22 de diciembre de 2025 a las 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 de diciembre de 2025 a las 17:34 UTCresolved

   This incident has been resolved.

1. 16 de diciembre de 2025 a las 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. 16 de diciembre de 2025 a las 16:55 UTCmonitoring

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

3. 16 de diciembre de 2025 a las 16:59 UTCresolved

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

1. 11 de diciembre de 2025 a las 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. 11 de diciembre de 2025 a las 4:45 UTCmonitoring

   We have patched the fix and are monitoring further.

3. 11 de diciembre de 2025 a las 4:54 UTCmonitoring

   We are continuing to monitor further.

4. 11 de diciembre de 2025 a las 5:10 UTCresolved

   This incident has been resolved.