Historial de interrupciones de Hevo

1. August 2, 2026 at 5:10 PM UTCidentified

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

2. August 2, 2026 at 5:16 PM 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. August 3, 2026 at 2:45 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 30, 2026 at 6:37 AM 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. July 31, 2026 at 12:12 AM UTCmonitoring

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

3. July 31, 2026 at 5:21 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 19, 2026 at 9:43 AM 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. July 19, 2026 at 10:00 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 16, 2026 at 8:38 AM UTCinvestigating

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

2. July 16, 2026 at 9:13 AM 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. July 16, 2026 at 11:19 AM 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. July 16, 2026 at 11:51 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 17, 2026 at 2:30 PM 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. June 17, 2026 at 5:16 PM UTCidentified

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

3. June 17, 2026 at 6:40 PM UTCidentified

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

4. June 17, 2026 at 10:37 PM 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. June 17, 2026 at 11:42 PM UTCmonitoring

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

6. June 18, 2026 at 6:38 AM UTCresolved

   This incident has been resolved.

1. June 12, 2026 at 2:31 PM 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. June 12, 2026 at 4:09 PM 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. June 12, 2026 at 4:09 PM UTCresolved

   This incident has been resolved.

1. June 4, 2026 at 1:15 PM 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. May 11, 2026 at 12:09 PM UTCinvestigating

   We are currently investigating this issue.

2. May 11, 2026 at 12:35 PM UTCinvestigating

   We are continuing to investigate this issue.

3. May 11, 2026 at 12:36 PM UTCmonitoring

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

4. May 14, 2026 at 11:34 AM UTCresolved

   This incident has been resolved.

1. May 9, 2026 at 6:48 PM 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. May 15, 2026 at 12:12 PM UTCresolved

   This incident has been resolved.

1. April 23, 2026 at 12:52 AM 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. April 23, 2026 at 2:41 AM UTCidentified

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

3. April 23, 2026 at 2:53 AM UTCmonitoring

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

4. April 23, 2026 at 2:53 AM UTCresolved

   This incident has been resolved.

1. April 16, 2026 at 2:23 PM 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. April 16, 2026 at 5:04 PM UTCidentified

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

3. April 16, 2026 at 5:04 PM UTCmonitoring

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

4. April 16, 2026 at 5:22 PM UTCresolved

   This incident has been resolved.

1. April 15, 2026 at 3:42 AM UTCinvestigating

   We identified an issue impacting data pipelines in the US-GCP region, which resulted in degraded performance. We are investigating the issue.

2. April 15, 2026 at 8:22 AM UTCinvestigating

   We are continuing to investigate this issue.

3. April 15, 2026 at 8:22 AM UTCresolved

   This incident has been resolved.

1. March 5, 2026 at 7:29 AM 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. March 5, 2026 at 7:33 AM 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. February 11, 2026 at 9:40 AM 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. February 11, 2026 at 2:47 PM UTCmonitoring

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

3. February 11, 2026 at 5:54 PM UTCresolved

   This incident has been resolved.

1. February 4, 2026 at 4:44 PM 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. February 4, 2026 at 4:45 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 4, 2026 at 5:02 PM 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. February 4, 2026 at 5:02 PM UTCidentified

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

5. February 4, 2026 at 5:19 PM UTCmonitoring

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

6. February 4, 2026 at 5:37 PM UTCresolved

   This incident has been resolved.

1. January 28, 2026 at 7:56 AM UTCinvestigating

   We are currently experiencing issues retrieving data for the Charge and Refund objects from Stripe. Our team is actively investigating the issue.

2. January 28, 2026 at 5:22 PM 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. January 28, 2026 at 5:23 PM UTCresolved

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

1. January 21, 2026 at 11:57 AM 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. January 21, 2026 at 7:07 PM UTCidentified

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

3. January 21, 2026 at 8:52 PM UTCmonitoring

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

4. January 21, 2026 at 8:52 PM UTCresolved

   This incident has been resolved.

1. December 22, 2025 at 4:17 PM 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. December 22, 2025 at 5:06 PM UTCinvestigating

   We are continuing to investigate this issue.

3. December 22, 2025 at 5:07 PM UTCidentified

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

4. December 22, 2025 at 5:30 PM 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. December 22, 2025 at 5:34 PM UTCresolved

   This incident has been resolved.

1. December 16, 2025 at 7:31 AM UTCidentified

   Snowflake is experiencing an outage in the US-West, AWS Europe, and AWS Asia Pacific Regions. This is impacting our Loading Job.

2. December 16, 2025 at 4:55 PM UTCmonitoring

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

3. December 16, 2025 at 4:59 PM UTCresolved

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

1. December 11, 2025 at 4:23 AM 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. December 11, 2025 at 4:45 AM UTCmonitoring

   We have patched the fix and are monitoring further.

3. December 11, 2025 at 4:54 AM UTCmonitoring

   We are continuing to monitor further.

4. December 11, 2025 at 5:10 AM UTCresolved

   This incident has been resolved.