lagcheck can I play right now?

Is GoTo down right now?

Checked 1 minute ago

No — GoTo is working normally
Zoom, Twilio, Amazon Web Services and Elastic Cloud are all reporting problems at the same time. Amazon Web Services and Elastic Cloud are infrastructure a lot of what we watch runs on. We cannot tell from here whether that is the cause — we are reading status pages, not tracing dependencies — but it is worth ruling out before you blame your own line.
If you are having trouble anyway, the problem is more likely to be between you and GoTo than at GoTo itself. Two things worth checking, in order: your connection under load — a line that idles at 20 ms can jump to 300 ms while something uploads, which drops you from sessions and looks exactly like a server fault — and whether the people you play with see the same thing, since a service can be healthy in your region and unwell in theirs. Run a connection check.

The last 48 hours

Nothing wrong in the last 48 hours.

Last problem before that: 3 days ago, lasting 3h 38m.

Longer record

98.44%Clear of trouble, 31 days
4Problems seen
237h 59mLongest
3 daysLast problem
Clear of trouble, each day, last 31 days

This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for GoTo.

Something was impaired on 1.56% of our checks over that window. That is how often GoTo was reporting a problem somewhere, which is not the same as how often it was unreachable. The longest outage we have on record ran 237h 59m.

Day by day

The last 30 days of GoTo, one row each.

DayClearUpChecksStartedLongest ended
2026-09-27 so far today 100% 100% 1 none —
2026-09-26 100% 100% 288 none —
2026-09-25 100% 100% 287 none —
2026-09-24 100% 100% 286 none —
2026-09-23 85.02% 85.02% 287 1 3h 38m
2026-09-22 100% 100% 285 none —
2026-09-21 100% 100% 287 none —
2026-09-20 100% 100% 287 none —
2026-09-19 100% 100% 287 none —
2026-09-18 100% 100% 285 none —
2026-09-17 100% 100% 283 none —
2026-09-16 100% 100% 286 none —
2026-09-15 100% 100% 286 none —
2026-09-14 100% 100% 286 none —
2026-09-13 100% 100% 287 none —
2026-09-12 100% 100% 287 none —
2026-09-11 100% 100% 285 none —
2026-09-10 100% 100% 287 none —
2026-09-09 98.25% 98.25% 285 1 34 min
2026-09-08 96.48% 96.48% 284 1 55 min
2026-09-07 100% 100% 287 none —
2026-09-06 100% 100% 286 none —
2026-09-05 100% 100% 287 none —
2026-09-04 95.79% 95.79% 285 1 1h 5m
2026-09-03 100% 100% 286 none —
2026-09-02 100% 100% 285 none —
2026-09-01 100% 100% 285 none —
2026-08-31 100% 100% 284 none —
2026-08-30 100% 100% 285 none —
2026-08-29 100% 100% 287 none —

Clear is the share of checks that found nothing wrong at all; Up is the share that found GoTo actually reachable — a vendor reporting one impaired component scores zero on the first and a hundred on the second, and both are true. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.

Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.

Outage history

StartedLastedSeverityWhat happened
2026-09-23 12:53 UTC 3h 38m partly down GoTo Connect - Issue with incoming calls
2026-09-09 15:46 UTC 34 min partly down Pro, Central, GoToAssist Remote Support v5 and LogMeIn Rescue - Elevated error rates
2026-09-08 16:55 UTC 55 min partly down Connectivity issues
2026-09-04 12:31 UTC 1h 5m partly down Emails not being delivered to customers
2026-08-27 15:55 UTC 13h 50m partly down LogMeIn Rescue, G2ARS v5, Pro, and Central - Elevated session launch failures
2026-08-15 15:02 UTC 1h 34m partly down Grasshopper - password reset and OTP emails blocked
2026-08-04 18:11 UTC 237h 59m partly down GoTo Customer Engagement - Whatsapp campaign issues
2026-08-04 18:11 UTC 227h 39m partly down GoTo Customer Engagement - Whatsapp campaign issues

When the status page says green and you still can't play

Status pages report the vendor's view of their own service, and they lag real outages — often by many minutes, sometimes by hours, because a human usually has to confirm before anything is posted. They also can't see the two things most likely to be wrong at your end.

The first is your own connection under load. A line that idles at 20 ms can jump to 300 ms the moment something starts uploading, which drops you from sessions and looks exactly like a server fault. Your plan speed says nothing about this; it's called bufferbloat and almost nobody measures it.

The second is where everyone else in your group is. A service can be healthy in your region and unwell in theirs, and if one person is hosting, their problem is everyone's problem.

Playing with people elsewhere

GoTo being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.

Other services we watch

Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.