GoToConnect incident

GoTo Connect - inbound/outbound call failures

Major Resolved View vendor source →

GoToConnect experienced a major incident on July 2, 2026 affecting VoIP Calls - GoTo Connect Web, lasting 6h 37m. The incident has been resolved; the full update timeline is below.

Started
Jul 02, 2026, 11:49 AM UTC
Resolved
Jul 02, 2026, 06:27 PM UTC
Duration
6h 37m
Detected by Pingoru
Jul 02, 2026, 11:49 AM UTC

Affected components

VoIP Calls - GoTo Connect Web

Update timeline

  1. investigating Jul 02, 2026, 11:49 AM UTC

    We are actively investigating reports that a subset of GoTo Connect customers may be experiencing issues with inbound and outbound calls. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Jul 02, 2026, 11:54 AM UTC

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

  3. identified Jul 02, 2026, 01:43 PM UTC

    Our engineers continue to investigate the issue and are actively working to determine the best path toward resolution. We will provide another update shortly.

  4. identified Jul 02, 2026, 02:12 PM UTC

    Our engineers are currently working on a plan to mitigate the issues and continue working toward resolution. We will provide another update shortly.

  5. identified Jul 02, 2026, 03:14 PM UTC

    Our engineers are continuing to implement a fix for the issue. We will provide another update shortly.

  6. identified Jul 02, 2026, 04:06 PM UTC

    Our engineers are continuing to investigate several underlying causes that result in the known issue. This includes identifying and following patterns, as well as understanding the full customer impact is. At this time, the investigation is ongoing. We will provide additional updates shortly.

  7. monitoring Jul 02, 2026, 04:36 PM UTC

    Our engineers have implemented a fix that has addressed the inbound/outbound call issues that were reported, and we are now monitoring for continued stability. We will provide a final update shortly.

  8. resolved Jul 02, 2026, 06:27 PM UTC

    Our engineers are now seeing that all services are functional. We will conduct an internal review of this issue and will make appropriate improvements to ensure that this issue does not reoccur.