GoToMeeting® System Status
Investigating - Some customers will encounter dificulties joining an Android devices using Chrome 40. We are working on this issue and the Chrome developement team has been notified.
Manual Workaround: If you sees the error message ("This webpage is not available") tap the “back” button, then tap on “Tap to join the session”.

We apologize for the inconvenience this may cause.
Jan 28, 14:05 UTC

About This Site

For information regarding Citrix Heartbleed vulnerability, please visit support.gotomeeting.com and follow the Recommended link for "SSL Security Update: Heartbleed bug".

GoToMeeting ® Operational
GoToWebinar ® Operational
GoToTraining® Operational
OpenVoice® Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Past Incidents
Jan 27, 2015
On 1/26/15 8:00am - 3:45pm Coordinated Universal Time (UTC), some GoToMeeting, Webinar, Training, and OpenVoice customers experienced "dead air" or silence after entering the conference access code. Callers may have also experienced a busy signal or an "out of service" message when dialing into the conference. Customers using Mic-and-Speakers options were unaffected. This issue was caused by a hardware fault in our audio infrastructure. Our operations team failed over to backup resources, and full operation was restored at 3:45pm UTC. We sincerely apologize for any inconvenience that this issue has caused.
Jan 27, 22:22 UTC
Jan 26, 2015

No incidents reported.

Jan 25, 2015

No incidents reported.

Jan 24, 2015

No incidents reported.

Jan 23, 2015

No incidents reported.

Jan 22, 2015

No incidents reported.

Jan 21, 2015
On 1/21/2015 from approximately 1:30 to 2:15 PM EST some callers may have experienced dropped calls or one-way audio while dialled into our Canada toll conference numbers. We sincerely apologize for any inconvenience this event has caused you or your customers.
Jan 21, 16:48 UTC
Jan 20, 2015

No incidents reported.

Jan 19, 2015

No incidents reported.

Jan 18, 2015

No incidents reported.

Jan 17, 2015

No incidents reported.

Jan 16, 2015

No incidents reported.

Jan 15, 2015

No incidents reported.

Jan 14, 2015

No incidents reported.

Jan 13, 2015

No incidents reported.

Jan 12, 2015

No incidents reported.

Jan 11, 2015

No incidents reported.

Jan 10, 2015

No incidents reported.

Jan 9, 2015
Resolved - At this time the changes to the affected accounts have been reverted, and service has been fully restored. We apologize for any frustration this incident caused, and our operations team is working to ensure this situation does not recur.
Jan 9, 17:23 UTC
Investigating - We are currently investigating renewed reports that OpenVoice users may be unable to start a conference bridge. After the caller enters the conference room number, they receive the following message:

"Thank you for calling Open Voice. This conference room number is no longer active. Please contact your account administrator with any questions. Code 5. Goodbye."

We apologize for any frustration that is being caused to you or your clients.
Jan 8, 22:39 UTC
Resolved - The resolution for this issue has been deployed and GoToTraining is 100% operational at this time. We apologize for any frustration this issue may have caused.
Jan 9, 03:46 UTC
Update - We identified a failure in the system which caused sending update and notification emails to past Gototraining occurences. Our team is currently working on a fix which will be deployed soon.

We apologize for the inconvenience this may have caused to you and your customers.
Jan 8, 18:49 UTC
Monitoring - We have received no new cases regarding incorrect email referencing past GoToTraining sessions. We are continuing to still investigating the cause and monitor the situation. We apologize for any frustration experienced by you or your clients.
Jan 8, 14:49 UTC
Update - We are still investigating the issue with the developers.
Jan 8, 14:18 UTC
Investigating - There are GoToTraining customers who are receiving incorrect email messages from our system related to the sessions they had in the past. There should not be any issue with starting or joining new sessions. We sincerely apologize for the disruption in service to you and your customers. This is top priority and we are working towards a resolution as quickly as possible.
Jan 8, 13:34 UTC
Jan 8, 2015
Resolved - At this time the changes to the affected accounts have been reverted, and service has been fully restored. We apologize for any frustration this incident caused, and our operations team is working to ensure this situation does not recur.
Jan 8, 04:07 UTC
Identified - We have identified the cause of the issue which is affecting a select group of customers. We are working to identify all of the accounts and undo the change that resulted in this issue. We appreciate your patience while we work to resolve this issue.
Jan 8, 00:39 UTC
Investigating - We are currently investigating reports that OpenVoice users may be unable to start a conference bridge. After the caller enters the conference room number, they receive the following message:

"Thank you for calling Open Voice. This conference room number is no longer active. Please contact your account administrator with any questions. Code 5. Goodbye."

We apologize for any frustration that is being caused to you or your clients.
Jan 8, 00:23 UTC
Jan 7, 2015

No incidents reported.

Jan 6, 2015

No incidents reported.

Jan 5, 2015

No incidents reported.

Jan 4, 2015

No incidents reported.

Jan 3, 2015
Resolved - At this time GoToMeeting audio service has been fully restored. We apologize for any frustration experienced and thank you for your patience.
Jan 3, 02:16 UTC
Investigating - Some GoToMeeting customers may be experiencing difficulties when trying to connect to audio bridges for new sessions. VoIP customers may not be able to connect to audio, and PSTN users dialing in may be dropped after entering their audio PIN. We are working to restore service as soon as possible. We sincerely apologize for any inconvenience this event has caused you or your customers.
Jan 3, 02:08 UTC
Jan 2, 2015

No incidents reported.

Jan 1, 2015

No incidents reported.

Dec 31, 2014

No incidents reported.

Dec 30, 2014

No incidents reported.

Dec 29, 2014

No incidents reported.