- Level
- confirmed
- Worst impact
- Degraded
- Regions
- latam
What to do
Check whether you use GoTo in latam. 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-09-22 16:21 UTC and 2025-09-22 14:00 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 September 22nd, from 14:15 UTC until 15:40 UTC, a subset of GoTo Connect customers may have experienced issues completing inbound and outbound PSTN calls in Brazil due to a network incident impacting a third-party service provider. Immediately after the root cause of the issue was discovered, it was promptly mitigated. We have confirmed that service has been restored and systems are operational at this time. We are continuing to monitor closely to ensure ongoing stability. We will conduct an internal investigation of this issue and make appropriate improvements to our systems 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-2cd1629994
Is GoTo still down?
No, this incident was resolved 2025-09-22 14:00 UTC. For GoTo's live state, see https://down.guide/gotomeeting.
How long did it last?
0m, from 2025-09-22 16:21 UTC to 2025-09-22 14:00 UTC, by the times GoTo posted.
What was affected?
GoTo named in latam.
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.