GoTo

Affected: Pro/Central

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-10 04:56 UTC

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

2. identified 2026-10-10 05:22 UTC

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

3. monitoring 2026-10-10 05:56 UTC

   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. resolved 2026-10-10 06:20 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Meeting, GoTo Webinar, GoTo Training

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 15:03 UTC

   We are actively investigating reports that some GoTo Meeting, Webinar or Training customers may be experiencing intermittent issues with webcam or screen share. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2026-09-29 15:13 UTC

   Our engineers have identified the issue and are now actively working towards a resolution. In the meantime, customers can close and restart their session. We will provide another update when available.

3. monitoring 2026-09-29 15:23 UTC

   Our engineers have corrected the issue and we are confirming that all services are functional. However, ongoing affected sessions should be restarted to be fully resolved. We will continue monitoring the situation and provide a final update shortly.

4. resolved 2026-09-29 15:35 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: PSTN Calls - Inbound

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 12:53 UTC

   We are actively investigating reports that some GoTo Connect customers may be experiencing receiving inbound calls. Outbound calls and internal extensions calls are not affected. Our engineers are working with our PSTN peers to identify the issue and will provide another update...

2. identified 2026-09-23 13:31 UTC

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

3. monitoring 2026-09-23 13:43 UTC

   Our engineers have corrected the issue and we are monitoring the successful establishment of incoming calls. We will continue monitoring the situation and provide a final update shortly.

4. resolved 2026-09-23 16:26 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Rescue, Pro/Central

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-09 15:46 UTC

   We are actively investigating reports that some DOIS - Run, Pro, Central, and LogMeIn Rescue customers may be experiencing slow or failed session launches for remote support, as well as new host installation for Pro and Central. Our engineers are working to identify the issue...

2. identified 2026-09-09 15:50 UTC

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

3. monitoring 2026-09-09 15:56 UTC

   Our engineers have corrected the issue and we are monitoring improvements with the affected product features. We will continue monitoring the situation and provide a final update shortly.

4. resolved 2026-09-09 16:14 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Contact Center, GoTo Meeting, Rescue, Customer Engagement, VoIP Calls - GoTo Connect Web, GoTo Webinar, GoTo Meeting API, GoTo Assist Remote Support v5, VoIP Calls - GoTo Connect Mobile, GoTo Training, GoTo Assist Remote support v4, GoTo Training API, PSTN Calls - Inbound, GoTo Webinar API, GoTo Assist Corporate, GoTo Connect API, Messaging - SMS, Messaging - Chat, Administration Portal, Admin API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 16:55 UTC

   We are currently investigating connectivity issues to a variety of GoTo products. A more detailed message will be sent shortly.

2. identified 2026-09-08 17:16 UTC

   We have identified the issue our team is all hands on deck to restore service.

3. monitoring 2026-09-08 17:24 UTC

   We are seeing improvements to connectivity and are monitoring gradual recovery of services.

4. resolved 2026-09-08 17:48 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Meeting, Rescue, Pro/Central, GoTo Webinar, Helpdesk, GoToMyPC, GoTo Training, GoTo Assist Service Desk, GoTo Assist Corporate

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-04 12:31 UTC

   We are actively investigating reports that some customers may be experiencing issues in receiving emails from GoTo, notably including 2FA confirmations for Resolve, Rescue and GoToMyPC. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2026-09-04 12:47 UTC

   Our engineers have identified the email delivery rate is improving and are continuously working towards a resolution with our mail delivery partner. We will provide another update shortly.

3. monitoring 2026-09-04 12:59 UTC

   Our partner has corrected the issue and we are seeing sustained stability in email services. We will continue monitoring the situation and provide a final update shortly.

4. resolved 2026-09-04 13:31 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Rescue, Pro/Central

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-27 15:55 UTC

   Our engineers are investigating issues with code signing for Rescue, GoToAssist v5, Pro and Central, which can lead to intermittent failures when starting sessions. We will provide another update shortly.

2. identified 2026-08-27 16:38 UTC

   Our engineers continue to investigate the code signing issues reported for Rescue, GoTo Assist v5, Pro, and Central. We will provide another update shortly.

3. monitoring 2026-08-27 17:40 UTC

   Our engineers are seeing an improvement on the situation and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. resolved 2026-08-28 16:24 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Grasshopper

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-15 15:02 UTC

   Our engineers are aware of an issue affecting password reset and OTP emails impacting Microsoft365 and Outlook users. We have identified the issue as a vendor issue, and we have engaged with them to work toward resolution. We will provide another update shortly.

2. monitoring 2026-08-15 15:52 UTC

   Our engineers are beginning to see signs of recovery following an internal mitigation as they continue to engage the vendor for final resolution. We are seeing that retries are successful, such that affected users have been able to receive password and authentication traffic. We...

3. resolved 2026-08-15 16:33 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Customer Engagement

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-04 18:11 UTC

   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...

2. identified 2026-08-07 19:44 UTC

   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. identified 2026-08-13 17:48 UTC

   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...

4. monitoring 2026-08-14 15:11 UTC

   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. resolved 2026-08-14 16:09 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Pro/Central, GoToMyPC, join.me

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-03 12:03 UTC

   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. investigating 2026-07-03 12:39 UTC

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

3. identified 2026-07-03 13:23 UTC

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

4. identified 2026-07-03 14:05 UTC

   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...

5. identified 2026-07-03 15:08 UTC

   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...

6. identified 2026-07-03 16:02 UTC

   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. identified 2026-07-03 18:21 UTC

   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. identified 2026-07-03 19:21 UTC

   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. monitoring 2026-07-03 19:55 UTC

   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. resolved 2026-07-03 20:25 UTC

    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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - GoTo Connect Web

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-02 11:49 UTC

   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. identified 2026-07-02 11:54 UTC

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

3. identified 2026-07-02 13:43 UTC

   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. identified 2026-07-02 14:12 UTC

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

5. identified 2026-07-02 15:14 UTC

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

6. identified 2026-07-02 16:06 UTC

   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...

7. monitoring 2026-07-02 16:36 UTC

   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. resolved 2026-07-02 18:27 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - GoTo Connect Web

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-01 09:43 UTC

   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. identified 2026-07-01 10:08 UTC

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

3. monitoring 2026-07-01 10:40 UTC

   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. monitoring 2026-07-01 10:43 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-07-01 10:50 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Contact Center

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-19 08:33 UTC

   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. identified 2026-06-19 08:38 UTC

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

3. identified 2026-06-19 10:08 UTC

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

4. monitoring 2026-06-19 12:39 UTC

   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. resolved 2026-06-19 13:11 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, Administration Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-28 14:17 UTC

   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. identified 2026-05-28 14:28 UTC

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

3. monitoring 2026-05-28 14:49 UTC

   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. resolved 2026-05-28 14:57 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Rescue, Pro/Central

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-27 15:17 UTC

   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. identified 2026-05-27 15:45 UTC

   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. monitoring 2026-05-27 15:48 UTC

   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. resolved 2026-05-27 15:57 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Rescue, Pro/Central

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-13 18:58 UTC

   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. identified 2026-05-13 19:22 UTC

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

3. identified 2026-05-13 20:04 UTC

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

4. identified 2026-05-13 21:13 UTC

   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. monitoring 2026-05-13 22:28 UTC

   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. identified 2026-05-13 22:40 UTC

   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. identified 2026-05-14 00:37 UTC

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

8. identified 2026-05-14 01:12 UTC

   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. identified 2026-05-14 02:03 UTC

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

10. monitoring 2026-05-14 02:12 UTC

    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. resolved 2026-05-14 02:22 UTC

    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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Grasshopper

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-08 01:22 UTC

   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. investigating 2026-05-08 02:09 UTC

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

3. monitoring 2026-05-08 04:10 UTC

   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. resolved 2026-05-08 17:11 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Connect API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-07 18:31 UTC

   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. monitoring 2026-05-08 01:54 UTC

   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. resolved 2026-05-08 02:01 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - GoTo Connect Web

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 16:55 UTC

   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. identified 2026-05-06 16:57 UTC

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

3. monitoring 2026-05-06 17:06 UTC

   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. resolved 2026-05-06 17:23 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Meeting, VoIP Calls - GoTo Connect Web, GoTo Webinar, Helpdesk, GoTo Meeting API, VoIP Calls - GoTo Connect Mobile, GoTo Training, GoTo Connect API, Messaging - SMS, Messaging - Chat, Administration Portal, Admin API, Authentication API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 14:14 UTC

   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. identified 2026-04-20 14:34 UTC

   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...

3. identified 2026-04-20 14:55 UTC

   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. identified 2026-04-20 15:12 UTC

   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. monitoring 2026-04-20 15:16 UTC

   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. resolved 2026-04-20 15:23 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: PSTN Calls - Inbound

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-15 21:08 UTC

   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. identified 2026-04-15 21:15 UTC

   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. monitoring 2026-04-15 21:38 UTC

   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. resolved 2026-04-15 21:41 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-06 12:58 UTC

   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. identified 2026-04-06 13:16 UTC

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

3. monitoring 2026-04-06 13:43 UTC

   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. resolved 2026-04-06 13:47 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - Deskphones, VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, PSTN Calls - Inbound, PSTN Calls - Outbound

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 16:08 UTC

   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. identified 2026-03-25 16:15 UTC

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

3. monitoring 2026-03-25 16:20 UTC

   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. resolved 2026-03-25 16:35 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Meeting, GoTo Webinar, GoTo Training

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-18 15:37 UTC

   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. identified 2026-03-18 15:51 UTC

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

3. identified 2026-03-18 15:58 UTC

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

4. monitoring 2026-03-18 16:04 UTC

   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. resolved 2026-03-18 18:19 UTC

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

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Contact Center

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-27 15:52 UTC

   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. investigating 2026-02-27 17:20 UTC

   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. identified 2026-02-27 18:00 UTC

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

4. monitoring 2026-02-27 18:42 UTC

   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. resolved 2026-02-27 19:15 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-02-27 10:30 UTC

   During the period from 08:04 to 9:10 UTC on February 27, a subset of GoTo Connect customers in Europe may have experienced issues receiving inbound PSTN calls. We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an...

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Administration Portal

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-27 00:53 UTC

   Engineers have identified an issue with being able to make/commit changes in GoTo Admin. We believe the issue to be linked to a connectivity issue between several of our data centers. We are currently working through this and will provide further details as more information...

2. monitoring 2026-01-27 01:31 UTC

   Our engineers have begun seeing signs of recovery and are continuing to monitor for continued stability. We will continue monitoring the situation and provide a final update shortly.

3. resolved 2026-01-27 01:40 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Grasshopper, Pro/Central, Administration Portal

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-01-22 22:10 UTC

   We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will...

2. identified 2026-01-22 22:19 UTC

   We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will...

3. identified 2026-01-22 22:19 UTC

   We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will...

4. identified 2026-01-22 22:21 UTC

   We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will...

5. identified 2026-01-23 04:12 UTC

   Microsoft is continuing to address the ongoing Microsoft 365 service incident. Microsoft reports improvements in availability, but recovery efforts are still in progress, and some users may continue to experience intermittent impact. For the latest updates, please refer to...

6. monitoring 2026-01-23 13:22 UTC

   Microsoft is confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

7. resolved 2026-01-23 22:13 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Pro/Central, Administration Portal

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-01-21 19:47 UTC

   Our engineers have identified an issue impacting the delivery of emails and are now actively working towards a resolution. This notably impacts emails sent from GoTo Admin (such as new user welcome emails), MFA emails from GoTo Assist, Pro and Central and password reset emails....

2. identified 2026-01-21 20:01 UTC

   Specifically for GoTO Assist Service Desk, this impacts all email-based processes, including incident creation/update notifications, "email me" reports, and customer invitations. We will provide another update shortly.

3. monitoring 2026-01-21 20:03 UTC

   Our engineers are confirming that all services are restored and emails are being delivered. There may be a small delay while the system processes the backlog of accumulated emails. We will continue monitoring the situation and will provide a final update shortly.

4. resolved 2026-01-21 20:09 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - Deskphones, VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, PSTN Calls - Inbound, PSTN Calls - Outbound

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-18 18:04 UTC

   We are aware that a subset of customers may be experiencing inbound/outbound call failure, as well as calls competing with no audio. Our engineers are investigating this, and we will provide further updates as more information becomes available Our engineers are working to...

2. identified 2026-01-18 18:12 UTC

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

3. monitoring 2026-01-18 18:26 UTC

   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. resolved 2026-01-18 18:41 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-18 19:29 UTC

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

2. identified 2025-12-18 19:33 UTC

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

3. identified 2025-12-18 19:41 UTC

   Users experiencing this issue should reload their GoTo Connect softphone, to benefit from a change preformed by our engineering teams. We will provide another update shortly.

4. monitoring 2025-12-18 19:42 UTC

   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. resolved 2025-12-18 20:15 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Training

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-11-26 08:37 UTC

   On 26th November 2025, between 06:51 UTC and 07:03 UTC, a subset of GoTo App users using GoTo Training may have experienced issues with joining or scheduling training sessions due to a small change in the infrastructure. Immediately the issue was identified, we reverted the...

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Pro/Central, Miradore, MDM, Remote Execution, join.me

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Azure Front Door – Connectivity issues across multiple regions.

1. investigating 2025-10-29 16:16 UTC

   We are actively investigating reports that some LogMeIn Resolve customers may be experiencing issues accessing the application. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-10-29 16:31 UTC

   Our engineers have identified the issue coming from an upstream cloud provider and are now actively working towards a resolution. We will provide another update shortly.

3. identified 2025-10-29 17:01 UTC

   We are currently seeing impacts on the following features across the LogMeIn portfolio: - Resolve ZeroTrust features - Access to Pro/Central - GoToMyPC Web Access We will provide another update shortly as our engineering teams are working on mitigation actions.

4. identified 2025-10-29 17:05 UTC

   For Pro/Central, the following actions can be taken as a workaround to access Remote Control. - Click on Computer Properties > At "Status" field Click Connect to this Computer link - Click on Computer Properties > Select "Desktop Shortcut" tab > Follow the instructions in the...

5. identified 2025-10-29 17:20 UTC

   Our engineers have identified that join.me is also affected by this issue.

6. identified 2025-10-29 17:37 UTC

   Our engineers continue to monitor the situation and explore potential workarounds for this issue.

7. identified 2025-10-29 17:49 UTC

   We are continuing to monitor the behavior of all LogMeIn products. Microsoft Azure is currently experiencing an incident which is at the source of these issues. We will be updating this status page in the next 30 minutes or earlier if the situation progresses.

8. monitoring 2025-10-29 18:07 UTC

   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.

9. identified 2025-10-29 18:13 UTC

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

10. identified 2025-10-29 18:19 UTC

    Our engineers have implemented workarounds for some LogMeIn Resolve and were able to restore the Login, Helpdesk and Reporting functions.

11. identified 2025-10-29 18:33 UTC

    We are continuing to monitor the situation with the Azure incident and applying workarounds where possible.

12. identified 2025-10-29 19:54 UTC

    Our engineers are still monitoring for any improvements the product availability in the light of mitigation actions performed by Microsoft Azure. We will provide another update in 1 hour or earlier if the situation improves.

13. monitoring 2025-10-29 21:18 UTC

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

14. resolved 2025-10-29 21:44 UTC

    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 the impact on future recurrence.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoToMyPC

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-26 10:35 UTC

   We are actively investigating reports that some GoToMyPC customers may be experiencing issues in accessing application. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-10-26 10:48 UTC

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

3. monitoring 2025-10-26 10:50 UTC

   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. resolved 2025-10-26 10:56 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: PSTN Calls - Outbound

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-21 15:51 UTC

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

2. identified 2025-10-21 16:23 UTC

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

3. monitoring 2025-10-21 16:27 UTC

   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. resolved 2025-10-21 16:52 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Meeting, Devices, GoTo Webinar, Helpdesk, GoToMyPC, GoTo Training, MDM, PSTN Calls - Inbound, Remote Execution, PSTN Calls - Outbound, Reporting, Support, Login

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 08:16 UTC

   We are actively investigating reports that GoTo Meeting, GoTo Webinar, GoTo Training , GoToMyPC (Web Experience), & GoTo Resolve customers may be experiencing issues while accessing the application. Our engineers are working to resolve the issue and will provide another update...

2. identified 2025-10-20 08:34 UTC

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

3. monitoring 2025-10-20 09:37 UTC

   We are continuing to closely monitor the outage at our third-party cloud service provider, which has impacted the functionality of our products. Our call center is also affected, and as a result, customers may experience difficulties reaching our support team. Our engineers are...

4. monitoring 2025-10-20 10:29 UTC

   All of the affected GoTo products have recovered and normal operation is expected. Due to the extent of the incident in our third-party cloud provider, there might be some isolated latency in asynchronous tasks, but these are expected to catch up shortly. Our engineering teams...

5. monitoring 2025-10-20 14:59 UTC

   We are continuing to monitor the behavior of all the GoTo products. At this time, AWS reported a new period of instability, which might have some temporary side-effects in functionalities of GoTo products as the situation progresses. This incident also affects the ability for...

6. monitoring 2025-10-20 17:29 UTC

   We are continuing to monitor the behavior of all GoTo products. AWS is currently experiencing ongoing instability which may cause temporary side-effects in functionalities of GoTo products as the situation progresses. At this moment, our Customer Support phone system is...

7. monitoring 2025-10-20 18:19 UTC

   We are continuing to monitor the behavior of all GoTo products. AWS is currently experiencing ongoing instability which may cause temporary side-effects in functionalities of GoTo products as the situation progresses. We are seeing signs of recovery and stability and will...

8. monitoring 2025-10-20 20:27 UTC

   We are continuing to monitor the behavior of all GoTo products and expect to be fully operational soon. Services are stabilizing and we are seeing positive progress across our platform.

9. resolved 2025-10-20 22:10 UTC

   All GoTo products are now fully operational. We have confirmed that services have returned to normal performance levels. We appreciate your patience during this incident. We will conduct an internal review of this issue and make appropriate improvements to our system to help...

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Webinar, GoTo Assist Remote support v4

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-08 06:53 UTC

   We continue to investigate reports from some GoTo Assist Remote Support customers regarding intermittent slowness, occasional empty unattended device lists on the web and issues with session recordings created in the past 48 hours. Our engineering team continues to work towards...

2. identified 2025-10-08 08:09 UTC

   We are continuing to investigate this issue. At this time, some GoTo Webinar customers may be experiencing audio quality issues during their sessions. Our engineering team is actively working to identify the cause and implement a solution. We will provide another update as soon...

3. identified 2025-10-08 08:12 UTC

   We are continuing to investigate this issue. At this time, some GoTo Webinar customers may be experiencing audio issues. Our engineers are working to identify the issue and will provide another update shortly.

4. identified 2025-10-08 10:26 UTC

   Our engineers have corrected the audio quality issues for GoTo Webinar and continue to investigate issues with G2ARS. We will continue to monitor the situation and will provide another update shortly.

5. monitoring 2025-10-08 16:56 UTC

   A fix for missing recordings in GoTo Assist has been deployed and are monitoring for its stability.

6. resolved 2025-10-08 17:32 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Contact Center, GoTo Meeting, Pro/Central, VoIP Calls - GoTo Connect Web, GoTo Webinar, GoTo Training, GoTo Assist Remote support v4, OpenVoice, Messaging - SMS, Administration Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-06 08:40 UTC

   We are actively investigating reports that some GoTo Connect Contact Centre, GoTo Meeting, GoTo Webinar, GoTo Training and Openvoice customers may be experiencing Issues while using their application. Our engineers are working to identify the issue and will provide another...

2. investigating 2025-10-06 08:51 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-06 10:07 UTC

   We are actively investigating reports that some GoTo Connect Contact Centre, GoTo Meeting, GoTo Webinar, GoTo Training & Openvoice and GoToAssist (Remote Support) customers may be experiencing Issues while using their application. Our engineers are working to identify the issue...

4. investigating 2025-10-06 11:06 UTC

   Our engineers believe they have identified the issue, and we have confirmed that the issue has been resolved completely and all systems are 100% operational at this time, for GoTo Meeting, GoTo Webinar, GoTo Training and OpenVoice. We are still continuing to investigate this...

5. identified 2025-10-06 11:50 UTC

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

6. monitoring 2025-10-06 11:53 UTC

   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.

7. identified 2025-10-06 13:09 UTC

   The mitigation is still ongoing for some services. We will provide another update shortly.

8. identified 2025-10-06 14:16 UTC

   Our engineering team is continuing to perform actions towards platform stability and are investigating on issues which may prevent the GoTo Connect softphone from loading properly.

9. identified 2025-10-06 15:13 UTC

   We are seeing improvement with regards to sporadic errors when launching the GoTo App softphone and are monitoring for stability. Our engineering team is continuing to perform actions towards platform stability and another update will be shared soon.

10. identified 2025-10-06 16:20 UTC

    Our engineers are actively working towards a resolution for the remaining affected functionalities. We will provide another update shortly.

11. identified 2025-10-06 17:30 UTC

    Our engineering team is seeing improvements in internal metrics. There are isolated issues with login to call queues as well as the call history in the GoTo app and are focused to resolve these lingering issues. We will provide a new update shortly.

12. identified 2025-10-06 18:39 UTC

    Our engineers are still actively working towards a resolution for the remaining affected functionalities. Another update will be shared soon.

13. identified 2025-10-06 19:39 UTC

    Our engineers are continuing to work towards a resolution for the remaining affected functionalities. There remains some isolated issues on Contact Center Agent login and logout as well as delays in voicemail function and notifications. Another update will be shared soon.

14. identified 2025-10-06 20:16 UTC

    Our engineers are continuing to work towards a resolution for the remaining affected functionalities.

15. monitoring 2025-10-06 23:28 UTC

    We have been seeing signs of recovery, and we will continue to monitor the platform for stability. We will provide a final update shortly.

16. identified 2025-10-07 12:27 UTC

    Our engineers have identified an issue for GoTo Meeting, GoTo Webinar and GoTo Training. Another update will be shared soon.

17. identified 2025-10-07 14:28 UTC

    Our engineering teams remain fully engaged in monitoring this issue and providing stability on the GoTo platform. Current issues include degraded performance for Contact Center Analytics, isolated audio issues for GoTo Meeting, GoTo Webinar and GoTo Training as well as...

18. identified 2025-10-07 15:54 UTC

    We are seeing improvements for GoTo Webinars after our engineers implemented a fix. Some intermittent issues remain for GoTo Meeting and Training for joining sessions. For GoTo Connect, we have corrected an issue related to loading contacts in the application. There remains...

19. monitoring 2025-10-07 19:02 UTC

    We are seeing improvement in all products metrics and we will continue to monitor the platform for stability.

20. resolved 2025-10-07 20:44 UTC

    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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoTo Connect API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-25 18:25 UTC

   Our engineers have identified an issue where Call Event Reports API may have stopped receiving notification for queue calls in their channel since September 16. The underlying cause has been identified, and they are actively working toward resolution We will provide another...

2. monitoring 2025-09-25 20:13 UTC

   Our engineers have implemented a fix and are seeing a correction in notification traffic. Our engineers are now monitoring for stability. We will continue monitoring the situation and provide a final update shortly.

3. resolved 2025-09-25 20:25 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-09-22 14:00 UTC

   On September 22nd, from 14:15 UTC until 15:40 UTC, a subset of GoTo Connect customers may have experienced issues completing inbound and outbound PSTN calls in Brazil due to a network incident impacting a third-party service provider. Immediately after the root cause of the...

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Contact Center

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-18 17:59 UTC

   We are actively investigating reports that some Contact Center – Call Queues and Contact Center – Supervisor customers may be experiencing issues to login and out of the call queues. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-09-18 18:01 UTC

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

3. monitoring 2025-09-18 18:03 UTC

   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. resolved 2025-09-18 18:18 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - Deskphones, VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, Messaging - Chat, Administration Portal

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-17 19:03 UTC

   We are actively investigating reports that some GoTo Connect customers may be experiencing issues, notably with messaging, some incoming call notifications. as well as loading GoTo Admin. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-09-17 19:21 UTC

   Our engineers have identified the issue and are now actively working towards a resolution. Due to the nature of the issue, the effects can be varied, but include access to GoToAdmin, issues sending or receiving SMS. We will provide another update shortly.

3. identified 2025-09-17 19:47 UTC

   Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update shortly.

4. monitoring 2025-09-17 19:49 UTC

   Our engineers have corrected the issue and we monitoring the gradual recovery of the affected services. We will continue monitoring the situation and provide another update shortly.

5. identified 2025-09-17 21:31 UTC

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

6. identified 2025-09-17 22:24 UTC

   Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update shortly.

7. identified 2025-09-18 00:46 UTC

   Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update shortly.

8. identified 2025-09-18 04:25 UTC

   Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update as soon as it becomes available.

9. monitoring 2025-09-18 12:54 UTC

   Our engineers have corrected the issue which arose as a side-effect of mitigating the initial problem. The main impact was an error message when starting the GoTo App, on Desktop, Web or Mobile. Recovery is going to be transparent for these clients and, specifically for the...

10. resolved 2025-09-18 18:49 UTC

    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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: PSTN Calls - Outbound

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-25 03:38 UTC

   We are actively investigating reports that some GoTo Connect VoIP Phones Calls and GoTo Connect customers from the APAC region may be experiencing issues while making outbound calls Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-08-25 04:28 UTC

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

3. monitoring 2025-08-25 04:30 UTC

   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. resolved 2025-08-25 04:36 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Grasshopper

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-20 18:19 UTC

   We are actively investigating reports that some Grasshopper customers may be experiencing loading the Grasshopper web portal and making outbound calls with the Grasshopper app. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-08-20 18:33 UTC

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

3. monitoring 2025-08-20 19:06 UTC

   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. resolved 2025-08-20 19:33 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: PSTN Calls - Inbound

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-20 17:58 UTC

   We are actively investigating reports that some GoTo Connect customers might be experiencing incoming call issues in Brazil. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-08-20 18:03 UTC

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

3. monitoring 2025-08-20 18:13 UTC

   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. resolved 2025-08-20 18:21 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-31 14:54 UTC

   We are aware of reports where a subset of GoTo Connect users have been unable to place/receive calls on GoTo App and GoTo Web. Our engineers are investigating the issue, and we will provide an update as more details become available. Our engineers are working to identify the...

2. identified 2025-07-31 15:00 UTC

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

3. monitoring 2025-07-31 15:03 UTC

   Our engineers have corrected the issue and we are receiving reports that calling is working as expected. We will continue monitoring the situation and provide a final update shortly.

4. resolved 2025-07-31 15:10 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: GoToMyPC

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-30 14:04 UTC

   We are actively investigating reports that some GoToMyPC customers may be experiencing issue with GoToMyPC Mycomputer Page. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-07-30 14:30 UTC

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

3. monitoring 2025-07-30 15:35 UTC

   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. resolved 2025-07-30 16:07 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: VoIP Calls - Deskphones, VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, PSTN Calls - Inbound

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-24 01:39 UTC

   We are actively investigating reports that some GoTo Connect customers may be experiencing multiple notifications when receiving inbound calls in the GoTo Connect app. Investigation so far shows that the issue is limited to the APAC region. Our engineers are working to identify...

2. identified 2025-07-24 02:05 UTC

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

3. identified 2025-07-24 03:00 UTC

   Our engineers keep working with the PSTN peer toward a resolution. We will provide another update shortly.

4. identified 2025-07-24 04:16 UTC

   Our engineers keep working with the PSTN peer toward a resolution. We will provide another update shortly.

5. monitoring 2025-07-24 04:28 UTC

   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. resolved 2025-07-24 05:10 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: Pro/Central, Hamachi

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-09 05:30 UTC

   We are actively investigating reports that some Pro and Central customers may be experiencing a "D error" while logging in to their accounts.

2. identified 2025-07-09 05:34 UTC

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

3. monitoring 2025-07-09 05:42 UTC

   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. resolved 2025-07-09 05:53 UTC

   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.

Excerpts are shortened. Read the full incident on GoTo's status page.

Affected: PSTN Calls - Inbound, PSTN Calls - Outbound

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-05-16 17:07 UTC

   We are actively investigating reports that some GoTo Connect VoIP phone customers may be experiencing call connection issues in Brazil. Our engineers are working to identify the issue and will provide another update shortly.

2. identified 2025-05-16 17:14 UTC

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

3. identified 2025-05-16 17:17 UTC

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

4. identified 2025-05-16 18:50 UTC

   Our engineers are still engaged with the impacted PSTN peer, while working to put workarounds in place to mitigate customer impact. We will provide another update shortly.

5. identified 2025-05-16 21:54 UTC

   Our engineers have already implemented mitigation and workaround measures to help minimize the impact. However, we remain dependent on our PSTN peer to fully resolve the issue. We are monitoring the situation closely and will provide updates as new information becomes available.

6. resolved 2025-05-17 15:13 UTC

   We have confirmed with the affected PSTN peer 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.

Excerpts are shortened. Read the full incident on GoTo's status page.