LogMeIn GoTo APIs incident
LogMeIn Rescue, Pro, and Central - Issue downloading Rescue and Pro/Central applets
LogMeIn GoTo APIs experienced a major incident on May 13, 2026 affecting Rescue and Pro/Central, lasting 7h 24m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 13, 2026, 06:58 PM UTC
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.
- identified May 13, 2026, 07:22 PM UTC
Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.
- identified May 13, 2026, 08:04 PM UTC
Our engineers are continuing to work on this issue and continue to work towards a resolution. We will provide another update shortly.
- identified May 13, 2026, 09:13 PM UTC
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.
- monitoring May 13, 2026, 10:28 PM UTC
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.
- identified May 13, 2026, 10:40 PM UTC
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.
- identified May 14, 2026, 12:37 AM UTC
We are continuing to work towards a resolution to ensure stability in starting and joining sessions. We will provide another update shortly.
- identified May 14, 2026, 01:12 AM UTC
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.
- identified May 14, 2026, 02:03 AM UTC
Our engineers are executing on the established plan to get back the system to prolonged stability We will provide another update shortly.
- monitoring May 14, 2026, 02:12 AM 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.
- resolved May 14, 2026, 02:22 AM 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.