Live  /  GoTo  /  Incident

GoTo: LogMeIn Rescue and G2ARS v5 - new session fails

GoTo · gotomeeting.comMajor incidentResolved2026-10-28 21:22 UTC
Public — what happened

Summary

GoTo said some customers of LogMeIn Rescue and G2ARS v5 were unable to start attended support sessions and could not get unattended devices deployed, with the problem first reported at 18:38 UTC on 2026-10-28. By 18:59 UTC the company said its engineers had found the issue, and it suggested customers retry their action in the meantime. At 19:58 UTC GoTo said it was still working toward a fix together with its solution provider, and the incident was later marked resolved at 21:22.

Affected

Rescue

As listed on GoTo’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach GoTo against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for GoTo: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the GoTo report →

More from GoTo

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the GoTo status & history page.

Related: GoTo status & history. SquidGrid is not affiliated with GoTo.