- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Grasshopper, Pro/Central, Administration Portal
- Down Index
- 34of 100
What to do
Check whether you use GoTo Grasshopper, Pro/Central, Administration Portal. 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 54m it lasted.
Anything that failed between 2026-01-22 22:19 UTC and 2026-01-23 22:13 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 7
- identified
We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.
provider
- identified
We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.
provider
- identified
We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.
provider
- identified
We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.
provider
- identified
Microsoft is continuing to address the ongoing Microsoft 365 service incident. Microsoft reports improvements in availability, but recovery efforts are still in progress, and some users may continue to experience intermittent impact. For the latest updates, please refer to Microsoft’s status page: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect. We will continue to share updates as more information becomes available.
provider
- monitoring
Microsoft is confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.
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-fc8b22fce0
Is GoTo still down?
No, this incident was resolved 2026-01-23 22:13 UTC. For GoTo's live state, see https://down.guide/gotomeeting.
How long did it last?
23h 54m, from 2026-01-22 22:19 UTC to 2026-01-23 22:13 UTC, by the times GoTo posted.
What was affected?
GoTo named Grasshopper, Pro/Central, Administration Portal.
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.