LogMeIn Rescue Outage History

LogMeIn Rescue is up right now

LogMeIn Rescue had 35 outages in the last 2 years totaling 54h 58m of downtime — averaging 1.4 incidents per month.

There were 35 LogMeIn Rescue outages since May 16, 2025 totaling 54h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.logmeinremotesupport.com

Major September 18, 2025

Contact Center – Call Queues and Contact Center – Issues logging into queues

Detected by Pingoru
Sep 18, 2025, 05:59 PM UTC
Resolved
Sep 18, 2025, 06:18 PM UTC
Duration
19m
Affected: Contact Center
Timeline · 4 updates
  1. investigating Sep 18, 2025, 05:59 PM UTC

    We are actively investigating reports that some Contact Center – Call Queues and Contact Center – Supervisor customers may be experiencing issues to login and out of the call queues. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Sep 18, 2025, 06:01 PM UTC

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

  3. monitoring Sep 18, 2025, 06:03 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.

  4. resolved Sep 18, 2025, 06:18 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.

Read the full incident report →

Major August 25, 2025

GoTo Connect - Issues with Outbound Calls - APAC region

Detected by Pingoru
Aug 25, 2025, 03:38 AM UTC
Resolved
Aug 25, 2025, 04:36 AM UTC
Duration
57m
Affected: PSTN Calls - Outbound
Timeline · 4 updates
  1. investigating Aug 25, 2025, 03:38 AM UTC

    We are actively investigating reports that some GoTo Connect VoIP Phones Calls and GoTo Connect customers from the APAC region may be experiencing issues while making outbound calls Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Aug 25, 2025, 04:28 AM UTC

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

  3. monitoring Aug 25, 2025, 04:30 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.

  4. resolved Aug 25, 2025, 04:36 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.

Read the full incident report →

Major August 20, 2025

Grasshopper - Issue with web portal and outgoing calls

Detected by Pingoru
Aug 20, 2025, 06:19 PM UTC
Resolved
Aug 20, 2025, 07:33 PM UTC
Duration
1h 14m
Affected: Grasshopper
Timeline · 4 updates
  1. investigating Aug 20, 2025, 06:19 PM UTC

    We are actively investigating reports that some Grasshopper customers may be experiencing loading the Grasshopper web portal and making outbound calls with the Grasshopper app. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Aug 20, 2025, 06:33 PM UTC

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

  3. monitoring Aug 20, 2025, 07:06 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.

  4. resolved Aug 20, 2025, 07:33 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.

Read the full incident report →

Major August 20, 2025

GoTo Connect - Incoming PSTN calls issue in Brazil

Detected by Pingoru
Aug 20, 2025, 05:58 PM UTC
Resolved
Aug 20, 2025, 06:21 PM UTC
Duration
23m
Affected: PSTN Calls - Inbound
Timeline · 4 updates
  1. investigating Aug 20, 2025, 05:58 PM UTC

    We are actively investigating reports that some GoTo Connect customers might be experiencing incoming call issues in Brazil. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Aug 20, 2025, 06:03 PM UTC

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

  3. monitoring Aug 20, 2025, 06:13 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.

  4. resolved Aug 20, 2025, 06:21 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.

Read the full incident report →

Major July 31, 2025

GoTo App/Web - inbound/outbound call failure

Detected by Pingoru
Jul 31, 2025, 02:54 PM UTC
Resolved
Jul 31, 2025, 03:10 PM UTC
Duration
16m
Affected: VoIP Calls - GoTo Connect WebVoIP Calls - GoTo Connect Mobile
Timeline · 4 updates
  1. investigating Jul 31, 2025, 02:54 PM UTC

    We are aware of reports where a subset of GoTo Connect users have been unable to place/receive calls on GoTo App and GoTo Web. Our engineers are investigating the issue, and we will provide an update as more details become available. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Jul 31, 2025, 03:00 PM UTC

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

  3. monitoring Jul 31, 2025, 03:03 PM UTC

    Our engineers have corrected the issue and we are receiving reports that calling is working as expected. We will continue monitoring the situation and provide a final update shortly.

  4. resolved Jul 31, 2025, 03:10 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.

Read the full incident report →

Major July 30, 2025

GoToMyPC Host page is not loading

Detected by Pingoru
Jul 30, 2025, 02:04 PM UTC
Resolved
Jul 30, 2025, 04:07 PM UTC
Duration
2h 2m
Affected: GoToMyPC
Timeline · 4 updates
  1. investigating Jul 30, 2025, 02:04 PM UTC

    We are actively investigating reports that some GoToMyPC customers may be experiencing issue with GoToMyPC Mycomputer Page. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Jul 30, 2025, 02:30 PM UTC

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

  3. monitoring Jul 30, 2025, 03:35 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.

  4. resolved Jul 30, 2025, 04:07 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.

Read the full incident report →

Major July 24, 2025

GoTo Connect - Multiple notifications of inbound calls in APAC

Detected by Pingoru
Jul 24, 2025, 01:39 AM UTC
Resolved
Jul 24, 2025, 05:10 AM UTC
Duration
3h 31m
Affected: VoIP Calls - DeskphonesVoIP Calls - GoTo Connect WebVoIP Calls - GoTo Connect MobilePSTN Calls - Inbound
Timeline · 6 updates
  1. investigating Jul 24, 2025, 01:39 AM UTC

    We are actively investigating reports that some GoTo Connect customers may be experiencing multiple notifications when receiving inbound calls in the GoTo Connect app. Investigation so far shows that the issue is limited to the APAC region. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified Jul 24, 2025, 02:05 AM UTC

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

  3. identified Jul 24, 2025, 03:00 AM UTC

    Our engineers keep working with the PSTN peer toward a resolution. We will provide another update shortly.

  4. identified Jul 24, 2025, 04:16 AM UTC

    Our engineers keep working with the PSTN peer toward a resolution. We will provide another update shortly.

  5. monitoring Jul 24, 2025, 04:28 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.

  6. resolved Jul 24, 2025, 05:10 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.

Read the full incident report →

Major July 9, 2025

Pro and Central Login error

Detected by Pingoru
Jul 09, 2025, 05:30 AM UTC
Resolved
Jul 09, 2025, 05:53 AM UTC
Duration
22m
Affected: Pro/CentralHamachi
Timeline · 4 updates
  1. investigating Jul 09, 2025, 05:30 AM UTC

    We are actively investigating reports that some Pro and Central customers may be experiencing a "D error" while logging in to their accounts.

  2. identified Jul 09, 2025, 05:34 AM UTC

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

  3. monitoring Jul 09, 2025, 05:42 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.

  4. resolved Jul 09, 2025, 05:53 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.

Read the full incident report →

Major May 16, 2025

GoTo Connect - Inbound and outbound calls failing in Brazil

Detected by Pingoru
May 16, 2025, 05:07 PM UTC
Resolved
May 17, 2025, 03:13 PM UTC
Duration
22h 5m
Affected: PSTN Calls - InboundPSTN Calls - Outbound
Timeline · 6 updates
  1. investigating May 16, 2025, 05:07 PM UTC

    We are actively investigating reports that some GoTo Connect VoIP phone customers may be experiencing call connection issues in Brazil. Our engineers are working to identify the issue and will provide another update shortly.

  2. identified May 16, 2025, 05:14 PM UTC

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

  3. identified May 16, 2025, 05:17 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified May 16, 2025, 06:50 PM UTC

    Our engineers are still engaged with the impacted PSTN peer, while working to put workarounds in place to mitigate customer impact. We will provide another update shortly.

  5. identified May 16, 2025, 09:54 PM UTC

    Our engineers have already implemented mitigation and workaround measures to help minimize the impact. However, we remain dependent on our PSTN peer to fully resolve the issue. We are monitoring the situation closely and will provide updates as new information becomes available.

  6. resolved May 17, 2025, 03:13 PM UTC

    We have confirmed with the affected PSTN peer 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.

Read the full incident report →