- Level
- confirmed
- Worst impact
- Degraded
- Components
- GoTo Training
- Down Index
- 8of 100
What to do
Check whether you use GoTo GoTo Training. 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 0m it lasted.
Anything that failed between 2025-11-26 08:37 UTC and 2025-11-26 08:37 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 1
- resolved
On 26th November 2025, between 06:51 UTC and 07:03 UTC, a subset of GoTo App users using GoTo Training may have experienced issues with joining or scheduling training sessions due to a small change in the infrastructure. Immediately the issue was identified, we reverted the change and promptly mitigated any further impact. We have confirmed that service has been restored and systems are operational at this time. 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-d8499454a9
Is GoTo still down?
No, this incident was resolved 2025-11-26 08:37 UTC. For GoTo's live state, see https://down.guide/gotomeeting.
How long did it last?
0m, from 2025-11-26 08:37 UTC to 2025-11-26 08:37 UTC, by the times GoTo posted.
What was affected?
GoTo named GoTo Training.
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.