LogMeIn Rescue, G2ARS v5, Pro, and Central - Elevated session launch 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 1d it lasted.

  Anything that failed between 2026-08-27 15:55 UTC and 2026-08-28 16:24 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. identifiedAug 27, 2026, 3:55 PM UTC

   Our engineers are investigating issues with code signing for Rescue, GoToAssist v5, Pro and Central, which can lead to intermittent failures when starting sessions. We will provide another update shortly.

   provider

2. identifiedAug 27, 2026, 4:38 PM UTC

   Our engineers continue to investigate the code signing issues reported for Rescue, GoTo Assist v5, Pro, and Central. We will provide another update shortly.

   provider

3. monitoringAug 27, 2026, 5:40 PM UTC

   Our engineers are seeing an improvement on the situation and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

   provider

4. resolvedAug 28, 2026, 4:24 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.