We started checking GoTo Meeting on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when GoTo Meeting reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what GoTo Meeting's own status page declared. Below it, any public chatter we saw about GoTo Meeting and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what GoTo Meeting's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about GoTo Meeting in the last 24 hours, which is not evidence that nothing is wrong.
LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session failures: partial outage, from 15:30 UTC to 18:15 UTC.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is GoTo Meeting's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention GoTo Meeting next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
Confirmation probe16:04 UTC, US-West: their own status feed changing prompted an extra probe. Result: GoTo Meeting answered normally.
Confirmation probe16:03 UTC, Asia-Pacific: their own status feed changing prompted an extra probe. Result: GoTo Meeting answered normally.
Confirmation probe16:03 UTC, US-East: their own status feed changing prompted an extra probe. Result: GoTo Meeting answered normally.
Confirmation probe16:02 UTC, Europe: their own status feed changing prompted an extra probe. Result: GoTo Meeting answered normally.
Confirmation probe15:43 UTC, Asia-Pacific: a new incident on their status page prompted an extra probe. Result: GoTo Meeting answered normally.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
444
US-West
100.00%
335
Europe
100.00%
309
Asia-Pacific
99.47%
187
Their declared record
GoTo Meeting's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Nov 5, 2026, 3:36 PM UTC to Nov 5, 2026, 6:04 PM UTC (2h 28m)resolved
their latest update (Nov 5, 2026, 6:04 PM UTC): 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.
Oct 29, 2026, 2:08 PM UTC to Oct 29, 2026, 11:15 PM UTC (9h 7m)resolved
their latest update (Oct 29, 2026, 11:15 PM UTC): 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.
LogMeIn Rescue and G2ARS v5 - new session failsPartial outage
Oct 28, 2026, 6:38 PM UTC to Oct 28, 2026, 9:22 PM UTC (2h 44m)resolved
their latest update (Oct 28, 2026, 9:22 PM UTC): 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.
GoTo Connect - Inbound calls failing for customers in BrazilPartial outage
Oct 22, 2026, 7:51 PM UTC to Oct 22, 2026, 8:45 PM UTC (54 min)resolved
their latest update (Oct 22, 2026, 8:45 PM UTC): 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.
LogMeIn Pro and Central websitePartial outage
Oct 10, 2026, 4:56 AM UTC to Oct 10, 2026, 6:20 AM UTC (1h 24m)resolved
their latest update (Oct 10, 2026, 6:20 AM UTC): 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.
GoTo Meeting, Webinar or Training - Webcam or screen share issuesPartial outage
Sep 29, 2026, 3:03 PM UTC to Sep 29, 2026, 3:35 PM UTC (32 min)resolved
their latest update (Sep 29, 2026, 3:35 PM UTC): 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.
GoTo Connect - Issue with incoming callsPartial outage
Sep 23, 2026, 12:53 PM UTC to Sep 23, 2026, 4:26 PM UTC (3h 32m)resolved
their latest update (Sep 23, 2026, 4:26 PM UTC): 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.
Pro, Central, GoToAssist Remote Support v5 and LogMeIn Rescue - Elevated error ratesPartial outage
Sep 9, 2026, 3:46 PM UTC to Sep 9, 2026, 4:14 PM UTC (27 min)resolved
their latest update (Sep 9, 2026, 4:14 PM UTC): 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.
Connectivity issuesPartial outage
Sep 8, 2026, 4:55 PM UTC to Sep 8, 2026, 5:48 PM UTC (52 min)resolved
their latest update (Sep 8, 2026, 5:48 PM UTC): 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.
Emails not being delivered to customersPartial outage
Sep 4, 2026, 12:31 PM UTC to Sep 4, 2026, 1:31 PM UTC (1h 1m)resolved
their latest update (Sep 4, 2026, 1:31 PM UTC): 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.
Showing the 10 most recent of 51 incidents GoTo Meeting has declared in the history we hold.
These entries are GoTo Meeting's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
GoTo Meeting's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.