GoToConnect incident

Multiple GoTo Products - Issues starting sessions

Major Resolved View vendor source →

GoToConnect experienced a major incident on February 18, 2025 affecting GoTo Meeting and GoTo Webinar and 1 more component, lasting 3h 15m. The incident has been resolved; the full update timeline is below.

Started
Feb 18, 2025, 03:45 PM UTC
Resolved
Feb 18, 2025, 07:00 PM UTC
Duration
3h 15m
Detected by Pingoru
Feb 18, 2025, 03:45 PM UTC

Affected components

GoTo MeetingGoTo WebinarGoTo TrainingGoTo Assist Remote support v4GoTo Assist Service DeskGoTo Assist Corporate

Update timeline

  1. investigating Feb 18, 2025, 03:45 PM UTC

    We are actively investigating reports that some GoToMeeting, GoTo Webinar, GoTo Training as well as GoTo Assist customers may be experiencing issue starting sessions. Our engineers are working to identify the issue and will provide another update shortly.

  2. investigating Feb 18, 2025, 04:15 PM UTC

    We are actively investigating reports that some GoTo customers may be intermittent experiencing issues. These issues vary according to the product. For GoTo Meeting, Webinar and Training, as well as for GoTo Assist, we are seeing intermittent issues with starting and joining sessions. For GoTo Connect, calls are not affected, but customers may see issues with presence, fax and license provisioning. Our engineers are working to identify the issue and will provide another update shortly.

  3. identified Feb 18, 2025, 04:28 PM UTC

    Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

  4. identified Feb 18, 2025, 05:04 PM UTC

    We are seeing some improvements in functionality of the different products which were affected by this issue. We will provide another update shortly.

  5. identified Feb 18, 2025, 05:36 PM UTC

    The teams are continuing to work on mitigation options for the various services, as well as trying to address the root cause of this issue. We will provide another update shortly.

  6. monitoring Feb 18, 2025, 05:42 PM UTC

    Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

  7. resolved Feb 18, 2025, 07:00 PM UTC

    We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.