Skip to main content
GoTo

GoTo Connect - Issues with messaging and notifications

Partial outage Lasted 23h 46m · started · GoTo's page

Level
confirmed
Worst impact
Partial outage
Components
VoIP Calls - Deskphones, VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, Messaging - Chat, Administration Portal
Down Index
35of 100

What to do

  • Check whether you use GoTo VoIP Calls - Deskphones, VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, Messaging - Chat and 1 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 23h 46m it lasted.

    Anything that failed between 2025-09-17 19:03 UTC and 2025-09-18 18:49 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 10

  1. investigating

    We are actively investigating reports that some GoTo Connect customers may be experiencing issues, notably with messaging, some incoming call notifications. as well as loading GoTo Admin. Our engineers are working to identify the issue and will provide another update shortly.

    provider

  2. identified

    Our engineers have identified the issue and are now actively working towards a resolution. Due to the nature of the issue, the effects can be varied, but include access to GoToAdmin, issues sending or receiving SMS. We will provide another update shortly.

    provider

  3. identified

    Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update shortly.

    provider

  4. monitoring

    Our engineers have corrected the issue and we monitoring the gradual recovery of the affected services. We will continue monitoring the situation and provide another update shortly.

    provider

  5. identified

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

    provider

  6. identified

    Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update shortly.

    provider

  7. identified

    Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update shortly.

    provider

  8. identified

    Our engineers are still working towards a resolution to this issue. We are continuing to take some actions and see improvements in internal metrics. We will provide another update as soon as it becomes available.

    provider

  9. monitoring

    Our engineers have corrected the issue which arose as a side-effect of mitigating the initial problem. The main impact was an error message when starting the GoTo App, on Desktop, Web or Mobile. Recovery is going to be transparent for these clients and, specifically for the mobile app, can also be manually triggered by simply re-opening the application on the mobile device. We will continue monitoring the situation through our internal metrics and provide a final update shortly.

    provider

  10. resolved

    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

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-dbf0960767

Is GoTo still down?

No, this incident was resolved 2025-09-18 18:49 UTC. For GoTo's live state, see https://down.guide/gotomeeting.

How long did it last?

23h 46m, from 2025-09-17 19:03 UTC to 2025-09-18 18:49 UTC, by the times GoTo posted.

What was affected?

GoTo named VoIP Calls - Deskphones, VoIP Calls - GoTo Connect Web, VoIP Calls - GoTo Connect Mobile, Messaging - Chat and 1 more.

What caused it?

GoTo hasn't published a root cause. If it does, it shows here.

Where does this come from?

GoTo's official status page, https://status.goto.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.