Login to GoTo applications - 504 timeout - multiple products impacted

What to do

• Check whether you use GoTo GoTo Meeting, VoIP Calls - GoTo Connect Web, GoTo Webinar, Helpdesk and 9 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 9m it lasted.

  Anything that failed between 2026-04-20 14:14 UTC and 2026-04-20 15:23 UTC may need a replay.

• Subscribe to GoTo's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=gotomeeting works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GoTo 6

1. investigatingApr 20, 2026, 2:14 PM UTC

   We are actively investigating reports that some GoTo Meeting and GoTo Admin customers may be experiencing timeouts when performing operations in GoTo Admin and GoTo Meeting components. Our engineers are working to identify the issue and will provide another update shortly.

   provider

2. identifiedApr 20, 2026, 2:34 PM UTC

   Our engineers have identified the issue and are actively working to correct the underlying cause. This issue appears to have impacted functionality with GoTo Admin, GoTo Connect, Contact Center, Analytics, Resolve, and other related services. We will provide another update shortly.

   provider

3. identifiedApr 20, 2026, 2:55 PM UTC

   This issue affects authentication to the various GoTo applications, which also affects Resolve, Pro/Central, in addition to GoTo Admin, Connect and Meetings. We will provide another update shortly.

   provider

4. identifiedApr 20, 2026, 3:12 PM UTC

   Our engineers are seeing signs of recovery for login to our applications. Our team is still engaged in ensuring prolonged stability of the applications. We will provide another update shortly.

   provider

5. monitoringApr 20, 2026, 3:16 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.

   provider

6. resolvedApr 20, 2026, 3:23 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.