Histórico de interrupções do Hevo

1. 21 Gwengolo 2026 da 23:59 UTCinvestigating

   Devido a uma falha da AWS que começou em 21 de setembro às 3:50 PM PDT, alguns oleodutos Edge foram afetados, resultando em ingestão tardia. Você pode consultar a página de status AWS Health para as últimas atualizações: https://health.aws.amazon.com/health/status Estamos acompanhando de perto a situação e vamos mantê-lo informado sobre as atualizações adicionais.

2. 22 Gwengolo 2026 da 00:08 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 22 Gwengolo 2026 da 00:08 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 22 Gwengolo 2026 da 00:31 UTCresolved

   Este incidente foi resolvido. O incidente AWS que afeta Hevo Edge foi resolvido, e os oleodutos afetados retornaram ao processamento normal. Completamos as verificações de recuperação e confirmamos que os serviços e gasodutos afetados estão funcionando como esperado. Como precaução, por favor, reveja seus pipelines críticos e dados a jusante. Se você notar algo incomum, entre em contato com o Hevo Support em [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Eost 2026 da 17:10 UTCidentified

   A questão foi identificada e estamos a trabalhar numa solução. Hora de início do incidente: 16:00 UTC

2. 2 Eost 2026 da 17:16 UTCmonitoring

   Foi implementada uma solução e estamos a acompanhar os resultados. Identificamos um problema impactando pipelines de dados e modelos na região dos EUA. Como os serviços recuperam, esperamos que os pipelines de dados experimentem até 1 hora de atraso de processamento. Continuaremos a monitorar a recuperação e fornecer atualizações adicionais conforme necessário.

3. 3 Eost 2026 da 02:45 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Gouere 2026 da 06:37 UTCidentified

   Atualmente, estamos vendo falhas no conector do Google Ads afetando os objetos do Grupo de Anúncios e Campanha após a atualização recente da versão 21 para a versão 24. Nossa equipe de engenharia identificou a causa raiz e está trabalhando ativamente na implementação de uma correção.

2. 31 Gouere 2026 da 00:12 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 31 Gouere 2026 da 05:21 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Gouere 2026 da 09:43 UTCmonitoring

   Observamos desempenho degradado afetando a API do Meta Ads de 08:42 - 09:30 UTC, o que pode ter resultado em atraso na ingestão de dados para pipelines do Facebook Ads. A questão parece estar resolvida e os serviços voltaram ao normal. Continuamos a acompanhar de perto a situação.

2. 19 Gouere 2026 da 10:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 08:38 UTCinvestigating

   Os registros atuais mostram que nenhum dos processos de infraestrutura é impactado. Estamos a investigar o problema com a UI.

2. 16 Gouere 2026 da 09:13 UTCidentified

   A AWS está investigando o problema com a Amazon CloudFront. Para mais informações, consultar a PAGE AWS STATUS: https://health.aws.amazon.com/health/status

3. 16 Gouere 2026 da 11:19 UTCmonitoring

   Estamos agora observando respostas saudáveis para pedidos encaminhados através do CloudFront, e a UI deve ser acessível em todas as regiões. A equipa ainda está a monitorizar isto. Última actualização do AWS (11:16 AM UTC): https://health.aws.amazon.com/health/status

4. 16 Gouere 2026 da 11:51 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

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

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

3. 17 Mezheven 2026 da 18:40 UTCidentified

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

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

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

6. 18 Mezheven 2026 da 06:38 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 4 Mezheven 2026 da 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 Mae 2026 da 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 11 Mae 2026 da 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 Mae 2026 da 12:36 UTCmonitoring

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

4. 14 Mae 2026 da 11:34 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 23 Ebrel 2026 da 02:53 UTCmonitoring

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

4. 23 Ebrel 2026 da 02:53 UTCresolved

   This incident has been resolved.

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

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

3. 16 Ebrel 2026 da 17:04 UTCmonitoring

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

4. 16 Ebrel 2026 da 17:22 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 15 Ebrel 2026 da 08:22 UTCresolved

   This incident has been resolved.

1. 5 Meurzh 2026 da 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 Meurzh 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 14:47 UTCmonitoring

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

3. 11 Cʼhwevrer 2026 da 17:54 UTCresolved

   This incident has been resolved.

1. 4 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 16:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 17:02 UTCidentified

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

5. 4 Cʼhwevrer 2026 da 17:19 UTCmonitoring

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

6. 4 Cʼhwevrer 2026 da 17:37 UTCresolved

   This incident has been resolved.

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

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

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

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

3. 21 Genver 2026 da 20:52 UTCmonitoring

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

4. 21 Genver 2026 da 20:52 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 22 Kerzu 2025 da 17:07 UTCidentified

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

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

   This incident has been resolved.

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

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

3. 16 Kerzu 2025 da 16:59 UTCresolved

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