GoToConnect Outage History

A scheduled maintenance window affected GoToMyPC and related services including Pro, Central, and Hamachi (Remote Access). Access to these remote-access tools may have been disrupted during the window. The maintenance began at Mar 13, 2025 5:33 AM UTC and ended at Mar 13, 2025 8:03 AM UTC, lasting about 2 hours and 30 minutes. GoToConnect issued 2 official updates during the incident and restored all affected components to normal operation by the end of the window.

GoTo Connect experienced a brief outage affecting voice services in Brazil. Inbound and outbound PSTN calls and GoTo Connect VoIP across Mobile, Deskphones, and Web were impacted, spanning five components in total. The outage began at 8:38 PM UTC and was resolved by 8:53 PM UTC, lasting about 15 minutes. The GoTo Connect status page indicated the issue was under investigation as engineers worked to identify the root cause, with updates issued during the incident.

The provider issued two status updates, and all affected components returned to normal after the incident. The impact was localized to Brazil, with no broader regional effects reported once services were restored.

GoToConnect scheduled maintenance affected GoToMyPC, Pro, Central, and Hamachi (Remote Access). The maintenance ran from 5:33 AM UTC to 8:03 AM UTC, lasting about 2 hours 30 minutes. During this period, access to GoToMyPC and related remote access components could have been limited or unavailable. The provider posted status updates during the incident, totaling 2 updates: one at the start announcing maintenance and another upon completion. The maintenance window ended and services returned to normal at 8:03 AM UTC.

GoToMeeting, GoTo Webinar, GoTo Training, and GoTo Assist customers experienced issues starting sessions, preventing some users from launching meetings or remote support sessions. The incident affected multiple GoTo products, with users reporting difficulties initiating sessions across several components. The outage began on 3:48 PM UTC and was resolved by 7:03 PM UTC, lasting about 3 hours 15 minutes. The provider issued 2 status updates during the incident as engineers investigated and then confirmed restoration of service. Affected components included six areas: GoTo Meeting, GoTo Webinar, and GoTo Training; GoTo Assist Remote Support v4; GoTo Assist Service Desk; and GoTo Assist Corporate.

A scheduled maintenance window affected GoToConnect components GoToMyPC, Pro, Central, and Hamachi (Remote Access), as well as LogMeIn Resolve Helpdesk and Reporting. Maintenance ran from approximately 5:30 AM UTC to 8:03 AM UTC, during which services were intermittently unavailable or degraded. The provider posted 3 status updates at Feb 5, 2025 5:33 AM UTC, Feb 5, 2025 6:03 AM UTC, and Feb 5, 2025 8:03 AM UTC; all components returned to normal by 8:03 AM UTC. The impact was limited to the maintenance window with no broader outages.

GoToConnect conducted a scheduled maintenance window affecting the LogMeIn Resolve components used for Remote Support: Helpdesk and Reporting. The maintenance started at Feb 2, 2025 5:03 PM UTC and concluded at Feb 2, 2025 8:03 PM UTC, lasting approximately 3 hours.

During the window, the status page published two updates documenting the maintenance, with the affected components transitioning to maintenance and then returning to up once work was completed. After the maintenance, both components were reported as up again.

GoToConnect experienced a brief partial outage affecting Central and Pro purchasing and trial workflows within the product. Some customers attempting to purchase or start a trial may have encountered issues, though purchases or trials remained possible via logmein.com. The outage began at 10:48 AM UTC and was resolved by 1:03 PM UTC, lasting roughly 2 hours and 15 minutes. The provider issued two status updates during the incident, starting with an investigation and followed by restoration of the affected services.

GoToConnect conducted a planned maintenance window affecting Rescue and GoToAssist (Remote Support) with the following components: GoTo Assist Remote Support v5, GoTo Assist Remote Support v4, and GoTo Assist Service Desk. The maintenance window lasted about 3 hours, from Jan 26, 2025 7:03 AM UTC to Jan 26, 2025 10:03 AM UTC, during which these components were unavailable. The GoToConnect status page issued two updates during the incident, noting that maintenance was in progress and that updates would be provided as necessary. Services were restored to normal operation after the window at Jan 26, 2025 10:03 AM UTC.

GoToAssist Remote Support v4, GoToAssist Remote Support v5, and the GoTo Assist Service Desk were placed into a scheduled maintenance window starting at 7:00 AM UTC. The maintenance, listed as in progress on the GoToConnect status page, lasted about three hours and involved three components: GoTo Assist Remote Support v5, GoTo Assist Remote Support v4, and GoTo Assist Service Desk. The page documented the maintenance activity and noted the expected impact during the window. Two official updates were published as the work proceeded. Jan 25, 2025 7:03 AM UTC marked the start of the maintenance transition, and Jan 25, 2025 10:03 AM UTC indicated the maintenance was completed and services were returned to normal.

The incident concluded with the status returning to up at 10:03 AM UTC. Overall, the event was a planned maintenance window affecting three components, with updates provided by GoToConnect to document progress and completion. There were no broader outages reported outside the listed services during this period.

The incident affected multiple GoToConnect services including VoIP calls (deskphones, web, and mobile), PSTN outbound and inbound calls, and the Contact Center, as well as GoTo Meeting tools. Users experienced degraded meetings and voice functionality across these products. The outage began at 8:28 PM UTC and was resolved by 9:13 PM UTC, lasting approximately 45 minutes.

The GoTo status page issued three updates during the outage, acknowledging that multiple services were impacted and later confirming that affected components returned to normal as services were restored.