Istoricul incidentelor Helpshift

1. 31 august 2026 la 18:02 UTCinvestigating

   Suntem conştienţi de o pană de serviciu în curs de desfăşurare Fulg de zăpadă care afectează serviciile dependente de Fulg de zăpadă pentru recuperarea şi prelucrarea datelor. Impactul clientului: Serviciile afectate pot experimenta probleme de disponibilitate degradată, date întârziate sau funcții. Stare: Monitorizăm activ recuperarea Fulgului de Nea și evaluăm impactul asupra serviciilor noastre. Nu este necesară nicio acțiune din partea clienților în acest moment. Vom continua să oferim actualizări pe măsură ce situația progresează și vom confirma odată ce serviciile afectate au revenit la normal.

2. 31 august 2026 la 18:05 UTCinvestigating

   Continuăm să monitorizăm îndeaproape situaţia şi vom furniza actualizări suplimentare pe măsură ce problema progresează.

3. 31 august 2026 la 20:57 UTCresolved

   Problema cauzată de pana de fulgi de zăpadă a fost rezolvată. Următoarele servicii sunt acum pe deplin operaționale: Analiza tabloului de bord Putere BI Analytics API Recuperarea și prelucrarea datelor au revenit la normal și toate serviciile afectate funcționează conform așteptărilor. Dacă întâlniți orice probleme legate de, vă rugăm să nu ezitați să ajungeți la echipa noastră de sprijin la [email protected]. Ne cerem scuze pentru orice neplăceri cauzate şi apreciem răbdarea şi înţelegerea dumneavoastră.

Traducere automată din actualizarea oficială a incidentului.

1. 31 iulie 2026 la 12:31 UTCinvestigating

   În prezent experimentăm performanţe degradate care afectează pagina de suport Web. Utilizatorii pot întâmpina erori atunci când încearcă să creeze un bilet prin intermediul formularului Contact Us și forme inteligente.

2. 31 iulie 2026 la 14:23 UTCmonitoring

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

3. 31 iulie 2026 la 14:37 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 07:52 UTCinvestigating

   Ne confruntăm în prezent cu performanțe degradate care afectează tabloul de bord Analytics. Utilizatorii pot observa că funcția de sul nu funcționează așa cum se așteaptă.

2. 24 iulie 2026 la 09:23 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 7 iulie 2026 la 12:49 UTCinvestigating

   Avem în prezent o problemă cu Helpshift, în cazul în care unii agenți se confruntă cu erori sau latență pe tabloul de bord.

2. 7 iulie 2026 la 13:06 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 7 iulie 2026 la 13:59 UTCmonitoring

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

4. 7 iulie 2026 la 14:04 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 2 iulie 2026 la 12:03 UTCinvestigating

   În prezent experimentăm o pană de curent în jurul Automatizărilor, Boţilor şi Vizualizărilor Smart. Echipa noastră investighează problema și lucrează pentru a restabili serviciile cât mai repede posibil.

2. 2 iulie 2026 la 12:23 UTCidentified

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

3. 2 iulie 2026 la 12:39 UTCmonitoring

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

4. 2 iulie 2026 la 12:42 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iunie 2026 la 12:40 UTCinvestigating

   We are currently experiencing an outage impacting the Auto-assignment feature. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 16 iunie 2026 la 13:07 UTCidentified

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

3. 16 iunie 2026 la 13:09 UTCmonitoring

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

4. 16 iunie 2026 la 13:21 UTCresolved

   This incident has been resolved.

1. 4 iunie 2026 la 08:47 UTCinvestigating

   We are currently experiencing a service outage. Our team is investigating the issue and working to restore services as quickly as possible.

2. 4 iunie 2026 la 08:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 iunie 2026 la 09:04 UTCidentified

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

4. 4 iunie 2026 la 09:12 UTCmonitoring

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

5. 4 iunie 2026 la 09:31 UTCresolved

   This incident has been resolved.

1. 22 mai 2026 la 17:07 UTCinvestigating

   We are currently experiencing a service disruption impacting the Issue Analytics data pipeline. As a result, the pipeline is not processing data, and analytics data is currently delayed by approximately 6 hours. Affected Components: Analytics → Advanced Analytics → Issues (All) All Endpoints under the Analytics API. For the affected systems, data freshness is currently impacted beyond the last 6 hours. All other systems and platform functionalities remain fully operational. Our engineering team is actively investigating the issue and working continuously to restore normal operations as quickly as possible. We will keep providing updates until normal service is fully restored.

2. 22 mai 2026 la 18:38 UTCinvestigating

   We are actively continuing our investigation into this issue and working to identify the root cause. We will share further updates as soon as we have more information.

3. 22 mai 2026 la 18:48 UTCidentified

   We have identified the fix and are actively working on implementing it. The resolution involves restoring data from backups, and due to the large volume of data, the process is taking longer than expected. We will continue to share updates as more information becomes available.

4. 22 mai 2026 la 20:22 UTCmonitoring

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

5. 22 mai 2026 la 20:25 UTCresolved

   This incident has been resolved, and all impacted services are now operating as expected. If you encounter any related issues, please contact us at [email protected]. We sincerely apologize for any inconvenience caused.

1. 7 mai 2026 la 11:19 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 7 mai 2026 la 11:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 mai 2026 la 11:45 UTCidentified

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

4. 7 mai 2026 la 11:51 UTCmonitoring

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

5. 7 mai 2026 la 12:09 UTCresolved

   This incident has been resolved.

1. 5 mai 2026 la 12:19 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 5 mai 2026 la 13:56 UTCinvestigating

   We are actively continuing our investigation into this issue.

3. 5 mai 2026 la 15:32 UTCidentified

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

4. 5 mai 2026 la 16:43 UTCmonitoring

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

5. 5 mai 2026 la 18:11 UTCresolved

   The issue has been resolved, and all affected services are now functioning as expected. If you experience any issues, please contact our support team at [email protected]. We apologize for any inconvenience caused and appreciate your patience.

1. 5 mai 2026 la 10:04 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 5 mai 2026 la 11:33 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 mai 2026 la 11:56 UTCmonitoring

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

4. 5 mai 2026 la 12:06 UTCresolved

   This incident has been resolved.

1. 5 mai 2026 la 08:58 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 5 mai 2026 la 09:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 mai 2026 la 09:31 UTCidentified

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

4. 5 mai 2026 la 09:37 UTCmonitoring

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

5. 5 mai 2026 la 09:41 UTCresolved

   This incident has been resolved.

1. 14 aprilie 2026 la 12:47 UTCinvestigating

   We are currently experiencing a disruption in service. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. 14 aprilie 2026 la 13:06 UTCmonitoring

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

3. 14 aprilie 2026 la 13:08 UTCresolved

   This incident has been resolved.

1. 1 aprilie 2026 la 10:16 UTCinvestigating

   We are currently experiencing a service outage affecting Helpshift Automations. At the moment, users may be unable to create new automations or load existing ones. Our engineering team is actively working to restore the service as quickly as possible.

2. 1 aprilie 2026 la 10:28 UTCresolved

   This incident has been resolved.

1. 10 martie 2026 la 19:26 UTCinvestigating

   We are currently experiencing degraded performance on the Helpshift Dashboard, which may impact the following services: Chatbots Time-Based Automations New Issue Automations Our team is actively investigating the root cause and will keep you updated with further information.

2. 10 martie 2026 la 21:49 UTCidentified

   The root cause of the degraded performance has been determined, and a fix has been applied.

3. 10 martie 2026 la 22:20 UTCmonitoring

   The affected services are now functioning as expected, and we are actively monitoring performance to maintain stability.

4. 10 martie 2026 la 22:37 UTCresolved

   The issue has now been fully resolved and all services are operating normally. We apologize for any inconvenience caused and appreciate your patience while we worked on this. If you continue to experience any issues, please reach out to us at [email protected].

1. 17 februarie 2026 la 14:58 UTCinvestigating

   We are currently experiencing a partial degradation impacting the Team section of Dashboard Analytics. The following reports are affected: 1. Team – Trends (Overall) 2. Team – Trends (Workload) 3. Team – Summary by Agents

2. 17 februarie 2026 la 15:05 UTCidentified

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

3. 17 februarie 2026 la 15:15 UTCresolved

   This incident has been resolved.

1. 19 decembrie 2025 la 09:51 UTCinvestigating

   We are currently experiencing a degraded state with the AI Reply feature. Our engineering team is actively investigating the issue and working toward a resolution.

2. 19 decembrie 2025 la 09:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 decembrie 2025 la 11:06 UTCresolved

   This incident has been resolved.

1. 5 decembrie 2025 la 09:06 UTCinvestigating

   We are currently experiencing a service outage caused by an issue with our dependent Cloudflare services. This may impact access to Helpshift features and overall platform availability. As per the Cloudflare status page (https://www.cloudflarestatus.com/), their services are undergoing updates/maintenance, which may be contributing to the disruption.

2. 5 decembrie 2025 la 09:09 UTCresolved

   This incident has been resolved.

1. 5 decembrie 2025 la 07:01 UTCinvestigating

   Currently a Helpshift Service Outage is being experienced. We are actively Investigating the Issue.

2. 5 decembrie 2025 la 07:05 UTCmonitoring

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

3. 5 decembrie 2025 la 07:20 UTCresolved

   This incident has been resolved.

1. 27 noiembrie 2025 la 09:32 UTCinvestigating

   We are currently investigating this issue.

2. 27 noiembrie 2025 la 09:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 noiembrie 2025 la 09:58 UTCidentified

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

4. 27 noiembrie 2025 la 10:17 UTCidentified

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

5. 27 noiembrie 2025 la 10:22 UTCresolved

   This incident has been resolved.