Live / GoTo / Incident
GoTo: LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session failures
GoTo · gotomeeting.comMajor incidentResolved2026-11-05 18:04 UTC
Public — what happened
Summary
GoTo said that some customers of LogMeIn Rescue and G2ARS v5 were having trouble, with attended sessions failing to start and unattended devices not being set up. The company began investigating at 15:36 UTC on 2026-11-05 and said its engineers had identified the problem by 15:48 UTC. It reported at 17:07 UTC that a correction was in place and that it was checking that all services worked, and the incident was marked resolved at 18:04.
Affected
Rescue, Pro/Central
Timeline
- Started — 2026-11-05 15:36 UTC
- Investigating — 2026-11-05 15:36 UTC
- Identified — 2026-11-05 15:48 UTC
- Monitoring — 2026-11-05 17:07 UTC
- Resolved — 2026-11-05 18:04 UTC · 2h 28m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 46, 2026, our weekly internet health report.