LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session failures

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 2h 28m it lasted.

  Anything that failed between 2026-11-05 15:36 UTC and 2026-11-05 18:04 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 4

1. investigatingNov 5, 2026, 3:36 PM UTC

   We are actively investigating reports that some LogMeIn Rescue 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. identifiedNov 5, 2026, 3:48 PM UTC

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

   provider

3. monitoringNov 5, 2026, 5:07 PM UTC

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

   provider

4. resolvedNov 5, 2026, 6:04 PM UTC

   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

Corrections

None so far.

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