GoToConnect outage history

GoToConnect conducted a scheduled maintenance window affecting GoToMyPC, Pro, Central, and Hamachi (Remote Access) components. The maintenance began at 5:33 AM UTC and was completed by 8:03 AM UTC, with full service restoration occurring about two and a half hours later. During the window, the affected GoToMyPC family services were placed into maintenance mode, which could have caused temporary accessibility limitations for remote access features.

GoToConnect conducted a brief maintenance window affecting the LogMeIn Resolve (Remote Support) / Integrations component. The maintenance began at 6:03 AM UTC and concluded at 7:03 AM UTC, after which the component returned to normal operation.

GoToConnect's Grasshopper component experienced an outage that blocked password resets and OTP emails for Microsoft365 and Outlook users. The incident began at 3:03 PM UTC and GoToConnect engineers identified this as a vendor issue and engaged the vendor for resolution.

By 3:58 PM UTC, there were signs of recovery as internal mitigations took effect and retries started succeeding, allowing password and authentication traffic to flow again. The Grasshopper component returned to normal operations by 4:33 PM UTC.

The outage began on Aug 4, 2026 6:13 PM UTC affecting GoTo Customer Engagement's WhatsApp campaigns. Users could not send campaigns or initiate outbound conversations, and onboarding new WhatsApp numbers was disabled, while SMS campaigns remained functional. An in-app notification indicated the limitation as teams worked with Meta to resolve the issue. A sample user report from Salem, Virginia described network issues during the early phase.

GoToConnect conducted a scheduled maintenance window affecting Rescue and GoToAssist (Remote Support) and GoToMyPC, Pro, Central, and Hamachi (Remote Access) / Pro/Central. The maintenance began at 4:03 AM UTC and concluded by 10:03 AM UTC, during which those components were briefly unavailable or degraded. Normal service resumed by 10:03 AM UTC for the affected services.

GoToConnect initiated a scheduled maintenance window affecting GoToMyPC, GoToPro, GoToCentral, and Hamachi (Remote Access). The maintenance began at 5:33 AM UTC and concluded at 8:03 AM UTC, lasting about two and a half hours. Users may have experienced limited access to remote desktop and related services during this period while backend updates were applied.

GoToConnect underwent a scheduled maintenance window affecting Rescue and GoToAssist (Remote Support) and the GoTo Assist Service Desk. The maintenance began at 4:33 AM UTC and was completed by 7:33 AM UTC, with services briefly unavailable during that period. The GoToConnect status page indicated the affected components were placed into maintenance and then returned to normal once the window ended, roughly three hours later.

GoToConnect's Grasshopper component entered a scheduled maintenance window at 8:03 AM UTC and returned to normal operation at 9:03 AM UTC. The Grasshopper component was the focus of the maintenance, and there were no broader service issues reported. No user reports were logged during the window, indicating minimal impact for customers.

The maintenance was resolved after about an hour, with the Grasshopper component coming back to up status on the GoToConnect status page.

GoToConnect entered a maintenance window affecting Rescue and GoToAssist (Remote Support) / GoTo Assist Service Desk. The maintenance began at 4:33 AM UTC and concluded at 7:33 AM UTC, lasting about three hours. During this period, the affected remote support features were temporarily unavailable while components transitioned in and out of maintenance. The maintenance has completed and GoToConnect services for Rescue and GoToAssist are back to normal.

Users attempting to sign in to GoToConnect faced a widespread login outage beginning at 12:08 PM UTC. The issue affected Pro and Central first, with GoToMeeting, GoToWebinar, join.me, GoToMyPC, Pro, Central, and Hamachi (Remote Access) experiencing sign-in problems and intermittent access for several hours. The outage disrupted access to core collaboration and remote-access tools for a broad set of GoTo products, impacting teams trying to connect to meetings or remote sessions.