- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
- Down Index
- 12of 100
What to do
Check whether you use GoTo in eu. 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 2026-02-27 12:29 UTC and 2026-02-27 10:30 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
During the period from 08:04 to 9:10 UTC on February 27, a subset of GoTo Connect customers in Europe may have experienced issues receiving inbound PSTN calls. 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-aed10bca35
Is GoTo still down?
No, this incident was resolved 2026-02-27 10:30 UTC. For GoTo's live state, see https://down.guide/gotomeeting.
How long did it last?
0m, from 2026-02-27 12:29 UTC to 2026-02-27 10:30 UTC, by the times GoTo posted.
What was affected?
GoTo named in eu.
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.