- 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 7h 25m it lasted.
Anything that failed between 2026-05-13 18:58 UTC and 2026-05-14 02:22 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 11
- investigating
We are actively investigating reports that some LogMeIn Rescue and Central customers may be experiencing issues downloading the applet to start or join remote sessions. Our engineers are working to identify the issue and will provide another update shortly.
provider
- identified
Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.
provider
- identified
Our engineers are continuing to work on this issue and continue to work towards a resolution. We will provide another update shortly.
provider
- identified
Our engineers are continuing to work on isolating the source of this issue. Due to its intermittent nature, trying again can allow to establish a proper connection. We will provide another update shortly.
provider
- monitoring
A potential fix was applied to resolve the issue, and we are continuing to monitor for stability. We will continue monitoring the situation and provide a final update shortly.
provider
- identified
Our engineers are still seeing some intermittent issues after the fix and are continuing to investigate those. We will provide a status update once we have further information. We will provide another update shortly.
provider
- identified
We are continuing to work towards a resolution to ensure stability in starting and joining sessions. We will provide another update shortly.
provider
- identified
Our engineers have identified a plan to get back the system to stustained stability and are starting to execute on it. We will provide another update shortly.
provider
- identified
Our engineers are executing on the established plan to get back the system to prolonged stability We will provide another update shortly.
provider
- monitoring
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
- 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-50230ff1c5
Is GoTo still down?
No, this incident was resolved 2026-05-14 02:22 UTC. For GoTo's live state, see https://down.guide/gotomeeting.
How long did it last?
7h 25m, from 2026-05-13 18:58 UTC to 2026-05-14 02:22 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.