Historial de interrupciones de Helpshift

1. August 31, 2026 at 6:02 PM UTCinvestigating

   Somos conscientes de un servicio continuo de Snowflake que está impactando servicios dependientes de Snowflake para la recuperación de datos y procesamiento. Impacto del cliente: Los servicios afectados pueden experimentar disponibilidad degradada, datos retrasados o problemas de funcionalidad. Situación: Estamos monitoreando activamente la recuperación de Snowflake y evaluando el impacto en nuestros servicios. No se requiere ninguna acción de los clientes en este momento. Seguiremos proporcionando actualizaciones a medida que avance la situación y confirmaremos una vez que los servicios afectados hayan regresado a la normalidad.

2. August 31, 2026 at 6:05 PM UTCinvestigating

   Seguimos vigilando de cerca la situación y proporcionaremos más actualizaciones a medida que avance la cuestión.

3. August 31, 2026 at 8:57 PM UTCresolved

   Se ha resuelto el problema causado por el saqueo de Snowflake. Los siguientes servicios están en pleno funcionamiento: Dashboard Analytics Power BI Analytics API La recuperación de datos y el procesamiento han regresado a la normalidad, y todos los servicios afectados funcionan según lo previsto. Si encuentras problemas relacionados, no dudes en contactar con nuestro equipo de Soporte en [email protected]. Nos disculpamos por cualquier inconveniente causado y apreciamos su paciencia y comprensión.

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

1. July 31, 2026 at 12:31 PM UTCinvestigating

   Actualmente estamos experimentando un rendimiento degradado que impacta en la Página de Soporte Web. Los usuarios pueden encontrar errores al intentar crear un ticket a través del formulario Contact Us y Smart Forms.

2. July 31, 2026 at 2:23 PM UTCmonitoring

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

3. July 31, 2026 at 2:37 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 24, 2026 at 7:52 AM UTCinvestigating

   Actualmente estamos experimentando un rendimiento degradado que afecta al panel de análisis. Los usuarios pueden notar que la función de desplazamiento no funciona como se espera.

2. July 24, 2026 at 9:23 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 7, 2026 at 12:49 PM UTCinvestigating

   Actualmente estamos experimentando un problema con Helpshift, donde algunos agentes están encontrando errores o latencia en el panel de control.

2. July 7, 2026 at 1:06 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 7, 2026 at 1:59 PM UTCmonitoring

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

4. July 7, 2026 at 2:04 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 2, 2026 at 12:03 PM UTCinvestigating

   Actualmente estamos experimentando un Outage en torno a Automations,Bots y Smart Views. Nuestro equipo está investigando la cuestión y trabajando para restaurar los servicios lo antes posible.

2. July 2, 2026 at 12:23 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. July 2, 2026 at 12:39 PM UTCmonitoring

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

4. July 2, 2026 at 12:42 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 16, 2026 at 12:40 PM 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. June 16, 2026 at 1:07 PM UTCidentified

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

3. June 16, 2026 at 1:09 PM UTCmonitoring

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

4. June 16, 2026 at 1:21 PM UTCresolved

   This incident has been resolved.

1. June 4, 2026 at 8:47 AM UTCinvestigating

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

2. June 4, 2026 at 8:59 AM UTCinvestigating

   We are continuing to investigate this issue.

3. June 4, 2026 at 9:04 AM UTCidentified

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

4. June 4, 2026 at 9:12 AM UTCmonitoring

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

5. June 4, 2026 at 9:31 AM UTCresolved

   This incident has been resolved.

1. May 22, 2026 at 5:07 PM 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. May 22, 2026 at 6:38 PM 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. May 22, 2026 at 6:48 PM 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. May 22, 2026 at 8:22 PM UTCmonitoring

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

5. May 22, 2026 at 8:25 PM 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. May 7, 2026 at 11:19 AM 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. May 7, 2026 at 11:32 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 7, 2026 at 11:45 AM UTCidentified

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

4. May 7, 2026 at 11:51 AM UTCmonitoring

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

5. May 7, 2026 at 12:09 PM UTCresolved

   This incident has been resolved.

1. May 5, 2026 at 12:19 PM 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. May 5, 2026 at 1:56 PM UTCinvestigating

   We are actively continuing our investigation into this issue.

3. May 5, 2026 at 3:32 PM UTCidentified

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

4. May 5, 2026 at 4:43 PM UTCmonitoring

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

5. May 5, 2026 at 6:11 PM 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. May 5, 2026 at 10:04 AM 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. May 5, 2026 at 11:33 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 5, 2026 at 11:56 AM UTCmonitoring

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

4. May 5, 2026 at 12:06 PM UTCresolved

   This incident has been resolved.

1. May 5, 2026 at 8:58 AM 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. May 5, 2026 at 9:23 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 5, 2026 at 9:31 AM UTCidentified

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

4. May 5, 2026 at 9:37 AM UTCmonitoring

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

5. May 5, 2026 at 9:41 AM UTCresolved

   This incident has been resolved.

1. April 14, 2026 at 12:47 PM 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. April 14, 2026 at 1:06 PM UTCmonitoring

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

3. April 14, 2026 at 1:08 PM UTCresolved

   This incident has been resolved.

1. April 1, 2026 at 10:16 AM 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. April 1, 2026 at 10:28 AM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 7:26 PM 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. March 10, 2026 at 9:49 PM UTCidentified

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

3. March 10, 2026 at 10:20 PM UTCmonitoring

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

4. March 10, 2026 at 10:37 PM 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. February 17, 2026 at 2:58 PM 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. February 17, 2026 at 3:05 PM UTCidentified

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

3. February 17, 2026 at 3:15 PM UTCresolved

   This incident has been resolved.

1. December 19, 2025 at 9:51 AM 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. December 19, 2025 at 9:58 AM UTCinvestigating

   We are continuing to investigate this issue.

3. December 19, 2025 at 11:06 AM UTCresolved

   This incident has been resolved.

1. December 5, 2025 at 9:06 AM 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. December 5, 2025 at 9:09 AM UTCresolved

   This incident has been resolved.

1. December 5, 2025 at 7:01 AM UTCinvestigating

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

2. December 5, 2025 at 7:05 AM UTCmonitoring

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

3. December 5, 2025 at 7:20 AM UTCresolved

   This incident has been resolved.

1. November 27, 2025 at 9:32 AM UTCinvestigating

   We are currently investigating this issue.

2. November 27, 2025 at 9:53 AM UTCinvestigating

   We are continuing to investigate this issue.

3. November 27, 2025 at 9:58 AM UTCidentified

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

4. November 27, 2025 at 10:17 AM UTCidentified

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

5. November 27, 2025 at 10:22 AM UTCresolved

   This incident has been resolved.