GoToMeeting System Status
Identified - We’re happy to announce that on January 31, 2017, the GoTo business of Citrix (which includes GoToMeeting, GoToWebinar, GoToTraining, GoToMyPC, GoToAssist, OpenVoice, Grasshopper and Event Services) separated from Citrix Systems, Inc. and merged with LogMeIn, Inc. For our customers, the new LogMeIn will offer best-in-class capabilities across a much larger combined portfolio while featuring the scale, resources and world-class talent required to accelerate innovation and address future customer needs.

We are very excited about the possibilities this merger presents for our customers. For the vast majority of customers, no actions will be needed. Our applications will continue to update automatically and take care of any changes required.

If you are an IT Admin, Billing Admin or have an Integration based on one of our APIs, you will need to make some updates. Full details of what you will need to do can be found here: https://support.logmeininc.com/account-update-faqs

Please follow this announcement in our customer community so you are automatically updated with new information as it becomes available: https://community.gotomeeting.com/gotomeeting/topics/important-updates-for-admins-after-the-merger-with-logmein-inc
May 24, 23:27 UTC
GoToMeeting Operational
GoToWebinar Operational
GoToTraining Operational
OpenVoice Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Aug 19, 2017

No incidents reported today.

Aug 18, 2017

No incidents reported.

Aug 17, 2017

No incidents reported.

Aug 16, 2017
Resolved - The Maintenance is completed.

We apologize for the iconvenience this may have caused
Aug 16, 07:32 UTC
Investigating - In order to provide our customers with the highest level of service, we have scheduled maintenance on GotoMeeting. The expected down time is 20-30min. During this time users will not be able to start new sessions on GoToMeeting, GoToTraining & GoToWebinar. In-flight sessions will be unaffected.. We sincerely apologize for the inconvenience caused by this maintenance.
Aug 16, 06:41 UTC
Aug 15, 2017
Resolved - At this time functionality is 100% restored.
Aug 15, 19:17 UTC
Monitoring - Changes have been made to mitigate this issue. No new problems are expected. The engineering team is monitoring the situation actively.
Aug 15, 16:33 UTC
Identified - The problem has been identified and engineers are working to resolve the problem.
Aug 15, 14:35 UTC
Investigating - We are aware of some users being unable to join or start GoToMeeting, GoToWebinar, and GoToTraining sessions. We are currently investigating this issue. We appreciate your patience.
Aug 15, 14:17 UTC
Aug 14, 2017

No incidents reported.

Aug 13, 2017

No incidents reported.

Aug 12, 2017

No incidents reported.

Aug 11, 2017

No incidents reported.

Aug 10, 2017

No incidents reported.

Aug 9, 2017

No incidents reported.

Aug 8, 2017
Completed - The scheduled maintenance has been completed.
Aug 8, 10:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 8, 09:01 UTC
Scheduled - In order to provide our customers with the highest level of service, we have scheduled maintenance on GoToMeeting, GoToWebinar, and GoToTraining. The maintenance will take approximately five minutes. During this time no impact is expected for users of our product. We sincerely apologize for the inconvenience which may be caused by this maintenance.
Aug 7, 12:12 UTC
Aug 7, 2017

No incidents reported.

Aug 6, 2017

No incidents reported.

Aug 5, 2017

No incidents reported.

Aug 4, 2017
Resolved - A fix has been deployed and all tests have been successful. The few affected customers ar now able to use all GotoMeeting functionality as before.

We apologize for the inconvenience this may have caused to you and your customers
Aug 4, 09:06 UTC
Identified - We identified a few users who are currently not able to use the GotoMeeting service nor login into their Gotomeeting portal. We are working towards a solution.

We apologize for the inconvenient this may cause
Aug 4, 08:18 UTC
Aug 3, 2017
Resolved - We have confirmed that this issue is completely resolved and all systems are 100% operational at this time.
Aug 3, 16:30 UTC
Monitoring - We have identified the issue and our engineering team has taken steps to resolve it. The script error is no longer occurring when logging in to the software on Windows computers and the software is working as expected.

While there was no impact to the functionality of the GoToMeeting platform during this time period, we are monitoring the situation to ensure the scripting error is completely resolved.
Aug 3, 15:49 UTC
Investigating - We are investigating a script error prompt that occurs when logging in to the GoToMeeting software on Windows computers, giving the message "An error has occurred in the script on this page". Clicking Yes or No on this prompt will clear the error and allow users to log in and use the service as normal. This error does not appear to have any impact on the functionality of the GoToMeeting service; organizers can still schedule, start, and host sessions as expected.

We are actively investigating the root cause of this issue.
Aug 3, 14:43 UTC
Aug 2, 2017

No incidents reported.

Aug 1, 2017

No incidents reported.

Jul 31, 2017

No incidents reported.

Jul 30, 2017

No incidents reported.

Jul 29, 2017

No incidents reported.

Jul 28, 2017

No incidents reported.

Jul 27, 2017

No incidents reported.

Jul 26, 2017

No incidents reported.

Jul 25, 2017

No incidents reported.

Jul 24, 2017

No incidents reported.

Jul 23, 2017

No incidents reported.

Jul 22, 2017

No incidents reported.

Jul 21, 2017

No incidents reported.

Jul 20, 2017
Resolved - Our engineers have identified and corrected the issue. We are 100% operational at this time.
Thank you for your patience.
Jul 20, 14:52 UTC
Investigating - Customers are reporting difficulty reaching our Canadian Toll numbers for OpenVoice. GoToMeeting and GoToWebinar are not impacted at this time. Our engineers are actively investigating the root cause. We apologize sincerely for those that are affected.

A workaround for Canadian callers would be to utilize any available toll free numbers or else dial internationally to the US numbers.
Jul 20, 14:42 UTC