GoTo Outage History

GoTo experienced a major authentication outage lasting 1.2 hours that caused 504 timeout errors across multiple products including GoTo Meeting, GoTo Admin, GoTo Connect, GoTo Webinar, GoTo Training, and other services. Users reported being unable to initiate sessions, encountering bad gateway errors, and timeouts when trying to create support sessions or perform administrative operations. Engineers identified and corrected the underlying authentication issue, with all systems confirmed as fully operational after monitoring for stability.

GoTo Connect VoIP phone customers experienced intermittent failures when completing inbound calls due to an incident with a third-party service provider. The issue affected PSTN inbound calls and lasted 33 minutes before being fully resolved. Engineers identified the root cause as originating from the underlying service provider and confirmed all systems returned to 100% operational status.

GoTo Connect experienced call quality issues affecting VoIP calls on Web, Desktop, and Mobile platforms for 52 minutes. Engineers identified and corrected the underlying issue, restoring all systems to full operational status. The incident has been resolved with monitoring confirmed that all services are functioning normally.

GoTo Connect customers experienced audio quality issues affecting all call types including deskphones, web, mobile, and inbound/outbound PSTN calls for 29 minutes. Engineers identified and corrected the underlying issue, restoring full operational status to all voice services.

GoTo Webinar, GoTo Training, and GoTo Meeting experienced issues preventing users from starting sessions for approximately 2.8 hours. The incident affected all three services simultaneously, with engineers identifying and deploying mitigating actions to resolve the problem. The issue was fully resolved with all systems returning to 100% operational status.

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 for 3.4 hours while engineers investigated, identified, and resolved the underlying problem. The service was restored to full operational status with ongoing monitoring to ensure stability.