Live / GoTo / Incident
GoTo: LogMeIn Pro and Central website
GoTo · gotomeeting.comMajor incidentResolved2026-10-10 06:20 UTC
Public — what happened
Summary
GoTo said that starting at 04:56 UTC on 2026-10-10, some LogMeIn Pro and Central customers might have trouble getting into the website, and it rated the incident as major. By 05:22 UTC the company reported it had found the problem, though it did not say publicly what the problem was. GoTo said a fix was in place at 05:56 UTC, and it marked the incident resolved at 06:20 after a period of watching to confirm services were working.
Affected
Pro/Central
Timeline
- Started — 2026-10-10 04:56 UTC
- Investigating — 2026-10-10 04:56 UTC
- Identified — 2026-10-10 05:22 UTC
- Monitoring — 2026-10-10 05:56 UTC
- Resolved — 2026-10-10 06:20 UTC · 1h 24m 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 42, 2026, our weekly internet health report.