GoToConnect outage history

GoTo Connect and a broad set of related GoTo/LogMeIn Resolve components entered maintenance at 1:33 AM UTC, affecting messaging (SMS and Chat), the Administration Portal, Grasshopper, and a wide range of Resolve services (Devices, Helpdesk, MDM, Remote Execution, Reporting, Support, Login, Integrations, Resolve MCP Server), plus Rescue and GoToAssist tools and related APIs. During this maintenance window, access to messaging, account management, and remote-support features could have been limited. Most services were brought back online by 5:33 AM UTC, with the remaining GoToMyPC components restored by 8:03 AM UTC.

GoToConnect faced a brief outage affecting webcam and screen sharing across GoTo Meeting, GoTo Webinar, and GoTo Training. The incident began at 3:28 PM UTC and was resolved by 3:38 PM UTC as engineers confirmed all services were functional again, though ongoing sessions should be restarted to be fully resolved.

The disruption was contained to media sharing features and cleared quickly, with status updates indicating a return to normal soon after the fix. A restart of affected sessions was advised to ensure full recovery for any in-progress meetings or trainings.

GoToConnect conducted a scheduled maintenance window affecting GoToMyPC, Pro, Central, and Hamachi (Remote Access). The maintenance began at 4:33 AM UTC and concluded by 7:33 AM UTC, during which these components were in maintenance mode and remote access could be interrupted. The GoToConnect status page documented the maintenance and later confirmed restoration to normal operation after the window closed.

GoToConnect briefly placed the GoToMyPC, Pro, Central, and Hamachi (Remote Access) components under maintenance. The maintenance window began at 7:43 AM UTC and concluded at 7:48 AM UTC, lasting about five minutes. Users relying on remote access may have experienced a short disruption during this window, with services returning to normal once the maintenance completed.

GoToConnect scheduled maintenance affected the GoToMyPC, Pro, Central, and Hamachi (Remote Access) components. The maintenance window began at 4:33 AM UTC and lasted about three hours, ending with the services returning to normal at 7:33 AM UTC. During the window, access to the GoToMyPC and related remote-access components may have been degraded or unavailable. Status updates confirmed the scope and that services were fully restored after the window.

Inbound PSTN calls to GoTo Connect were unavailable for receiving during the incident, while outbound calls and internal extensions remained functional. The issue began around 12:58 PM UTC and persisted for about three and a half hours until it was resolved by 4:28 PM UTC. GoTo Connect engineers coordinated with PSTN peers to identify the cause and work toward a fix, with the issue being identified around 1:33 PM UTC and a corrective action in place by 1:48 PM UTC as monitoring continued. A user reported inbound calls were not working around 4:06 PM UTC while the service was being restored.

GoToConnect services briefly underwent maintenance affecting multiple components across the GoTo suite, including the GoTo Connect Administration Portal, Rescue and GoToAssist remote support, GoToMyPC (Pro, Central, and Hamachi), and related Purchase & Subscription operations. Users may have experienced intermittent access to administration, remote support, and remote access tools during the window. The maintenance began at 7:08 AM UTC and completed by 7:13 AM UTC, with services returning to normal shortly after. Status updates indicated a planned maintenance event.

GoToConnect initiated a maintenance window at 5:03 AM UTC, affecting a broad set of components including the GoTo Connect Administration Portal, LogMeIn Resolve / Reporting, Rescue and GoToAssist services (Rescue, Rescue Live Control, Rescue Live Guide, Rescue Live Lens), and remote access offerings (GoToMyPC, Pro, Central, Hamachi), as well as Purchase & Subscription Operations (New purchases, Self Serve, Trial initiation, Subscription Management).

During the window, users could have experienced outages or degraded access across these services. The maintenance completed and services returned to normal by 7:03 AM UTC. The window lasted about two hours.

GoToConnect experienced a brief outage beginning at 3:48 PM UTC with elevated error rates affecting Pro, Central, and LogMeIn Rescue customers. Remote support session launches were slow or failing, and new host installations for Pro and Central could be impacted. Affected components included Rescue and GoToAssist (Remote Support) and GoToMyPC, Pro, Central, and Hamachi (Remote Access). Engineers investigated and implemented a fix, with services restored by 4:18 PM UTC after about 30 minutes, and monitoring continued to ensure stability.

A broad outage affected the GoToConnect family, with connectivity issues impacting a wide range of services. Core GoTo Connect tools including Chat, SMS, and the Administration Portal were degraded, along with the Contact Center and Customer Engagement products. The disruption extended to collaboration and meeting tools such as GoTo Meeting, GoTo Webinar, and GoTo Training, and even reached Rescue/GoToAssist components, various APIs, and PSTN inbound calls. Users reported trouble placing or receiving calls, failing connections to meetings, and messaging errors. Impact began at 4:58 PM UTC and progressed to gradual recovery as services came back online.