In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 05, 2022 - 16:01 UTC
Scheduled - In the past, IP-only allowlisting was possible due to static IP ranges that were not updated often. As of February 19, 2023, certain components of both GoToAssist Corporate and GoToAssist Remote Support v.4 will be moving to AWS CloudFront and require domain-allowlisting, due to the more dynamic nature of the CloudFront IP ranges being changed frequently and managed by a third party (AWS).
Before February 19, 2023, please be sure to make the following changes to your allowlisting to prevent disruption in service.
** GoToAssist Corporate If current allowlisting is by IP-range only, please add the following domains:
If current allowlisting is by domain wildcard only, please add the following domains ++ (the other necessary wildcard(s) should already be in configured in your allowlisting – reference article below):
If current allowlisting is by domain wildcard only, there should be no changes, as the domains have been listed on the Universal Allowlisting for quite some time, however if errors occur, please check the domains required above.
Welcome to the GoTo status page for Rescue, GoToAssist and GoToAssist Corporate. Any known issues affecting these products will be tracked on this page. Potential service interruptions may vary from customer to customer depending on the systems or services impacted.
Please reach out to our Customer Support team at https://support.goto.com/ if you have questions or need additional assistance.
As part of our commitment to provide exceptional service and reliability to our customers, GoToAssist Remote Support v5 will be conducting service maintenance on the following date and time listed below. Our team will be taking all appropriate actions to minimize service interruptions during this event.
Date and Time: February 02, 2023, 08:00 AM UTC to 08:30 AM UTC
Purpose: This maintenance is to ensure and maintain system performance and stability.
Duration: All maintenance will be performed within the 30 minutes maintenance window.
What to expect: During the maintenance window GoToAssist Remote Support v5 customers will not be able to start a session with the support key (using the 9-digit session pin) for a 5 minutes period during the entire maintenance window. In-flight sessions will be affected for a 5 minutes period.
We would like to thank you for your patience and understanding during this time period. Posted on
Jan 27, 2023 - 12:36 UTC
Completed -
The scheduled maintenance has been completed.
Jan 27, 08:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 27, 08:00 UTC
Scheduled -
As part of our commitment to provide exceptional service and reliability to our customers, GoToAssist Remote Support v5 will be conducting service maintenance on the following date and time listed below. Our team will be taking all appropriate actions to minimize service interruptions during this event.
Date and Time: January 27, 2023, 08:00 AM UTC to 08:30 AM UTC
Purpose: This maintenance is to ensure and maintain system performance and stability.
Duration: All maintenance will be performed within the 30 minutes maintenance window.
What to expect: During the maintenance window on GoToAssist Remote Support v5, starting a session with the support key (using the 9-digit session pin) will not function, however, if the session is started outside of the aforementioned time frame, then the session will not be affected. In case a session ends in the timeframe mentioned above, then it may not appear in Session Usage Report.
We would like to thank you for your patience and understanding during this time period.
Jan 26, 16:59 UTC
Resolved -
From January 24, 10:07 PM UTC until 10:26 PM UTC, GoTo Assist Service Desk customers may have experienced a 502 error while trying to use the website https://support.assist.com/portal. This was also affecting the application itself. Immediately after the root cause of the issue was discovered, it was promptly fixed.
We have confirmed that the issue has been resolved completely and all systems are 100% operational at this time.
We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.
Jan 24, 22:30 UTC