Live / GoTo / Incident
GoTo: LogMeIn Rescue, Pro, Central, and G2ARS v5 - session failure
GoTo · gotomeeting.comMajor incidentResolved2026-10-29 23:15 UTC
Public — what happened
Summary
GoTo said some customers of LogMeIn Rescue, Pro, Central and G2ARS v5 could not start attended sessions, and unattended devices were not being deployed, beginning at 14:08 UTC on October 29. The company suggested Rescue customers use the applet and Pro, Central and G2ARS v5 customers retry in the meantime. GoTo reported improvements by 15:22 UTC and said all services were working again by 15:46 UTC. It later looked into a renewed rise in activity at 18:51 UTC, said it had not seen matching failures, confirmed services were working at 19:27 UTC, and marked the incident resolved at 23:15 UTC without stating a cause.
Affected
Rescue, Pro/Central
Timeline
- Started — 2026-10-29 14:08 UTC
- Investigating — 2026-10-29 14:08 UTC (2 updates)
- Identified — 2026-10-29 15:22 UTC
- Monitoring — 2026-10-29 15:46 UTC (3 updates)
- Resolved — 2026-10-29 23:15 UTC · 9h 07m 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 45, 2026, our weekly internet health report.