Skip to main content
GoTo

LogMeIn Rescue, Pro, Central, and G2ARS v5 - session failure

Partial outage Lasted 9h 7m · started · GoTo's page

Level
confirmed
Worst impact
Partial outage
Components
Rescue, Pro/Central
Down Index
33of 100

What to do

  • Check whether you use GoTo Rescue, Pro/Central. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 9h 7m it lasted.

    Anything that failed between 2026-10-29 14:08 UTC and 2026-10-29 23:15 UTC may need a replay.
  • Subscribe to GoTo's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=gotomeeting works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GoTo 7

  1. investigating

    We are actively investigating reports that some LogMeIn Rescue, Pro, Central, and G2ARS v5 customers may be experiencing attended session not starting and unattended devices not deployed. Our engineers are working to identify the issue and will provide another update shortly.

    provider

  2. investigating

    We are still actively investigating LogMeIn Rescue, Pro, Central, and G2ARS v5 attended session not starting and unattended devices not deployed. LogMeIn Rescue customers can trust the applet as a workaround. Pro, Central and G2ARS v5 customers can continue to retry. Our engineers are working to identify the issue. Another update will follow.

    provider

  3. identified

    Our engineers are seeing improvements and are actively working towards a full resolution. We will provide another update shortly.

    provider

  4. monitoring

    Our engineers are confirming that all services are functional. We will continue monitoring the situation for an extended period and provide a final update later.

    provider

  5. monitoring

    We are investigating a renewed increase in activity related to the recent issue affecting LogMeIn Rescue, Pro, Central, and G2ARS v5. Our engineers have not yet observed a corresponding increase in signing failures and are validating service health and customer impact. We’ll provide another update momentarily.

    provider

  6. monitoring

    Our engineers we are confirming that all services are functional once again. We will continue monitoring the situation and provide updates as needed.

    provider

  7. resolved

    We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-9b521b89d6

Is GoTo still down?

No, this incident was resolved 2026-10-29 23:15 UTC. For GoTo's live state, see https://down.guide/gotomeeting.

How long did it last?

9h 7m, from 2026-10-29 14:08 UTC to 2026-10-29 23:15 UTC, by the times GoTo posted.

What was affected?

GoTo named Rescue, Pro/Central.

What caused it?

GoTo hasn't published a root cause. If it does, it shows here.

Where does this come from?

GoTo's official status page, https://status.goto.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.