- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Pro/Central, Miradore, MDM, Remote Execution, join.me
- Down Index
- 33of 100
What to do
Check whether you use GoTo Pro/Central, Miradore, MDM, Remote Execution and 1 more. 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 5h 27m it lasted.
Anything that failed between 2025-10-29 16:16 UTC and 2025-10-29 21:44 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 14
- investigating
We are actively investigating reports that some LogMeIn Resolve customers may be experiencing issues accessing the application. Our engineers are working to identify the issue and will provide another update shortly.
provider
- identified
Our engineers have identified the issue coming from an upstream cloud provider and are now actively working towards a resolution. We will provide another update shortly.
provider
- identified
We are currently seeing impacts on the following features across the LogMeIn portfolio: - Resolve ZeroTrust features - Access to Pro/Central - GoToMyPC Web Access We will provide another update shortly as our engineering teams are working on mitigation actions.
provider
- identified
For Pro/Central, the following actions can be taken as a workaround to access Remote Control. - Click on Computer Properties > At "Status" field Click Connect to this Computer link - Click on Computer Properties > Select "Desktop Shortcut" tab > Follow the instructions in the "Create your shortcut" section - Start Remote Control via LogMeIn Client
provider
- identified
Our engineers have identified that join.me is also affected by this issue.
provider
- identified
Our engineers continue to monitor the situation and explore potential workarounds for this issue.
provider
- identified
We are continuing to monitor the behavior of all LogMeIn products. Microsoft Azure is currently experiencing an incident which is at the source of these issues. We will be updating this status page in the next 30 minutes or earlier if the situation progresses.
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
- 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 have implemented workarounds for some LogMeIn Resolve and were able to restore the Login, Helpdesk and Reporting functions.
provider
- identified
We are continuing to monitor the situation with the Azure incident and applying workarounds where possible.
provider
- identified
Our engineers are still monitoring for any improvements the product availability in the light of mitigation actions performed by Microsoft Azure. We will provide another update in 1 hour or earlier if the situation improves.
provider
- monitoring
Our engineers have confirmed 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 the impact on 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-65f57692a7
Is GoTo still down?
No, this incident was resolved 2025-10-29 21:44 UTC. For GoTo's live state, see https://down.guide/gotomeeting.
How long did it last?
5h 27m, from 2025-10-29 16:16 UTC to 2025-10-29 21:44 UTC, by the times GoTo posted.
What was affected?
GoTo named Pro/Central, Miradore, MDM, Remote Execution and 1 more.
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.