Istoricul incidentelor Hevo

1. 21 septembrie 2026 la 23:59 UTCinvestigating

   Datorita unei pane AWS care a inceput pe 21 sep la 3:50 PM PDT, unele conducte Edge au fost afectate, rezultând în ingestie întârziată. Puteţi consulta pagina de stare AWS Health pentru ultimele actualizări: https://health.aws.amazon.com/health/status Suntem monitorizarea îndeaproape a situației și vă va ține la curent cu actualizările ulterioare.

2. 22 septembrie 2026 la 00:08 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 22 septembrie 2026 la 00:08 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 22 septembrie 2026 la 00:31 UTCresolved

   Acest incident a fost rezolvat. Incidentul AWS care afectează Hevo Edge a fost rezolvat, iar conductele afectate au revenit la procesarea normală. Am finalizat verificările de recuperare și am confirmat că serviciile și conductele afectate funcționează conform așteptărilor. Ca măsură de precauție, vă rugăm să revizuiți conductele critice și datele din aval. Dacă observaţi ceva neobişnuit, contactaţi Hevo Support la [email protected].

Traducere automată din actualizarea oficială a incidentului.

1. 2 august 2026 la 17:10 UTCidentified

   Problema a fost identificată şi lucrăm la o soluţie. Ora de începere a incidentului: 4:00 PM UTC

2. 2 august 2026 la 17:16 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele. Am identificat o problemă care afectează conductele de date și modelele din regiunea SUA. Ca servicii de recuperare, ne așteptăm ca conductele de date să experimenteze până la 1 oră de la decalajul de procesare. Vom continua să monitorizăm recuperarea și să oferim actualizări suplimentare, după caz.

3. 3 august 2026 la 02:45 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iulie 2026 la 06:37 UTCidentified

   Vedem în prezent eșecuri în conectorul Google Ads care afectează Ad Group și obiecte de campanie în urma recentei actualizări de la versiunea 21 la versiunea 24. Echipa noastră de Inginerie a identificat cauza principală şi lucrează activ la implementarea unui fix.

2. 31 iulie 2026 la 00:12 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 31 iulie 2026 la 05:21 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 19 iulie 2026 la 09:43 UTCmonitoring

   Am observat performanţe degradate care afectează Meta Ads API de la 08:42 - 09:30 UTC, ceea ce poate fi condus la ingestie întârziată de date pentru conductele Facebook Ads. Problema pare să fie rezolvată, iar serviciile au revenit la normal. Continuăm să monitorizăm îndeaproape situaţia.

2. 19 iulie 2026 la 10:00 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 08:38 UTCinvestigating

   Jurnalele actuale arată că nici unul dintre procesele de suport nu sunt afectate. Investigăm în prezent problema cu UI.

2. 16 iulie 2026 la 09:13 UTCidentified

   AWS investighează problema cu Amazon CloudFront. Pentru detalii suplimentare, vă rugăm să consultați PAGINA STATUS AWS: https://health.aws.amazon.com/health/status

3. 16 iulie 2026 la 11:19 UTCmonitoring

   Observăm acum răspunsuri sănătoase pentru cererile rutate prin intermediul CloudFront, iar UI ar trebui să fie accesibile între regiuni. Echipa încă monitorizează asta. Ultima actualizare de la AWS (11:16 AM UTC): https://health.aws.amazon.com/health/status

4. 16 iulie 2026 la 11:51 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 17 iunie 2026 la 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 iunie 2026 la 17:16 UTCidentified

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

3. 17 iunie 2026 la 18:40 UTCidentified

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

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

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

6. 18 iunie 2026 la 06:38 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 4 iunie 2026 la 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 la 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 11 mai 2026 la 12:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 mai 2026 la 12:36 UTCmonitoring

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

4. 14 mai 2026 la 11:34 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 23 aprilie 2026 la 02:53 UTCmonitoring

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

4. 23 aprilie 2026 la 02:53 UTCresolved

   This incident has been resolved.

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

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

3. 16 aprilie 2026 la 17:04 UTCmonitoring

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

4. 16 aprilie 2026 la 17:22 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 15 aprilie 2026 la 08:22 UTCresolved

   This incident has been resolved.

1. 5 martie 2026 la 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 martie 2026 la 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 februarie 2026 la 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 februarie 2026 la 14:47 UTCmonitoring

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

3. 11 februarie 2026 la 17:54 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

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

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

5. 4 februarie 2026 la 17:19 UTCmonitoring

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

6. 4 februarie 2026 la 17:37 UTCresolved

   This incident has been resolved.

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

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

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

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

3. 21 ianuarie 2026 la 20:52 UTCmonitoring

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

4. 21 ianuarie 2026 la 20:52 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 22 decembrie 2025 la 17:07 UTCidentified

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

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

   This incident has been resolved.

1. 16 decembrie 2025 la 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 decembrie 2025 la 16:55 UTCmonitoring

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

3. 16 decembrie 2025 la 16:59 UTCresolved

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