История сбоев Goto Apis

1. 4 сентября 2026 г. в 12:31 UTCinvestigating

   Мы активно изучаем сообщения о том, что некоторые клиенты могут испытывать проблемы с получением электронных писем от GoTo, в том числе 2FA-подтверждения для Resolve, Rescue и GoToMyPC. Наши инженеры работают над выявлением проблемы и в ближайшее время предоставят еще одно обновление.

2. 4 сентября 2026 г. в 12:47 UTCidentified

   Наши инженеры определили, что скорость доставки электронной почты улучшается и постоянно работают над разрешением с нашим партнером по доставке почты. В ближайшее время мы предоставим еще одно обновление.

3. 4 сентября 2026 г. в 12:59 UTCmonitoring

   Наш партнер исправил проблему, и мы видим устойчивую стабильность в службах электронной почты. Мы продолжим следить за ситуацией и в ближайшее время предоставим окончательную информацию.

4. 4 сентября 2026 г. в 13:31 UTCresolved

   Мы подтвердили, что проблема решена и все системы работают на 100%. Мы проведем внутренний обзор этого вопроса и внесем соответствующие улучшения в нашу систему, чтобы помочь предотвратить или свести к минимуму будущие рецидивы.

Автоматический перевод официального обновления инцидента.

1. 27 августа 2026 г. в 15:55 UTCidentified

   Наши инженеры изучают проблемы с подписанием кода для Rescue, GoToAssist v5, Pro и Central, что может привести к периодическим сбоям при запуске сеансов. В ближайшее время мы предоставим еще одно обновление.

2. 27 августа 2026 г. в 16:38 UTCidentified

   Наши инженеры продолжают исследовать проблемы с подписанием кода для Rescue, GoTo Assist v5, Pro и Central. В ближайшее время мы предоставим еще одно обновление.

3. 27 августа 2026 г. в 17:40 UTCmonitoring

   Наши инженеры видят улучшение ситуации, и мы подтверждаем, что все службы работают. Мы продолжим следить за ситуацией и в ближайшее время предоставим окончательную информацию.

4. 28 августа 2026 г. в 16:24 UTCresolved

   Мы подтвердили, что проблема решена и все системы работают на 100%. Мы проведем внутренний обзор этого вопроса и внесем соответствующие улучшения в нашу систему, чтобы помочь предотвратить или свести к минимуму будущие рецидивы.

Автоматический перевод официального обновления инцидента.

1. 15 августа 2026 г. в 15:02 UTCidentified

   Наши инженеры знают о проблеме, затрагивающей сброс паролей и OTP-сообщения, затрагивающие пользователей Microsoft365 и Outlook. Мы определили проблему как проблему поставщика, и мы сотрудничали с ними, чтобы работать над ее решением. В ближайшее время мы предоставим еще одно обновление.

2. 15 августа 2026 г. в 15:52 UTCmonitoring

   Наши инженеры начинают видеть признаки восстановления после внутреннего смягчения, поскольку они продолжают привлекать поставщика для окончательного разрешения. Мы видим, что повторные попытки успешны, так что пострадавшие пользователи смогли получить трафик паролей и аутентификации. Мы продолжим следить за ситуацией и в ближайшее время предоставим окончательную информацию.

3. 15 августа 2026 г. в 16:33 UTCresolved

   Мы подтвердили, что проблема решена и все системы работают на 100%. Мы проведем внутренний обзор этого вопроса и внесем соответствующие улучшения в нашу систему, чтобы помочь предотвратить или свести к минимуму будущие рецидивы.

Автоматический перевод официального обновления инцидента.

1. 4 августа 2026 г. в 18:11 UTCidentified

   Our team is working on an issue regarding WhatsApp campaigns. Until this is resolved, we have temporarily disabled the following features and added an in-app notification for the affected customers. - Customers cannot send campaigns or initiate outbound conversations - Customers cannot onboard new WhatsApp numbers SMS campaigns are unaffected by this and remain functional. We are working with Meta to resolve this situation and will post an update as soon as possible.

2. 7 августа 2026 г. в 19:44 UTCidentified

   We are still fully engaged in the incident's resolution and are escalating the matter with Meta on all means available. We will post another update as soon as the situation progresses.

3. 13 августа 2026 г. в 17:48 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. 14 августа 2026 г. в 15:11 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. 14 августа 2026 г. в 16:09 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. 3 июля 2026 г. в 12:03 UTCinvestigating

   We are actively investigating reports that some Pro and Central customers may be experiencing issues when trying to login. Our engineers are working to identify the issue and will provide another update shortly.

2. 3 июля 2026 г. в 12:39 UTCinvestigating

   Our engineers are still working to identify the source of this issue and will provide another update shortly.

3. 3 июля 2026 г. в 13:23 UTCidentified

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

4. 3 июля 2026 г. в 14:05 UTCidentified

   Our engineers have performed a change which will help restore functionality. However, it can take up to 4 hours to take full effect. In the meantime, login can be intermittently working. The team is also looking at other options to get to a faster recovery. We will provide another update shortly.

5. 3 июля 2026 г. в 15:08 UTCidentified

   Our engineers have performed a change to restore functionality. It is still in progress to take full effect. In the meantime, login can be intermittently working. The team is also still looking at other options to get to a faster recovery. We will provide another update when new information is available.

6. 3 июля 2026 г. в 16:02 UTCidentified

   Our engineers follow closely the change's progression towards resolution while investigating a faster option. Login can still be intermittently working. We will provide another update soon.

7. 3 июля 2026 г. в 18:21 UTCidentified

   Our engineers have identified that change did not produce the expected outcome and are now working on an alternate solution. We will provide another update shortly.

8. 3 июля 2026 г. в 19:21 UTCidentified

   Our engineers are seeing signs of improvements for Join.me, Pro and Central and still working on resolution for GoToMyPC. We will provide another update shortly.

9. 3 июля 2026 г. в 19:55 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.

10. 3 июля 2026 г. в 20:25 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. 2 июля 2026 г. в 11:49 UTCinvestigating

   We are actively investigating reports that a subset of GoTo Connect customers may be experiencing issues with inbound and outbound calls. Our engineers are working to identify the issue and will provide another update shortly.

2. 2 июля 2026 г. в 11:54 UTCidentified

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

3. 2 июля 2026 г. в 13:43 UTCidentified

   Our engineers continue to investigate the issue and are actively working to determine the best path toward resolution. We will provide another update shortly.

4. 2 июля 2026 г. в 14:12 UTCidentified

   Our engineers are currently working on a plan to mitigate the issues and continue working toward resolution. We will provide another update shortly.

5. 2 июля 2026 г. в 15:14 UTCidentified

   Our engineers are continuing to implement a fix for the issue. We will provide another update shortly.

6. 2 июля 2026 г. в 16:06 UTCidentified

   Our engineers are continuing to investigate several underlying causes that result in the known issue. This includes identifying and following patterns, as well as understanding the full customer impact is. At this time, the investigation is ongoing. We will provide additional updates shortly.

7. 2 июля 2026 г. в 16:36 UTCmonitoring

   Our engineers have implemented a fix that has addressed the inbound/outbound call issues that were reported, and we are now monitoring for continued stability. We will provide a final update shortly.

8. 2 июля 2026 г. в 18:27 UTCresolved

   Our engineers are now seeing that all services are functional. We will conduct an internal review of this issue and will make appropriate improvements to ensure that this issue does not reoccur.

1. 1 июля 2026 г. в 09:43 UTCinvestigating

   We are actively investigating reports that a subset of GoTo Connect customers may be experiencing issues with inbound and outbound calls. Our engineers are working to identify the issue and will provide another update shortly.

2. 1 июля 2026 г. в 10:08 UTCidentified

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

3. 1 июля 2026 г. в 10:40 UTCmonitoring

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

4. 1 июля 2026 г. в 10:43 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 1 июля 2026 г. в 10:50 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. 19 июня 2026 г. в 08:33 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. 19 июня 2026 г. в 08:38 UTCidentified

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

3. 19 июня 2026 г. в 10:08 UTCidentified

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

4. 19 июня 2026 г. в 12:39 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. 19 июня 2026 г. в 13:11 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. 28 мая 2026 г. в 14:17 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. 28 мая 2026 г. в 14:28 UTCidentified

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

3. 28 мая 2026 г. в 14:49 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. 28 мая 2026 г. в 14:57 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. 27 мая 2026 г. в 15:17 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. 27 мая 2026 г. в 15:45 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. 27 мая 2026 г. в 15:48 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. 27 мая 2026 г. в 15:57 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. 13 мая 2026 г. в 18:58 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. 13 мая 2026 г. в 19:22 UTCidentified

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

3. 13 мая 2026 г. в 20:04 UTCidentified

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

4. 13 мая 2026 г. в 21:13 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. 13 мая 2026 г. в 22:28 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. 13 мая 2026 г. в 22:40 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. 14 мая 2026 г. в 00:37 UTCidentified

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

8. 14 мая 2026 г. в 01:12 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. 14 мая 2026 г. в 02:03 UTCidentified

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

10. 14 мая 2026 г. в 02:12 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. 14 мая 2026 г. в 02:22 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. 8 мая 2026 г. в 01:22 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. 8 мая 2026 г. в 02:09 UTCinvestigating

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

3. 8 мая 2026 г. в 04:10 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. 8 мая 2026 г. в 17:11 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. 7 мая 2026 г. в 18:31 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. 8 мая 2026 г. в 01:54 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. 8 мая 2026 г. в 02:01 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. 6 мая 2026 г. в 16:55 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. 6 мая 2026 г. в 16:57 UTCidentified

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

3. 6 мая 2026 г. в 17:06 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. 6 мая 2026 г. в 17:23 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. 20 апреля 2026 г. в 14:14 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. 20 апреля 2026 г. в 14:34 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. 20 апреля 2026 г. в 14:55 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. 20 апреля 2026 г. в 15:12 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. 20 апреля 2026 г. в 15:16 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. 20 апреля 2026 г. в 15:23 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. 15 апреля 2026 г. в 21:08 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. 15 апреля 2026 г. в 21:15 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. 15 апреля 2026 г. в 21:38 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. 15 апреля 2026 г. в 21:41 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. 6 апреля 2026 г. в 12:58 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. 6 апреля 2026 г. в 13:16 UTCidentified

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

3. 6 апреля 2026 г. в 13:43 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. 6 апреля 2026 г. в 13:47 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. 25 марта 2026 г. в 16:08 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. 25 марта 2026 г. в 16:15 UTCidentified

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

3. 25 марта 2026 г. в 16:20 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. 25 марта 2026 г. в 16:35 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. 18 марта 2026 г. в 15:37 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. 18 марта 2026 г. в 15:51 UTCidentified

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

3. 18 марта 2026 г. в 15:58 UTCidentified

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

4. 18 марта 2026 г. в 16:04 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. 18 марта 2026 г. в 18:19 UTCresolved

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

1. 27 февраля 2026 г. в 15:52 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. 27 февраля 2026 г. в 17:20 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. 27 февраля 2026 г. в 18:00 UTCidentified

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

4. 27 февраля 2026 г. в 18:42 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. 27 февраля 2026 г. в 19:15 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.