Historial de interrupciones de Grasshopper

1. September 4, 2026 at 12:31 PM UTCinvestigating

   Estamos investigando activamente informes de que algunos clientes pueden estar experimentando problemas en la recepción de correos electrónicos de GoTo, incluyendo 2FA confirmaciones para Resolve, Rescate y GoToMyPC. Nuestros ingenieros están trabajando para identificar el problema y proporcionarán otra actualización en breve.

2. September 4, 2026 at 12:47 PM UTCidentified

   Nuestros ingenieros han identificado la tasa de entrega de correo electrónico está mejorando y están trabajando continuamente en una resolución con nuestro socio de correo electrónico. Vamos a proporcionar otra actualización en breve.

3. September 4, 2026 at 12:59 PM UTCmonitoring

   Nuestro socio ha corregido el problema y estamos viendo estabilidad sostenida en los servicios de correo electrónico. Seguiremos vigilando la situación y proporcionaremos una actualización final en breve.

4. September 4, 2026 at 1:31 PM UTCresolved

   Hemos confirmado que la cuestión se ha resuelto y que todos los sistemas son 100% operativos. Llevaremos a cabo un examen interno de esta cuestión y haremos mejoras apropiadas a nuestro sistema para ayudar a prevenir o minimizar la repetición futura.

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

1. August 27, 2026 at 3:55 PM UTCidentified

   Nuestros ingenieros están investigando problemas con la firma de códigos para Rescate, GoToAsist v5, Pro y Central, lo que puede conducir a fallos intermitentes al iniciar las sesiones. Vamos a proporcionar otra actualización en breve.

2. August 27, 2026 at 4:38 PM UTCidentified

   Nuestros ingenieros continúan investigando los problemas de firma de códigos reportados para Rescate, GoTo Assist v5, Pro y Central. Vamos a proporcionar otra actualización en breve.

3. August 27, 2026 at 5:40 PM UTCmonitoring

   Nuestros ingenieros están viendo una mejora en la situación y estamos confirmando que todos los servicios son funcionales. Seguiremos vigilando la situación y proporcionaremos una actualización final en breve.

4. August 28, 2026 at 4:24 PM UTCresolved

   Hemos confirmado que la cuestión se ha resuelto y que todos los sistemas son 100% operativos. Llevaremos a cabo un examen interno de esta cuestión y haremos mejoras apropiadas a nuestro sistema para ayudar a prevenir o minimizar la repetición futura.

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

1. August 15, 2026 at 3:02 PM UTCidentified

   Nuestros ingenieros son conscientes de un problema que afecta el restablecimiento de contraseñas y correos electrónicos OTP que impactan a los usuarios de Microsoft365 y Outlook. Hemos identificado la cuestión como una cuestión de proveedores, y nos hemos comprometido con ellos para trabajar hacia la resolución. Vamos a proporcionar otra actualización en breve.

2. August 15, 2026 at 3:52 PM UTCmonitoring

   Nuestros ingenieros están empezando a ver signos de recuperación después de una mitigación interna, ya que continúan involucrando al proveedor para la resolución final. Estamos viendo que las retries tienen éxito, tal que los usuarios afectados han podido recibir contraseña y tráfico de autenticación. Seguiremos vigilando la situación y proporcionaremos una actualización final en breve.

3. August 15, 2026 at 4:33 PM UTCresolved

   Hemos confirmado que la cuestión se ha resuelto y que todos los sistemas son 100% operativos. Llevaremos a cabo un examen interno de esta cuestión y haremos mejoras apropiadas a nuestro sistema para ayudar a prevenir o minimizar la repetición futura.

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

1. August 4, 2026 at 6:11 PM UTCidentified

   Nuestro equipo está trabajando en un tema relativo a las campañas de WhatsApp. Hasta que esto se resuelva, hemos desactivado temporalmente las siguientes características y añadido una notificación de solicitud para los clientes afectados. - Los clientes no pueden enviar campañas ni iniciar conversaciones externas - Los clientes no pueden a bordo nuevos números de WhatsApp Las campañas de SMS no son afectadas por esto y siguen siendo funcionales. Trabajamos con Meta para resolver esta situación y publicaremos una actualización lo antes posible.

2. August 7, 2026 at 7:44 PM UTCidentified

   Todavía estamos totalmente comprometidos en la resolución del incidente y estamos intensificando el asunto con Meta en todos los medios disponibles. Publicaremos otra actualización tan pronto como la situación avance.

3. August 13, 2026 at 5:48 PM UTCidentified

   Our engineers have made progress on the escalation with Meta and we are working to re-enable the Whatsapp 1-to-1 template features for all affected customers. WhatsApp campaigns are being addressed separately and remain unavailable for now. We will update this page as soon as we have a restoration estimate for this feature.

4. August 14, 2026 at 3:11 PM UTCmonitoring

   Following the re-enablement of 1-to-1 templates yesterday, our engineers have re-enabled WhatAapp campaigns for all affected customers. A reload of the GoTo App will be necessary to access this feature again.

5. August 14, 2026 at 4:09 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

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

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

   Estamos investigando activamente informes de que algunos clientes de Pro y Central pueden estar experimentando problemas al intentar iniciar sesión. Nuestros ingenieros están trabajando para identificar el problema y proporcionarán otra actualización en breve.

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

   Nuestros ingenieros siguen trabajando para identificar la fuente de este problema y proporcionarán otra actualización en breve.

3. July 3, 2026 at 1:23 PM UTCidentified

   Nuestros ingenieros han identificado la cuestión y ahora están trabajando activamente en una resolución. Vamos a proporcionar otra actualización en breve.

4. July 3, 2026 at 2:05 PM UTCidentified

   Nuestros ingenieros han realizado un cambio que ayudará a restaurar la funcionalidad. Sin embargo, puede tomar hasta 4 horas para tener pleno efecto. Mientras tanto, el login puede estar trabajando intermitentemente. El equipo también está mirando otras opciones para llegar a una recuperación más rápida. Vamos a proporcionar otra actualización en breve.

5. July 3, 2026 at 3:08 PM UTCidentified

   Nuestros ingenieros han realizado un cambio para restaurar la funcionalidad. Todavía está en marcha para tener pleno efecto. Mientras tanto, el login puede estar trabajando intermitentemente. El equipo también está mirando otras opciones para llegar a una recuperación más rápida. Proporcionaremos otra actualización cuando se disponga de nueva información.

6. July 3, 2026 at 4:02 PM UTCidentified

   Nuestros ingenieros siguen de cerca la evolución del cambio hacia la resolución mientras investigan una opción más rápida. Iniciar sesión todavía puede estar trabajando intermitentemente. Vamos a proporcionar otra actualización pronto.

7. July 3, 2026 at 6:21 PM UTCidentified

   Nuestros ingenieros han identificado que el cambio no produjo el resultado esperado y ahora están trabajando en una solución alternativa. Vamos a proporcionar otra actualización en breve.

8. July 3, 2026 at 7:21 PM UTCidentified

   Nuestros ingenieros están viendo señales de mejoras para Join.me, Pro y Central y siguen trabajando en resolución para GoToMyPC. Vamos a proporcionar otra actualización en breve.

9. July 3, 2026 at 7:55 PM UTCmonitoring

   Nuestros ingenieros han corregido el problema y estamos confirmando que todos los servicios son funcionales. Seguiremos vigilando la situación y proporcionaremos una actualización final.

10. July 3, 2026 at 8:25 PM UTCresolved

    Hemos confirmado que la cuestión se ha resuelto y que todos los sistemas son 100% operativos. Llevaremos a cabo un examen interno de esta cuestión y haremos mejoras apropiadas a nuestro sistema para ayudar a prevenir o minimizar la repetición futura.

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

1. July 2, 2026 at 11:49 AM UTCinvestigating

   Estamos investigando activamente informes de que un subconjunto de clientes de GoTo Connect puede estar experimentando problemas con llamadas inbound y outbound. Nuestros ingenieros están trabajando para identificar el problema y proporcionarán otra actualización en breve.

2. July 2, 2026 at 11:54 AM UTCidentified

   Nuestros ingenieros han identificado el tema y ahora están trabajando activamente para una resolución. Vamos a proporcionar otra actualización en breve.

3. July 2, 2026 at 1:43 PM UTCidentified

   Nuestros ingenieros continúan investigando el tema y están trabajando activamente para determinar el mejor camino hacia la resolución. Vamos a proporcionar otra actualización en breve.

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

   Nuestros ingenieros están trabajando actualmente en un plan para mitigar los problemas y seguir trabajando en la resolución. Vamos a proporcionar otra actualización en breve.

5. July 2, 2026 at 3:14 PM UTCidentified

   Nuestros ingenieros siguen implementando una solución para el tema. Vamos a proporcionar otra actualización en breve.

6. July 2, 2026 at 4:06 PM UTCidentified

   Nuestros ingenieros continúan investigando varias causas subyacentes que dan lugar a la cuestión conocida. Esto incluye identificar y seguir patrones, así como entender el impacto completo del cliente es. En este momento, la investigación continúa. Vamos a proporcionar actualizaciones adicionales en breve.

7. July 2, 2026 at 4:36 PM UTCmonitoring

   Nuestros ingenieros han implementado una solución que ha abordado los problemas de llamadas inbound/outbound que fueron reportados, y ahora estamos monitoreando para la estabilidad continua. Presentaremos una actualización final en breve.

8. July 2, 2026 at 6:27 PM UTCresolved

   Nuestros ingenieros están viendo ahora que todos los servicios son funcionales. Realizaremos un examen interno de esta cuestión y haremos mejoras apropiadas para asegurar que esta cuestión no vuelva a ocurrir.

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

1. July 1, 2026 at 9:43 AM UTCinvestigating

   Estamos investigando activamente informes de que un subconjunto de clientes de GoTo Connect puede estar experimentando problemas con llamadas inbound y outbound. Nuestros ingenieros están trabajando para identificar el problema y proporcionarán otra actualización en breve.

2. July 1, 2026 at 10:08 AM UTCidentified

   Nuestros ingenieros han identificado el tema y ahora están trabajando activamente para una resolución. Vamos a proporcionar otra actualización en breve.

3. July 1, 2026 at 10:40 AM UTCmonitoring

   Nuestros ingenieros han corregido el problema, y estamos confirmando que todos los servicios son funcionales. Seguiremos vigilando la situación y proporcionaremos una actualización final en breve.

4. July 1, 2026 at 10:43 AM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. July 1, 2026 at 10:50 AM UTCresolved

   Hemos confirmado que la cuestión se ha resuelto y que todos los sistemas son 100% operativos. Llevaremos a cabo un examen interno de esta cuestión y haremos mejoras apropiadas a nuestro sistema para ayudar a prevenir o minimizar la repetición futura.

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

1. June 19, 2026 at 8:33 AM UTCinvestigating

   We are actively investigating reports of an impact affecting GoTo Connect, including Call History, Virtual Receptionist Reporting, Voicemail Deletion, and Call-Report Ingestion. Our engineers are working to identify the issue and will provide another update shortly.

2. June 19, 2026 at 8:38 AM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. June 19, 2026 at 10:08 AM UTCidentified

   Our engineers continue to investigate the issue. We will provide another update as soon as it is available.

4. June 19, 2026 at 12:39 PM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

5. June 19, 2026 at 1:11 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. May 28, 2026 at 2:17 PM UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing authentication issues accessing the GoTo app or GoTo Admin or Analytics portals. Our engineers are working to identify the issue and will provide another update shortly.

2. May 28, 2026 at 2:28 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. May 28, 2026 at 2:49 PM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. May 28, 2026 at 2:57 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. May 27, 2026 at 3:17 PM UTCinvestigating

   We are actively investigating an issue with Logmein Rescue may have issues starting or joining remote sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. May 27, 2026 at 3:45 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We are seeing gradual improvement and continuing to monitor the progress. We will provide another update shortly.

3. May 27, 2026 at 3:48 PM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. May 27, 2026 at 3:57 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. May 13, 2026 at 6:58 PM UTCinvestigating

   We are actively investigating reports that some LogMeIn Rescue and Central customers may be experiencing issues downloading the applet to start or join remote sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. May 13, 2026 at 7:22 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. May 13, 2026 at 8:04 PM UTCidentified

   Our engineers are continuing to work on this issue and continue to work towards a resolution. We will provide another update shortly.

4. May 13, 2026 at 9:13 PM UTCidentified

   Our engineers are continuing to work on isolating the source of this issue. Due to its intermittent nature, trying again can allow to establish a proper connection. We will provide another update shortly.

5. May 13, 2026 at 10:28 PM UTCmonitoring

   A potential fix was applied to resolve the issue, and we are continuing to monitor for stability. We will continue monitoring the situation and provide a final update shortly.

6. May 13, 2026 at 10:40 PM UTCidentified

   Our engineers are still seeing some intermittent issues after the fix and are continuing to investigate those. We will provide a status update once we have further information. We will provide another update shortly.

7. May 14, 2026 at 12:37 AM UTCidentified

   We are continuing to work towards a resolution to ensure stability in starting and joining sessions. We will provide another update shortly.

8. May 14, 2026 at 1:12 AM UTCidentified

   Our engineers have identified a plan to get back the system to stustained stability and are starting to execute on it. We will provide another update shortly.

9. May 14, 2026 at 2:03 AM UTCidentified

   Our engineers are executing on the established plan to get back the system to prolonged stability We will provide another update shortly.

10. May 14, 2026 at 2:12 AM UTCmonitoring

    Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

11. May 14, 2026 at 2:22 AM UTCresolved

    We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. May 8, 2026 at 1:22 AM UTCinvestigating

   We are actively investigating reports that some Grasshopper customers may be experiencing login issues on apps. Our engineers are working to identify the issue and will provide another update shortly.

2. May 8, 2026 at 2:09 AM UTCinvestigating

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. May 8, 2026 at 4:10 AM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. May 8, 2026 at 5:11 PM UTCresolved

   We have confirmed that the issue has been resolved and all systems are 100% operational at this time. We will conduct an internal investigation of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. May 7, 2026 at 6:31 PM UTCidentified

   Our engineers have identified the issue with call recordings and transcripts availability delay and are now actively working towards a resolution. We will provide another update shortly.

2. May 8, 2026 at 1:54 AM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

3. May 8, 2026 at 2:01 AM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. May 6, 2026 at 4:55 PM UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing issue opening the app. Our engineers are working to identify the issue and will provide another update shortly.

2. May 6, 2026 at 4:57 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. May 6, 2026 at 5:06 PM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. May 6, 2026 at 5:23 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. April 20, 2026 at 2:14 PM UTCinvestigating

   We are actively investigating reports that some GoTo Meeting and GoTo Admin customers may be experiencing timeouts when performing operations in GoTo Admin and GoTo Meeting components. Our engineers are working to identify the issue and will provide another update shortly.

2. April 20, 2026 at 2:34 PM UTCidentified

   Our engineers have identified the issue and are actively working to correct the underlying cause. This issue appears to have impacted functionality with GoTo Admin, GoTo Connect, Contact Center, Analytics, Resolve, and other related services. We will provide another update shortly.

3. April 20, 2026 at 2:55 PM UTCidentified

   This issue affects authentication to the various GoTo applications, which also affects Resolve, Pro/Central, in addition to GoTo Admin, Connect and Meetings. We will provide another update shortly.

4. April 20, 2026 at 3:12 PM UTCidentified

   Our engineers are seeing signs of recovery for login to our applications. Our team is still engaged in ensuring prolonged stability of the applications. We will provide another update shortly.

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

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

6. April 20, 2026 at 3:23 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. April 15, 2026 at 9:08 PM UTCinvestigating

   We are actively investigating reports that some GoTo Connect VoIP Phones Calls customers may be experiencing intermittent issues completing inbound calls. Our engineers are working to identify the issue and will provide another update shortly.

2. April 15, 2026 at 9:15 PM UTCidentified

   Our engineers have identified the issue as being caused by an ongoing incident with one of our underlying third-party service providers who are actively working towards a resolution. We will provide another update as soon as they become available.

3. April 15, 2026 at 9:38 PM UTCmonitoring

   Our underlying third-party service provider has corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. April 15, 2026 at 9:41 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. April 6, 2026 at 12:58 PM UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing issues with call quality for GoToConnect Web, Desktop and Mobile. Our engineers are working to identify the issue and will provide another update shortly.

2. April 6, 2026 at 1:16 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. April 6, 2026 at 1:43 PM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. April 6, 2026 at 1:47 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. March 25, 2026 at 4:08 PM UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing audio issues on calls Our engineers are working to identify the issue and will provide another update shortly.

2. March 25, 2026 at 4:15 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. March 25, 2026 at 4:20 PM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. March 25, 2026 at 4:35 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. March 18, 2026 at 3:37 PM UTCinvestigating

   We are actively investigating reports that some GoTo Webinar customers may be experiencing an issue starting sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. March 18, 2026 at 3:51 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. March 18, 2026 at 3:58 PM UTCidentified

   We are seeing improvements in GoTo Webinar, Training and Meeting as mitigating actions are being deployed. We will provide another update shortly.

4. March 18, 2026 at 4:04 PM UTCmonitoring

   Our engineers have corrected the issue and we are monitoring recovery across all services which were affected. We will continue monitoring the situation and provide a final update shortly.

5. March 18, 2026 at 6:19 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational.

1. February 27, 2026 at 3:52 PM UTCinvestigating

   We are actively investigating reports that some Contact Center – Call Queue customers may be experiencing issues with queue calls not being distributed to Contact Center agents. Our engineers are working to identify the issue and will provide another update shortly.

2. February 27, 2026 at 5:20 PM UTCinvestigating

   We are continuing to investigate the reports of call queue distribution issues. Our engineers are still fully engaged to identify the source of issue and will provide another update shortly.

3. February 27, 2026 at 6:00 PM UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

4. February 27, 2026 at 6:42 PM UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

5. February 27, 2026 at 7:15 PM UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.