LogMeIn Outage History

LogMeIn experienced a major authentication issue causing 504 timeouts that prevented users from logging into multiple GoTo applications including GoTo Meeting, GoTo Admin, GoTo Connect, Contact Center, Analytics, and Resolve. The authentication system failure affected access to various GoTo services for approximately 1.2 hours before engineers identified and corrected the underlying cause. All systems were confirmed to be fully operational after the resolution.

GoTo Connect VoIP phone customers experienced intermittent failures when completing inbound calls due to 503 errors caused by an incident with a third-party service provider. The issue affected some customers' ability to receive calls properly for 35 minutes. The underlying provider resolved their incident, restoring full functionality to all GoTo Connect VoIP services.

GoTo Connect customers experienced call quality issues across Web, Desktop, and Mobile platforms for 51 minutes. The incident affected voice communication quality for users of the service. Engineers identified and corrected the underlying issue, with all systems returning to full operational status.

GoTo Connect customers experienced audio quality issues during phone calls for 27 minutes. Engineers identified and corrected the underlying problem affecting call audio. The service was restored to full operational status with confirmed resolution.

GoTo Webinar, GoTo Training, and GoTo Meeting experienced a major service disruption where customers were unable to start sessions. The issue affected all three platforms for approximately 2.7 hours before engineers identified the root cause and deployed mitigating actions. The services were fully restored and confirmed operational after monitoring the recovery across all affected systems.

GoTo Contact Center experienced a major incident where call queue distribution failed, preventing queued calls from being routed to agents. The issue affected Contact Center customers using call queue functionality for 3.4 hours. Engineers identified and corrected the underlying problem, restoring full service operations.