- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Pro/Central, GoToMyPC, join.me
- Down Index
- 33of 100
What to do
Check whether you use GoTo Pro/Central, GoToMyPC, join.me. 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 8h 22m it lasted.
Anything that failed between 2026-07-03 12:03 UTC and 2026-07-03 20:25 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
- investigating
We are actively investigating reports that some Pro and Central customers may be experiencing issues when trying to login. Our engineers are working to identify the issue and will provide another update shortly.
provider
- investigating
Our engineers are still working to identify the source of this issue and will provide another update shortly.
provider
- identified
Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.
provider
- identified
Our engineers have performed a change which will help restore functionality. However, it can take up to 4 hours to take full effect. In the meantime, login can be intermittently working. The team is also looking at other options to get to a faster recovery. We will provide another update shortly.
provider
- identified
Our engineers have performed a change to restore functionality. It is still in progress to take full effect. In the meantime, login can be intermittently working. The team is also still looking at other options to get to a faster recovery. We will provide another update when new information is available.
provider
- identified
Our engineers follow closely the change's progression towards resolution while investigating a faster option. Login can still be intermittently working. We will provide another update soon.
provider
- identified
Our engineers have identified that change did not produce the expected outcome and are now working on an alternate solution. We will provide another update shortly.
provider
- identified
Our engineers are seeing signs of improvements for Join.me, Pro and Central and still working on resolution for GoToMyPC. We will provide another update shortly.
provider
- monitoring
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.
provider
- 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-f9eaef983c
Is GoTo still down?
No, this incident was resolved 2026-07-03 20:25 UTC. For GoTo's live state, see https://down.guide/gotomeeting.
How long did it last?
8h 22m, from 2026-07-03 12:03 UTC to 2026-07-03 20:25 UTC, by the times GoTo posted.
What was affected?
GoTo named Pro/Central, GoToMyPC, join.me.
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.