Skip to content

Outage tracker / GoTo Meeting

Is GoTo Meeting down?

Short linkrlup.io/down/gotomeeting

I'm having a problem

Vendor reports an incidentWhat GoTo Meeting reports

GoTo Meeting reports an incident on its status page: LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session failures.

Impact: major. Since 2026-11-05 15:36 UTC.

Latest update, 2026-11-05 17:07 UTC: 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 shortly.

GoTo Meeting's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of GoTo Meeting pass from all 4 regions we check.

As of Nov 5, 2026, 6:00 PM UTC, RealUptime's checks of GoTo Meeting passed in all 4 regions that returned a reading.

Front-door checks

our check readinglive · checked Nov 5, 2026, 6:00 PM UTC
US-East1808 msChecks passing
US-West1671 msChecks passing
Europe1228 msChecks passing
Asia-Pacific2048 msChecks passing
their status pagetheir claim, not our reading

GoTo Meeting reports: Minor incident (“Minor Service Outage”)

from GoTo Meeting's own status page, checked Nov 5, 2026, 4:02 PM UTC

GoTo Meeting reports an active incident: LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session failures (partial outage, since Nov 5, 2026, 3:36 PM UTC)

GoTo Meeting's status page reports Minor Service Outage. Our checks of GoTo Meeting currently pass with normal latency. Our checks currently pass from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

GoTo Meeting's own component breakdown, as they publish it

  • Contact CenterOperational
  • Customer EngagementOperational
  • DevicesOperational
  • GoTo Assist Remote Support v5 APIOperational
  • GoTo MeetingOperational
  • GrasshopperOperational
  • MiradoreOperational
  • New purchasesOperational
  • Pro/CentralPartial outage
  • RescuePartial outage
  • VoIP Calls - DeskphonesOperational
  • CC-ProOperational
  • GoTo Assist Remote Support v5Operational
  • GoTo Meeting APIOperational
  • GoTo WebinarOperational
  • GoToMyPCOperational
  • HelpdeskOperational
  • Self ServeOperational
  • VoIP Calls - GoTo Connect WebOperational
  • GoTo Assist Remote support v4Operational
  • GoTo TrainingOperational
  • GoTo Training APIOperational
  • HamachiOperational
  • MDMOperational
  • Trial initiationOperational
  • VoIP Calls - GoTo Connect MobileOperational
  • GoTo Assist Service DeskOperational
  • GoTo Webinar APIOperational
  • OpenVoiceOperational
  • PSTN Calls - InboundOperational
  • Remote ExecutionOperational
  • Subscription ManagementOperational
  • GoTo Assist CorporateOperational
  • GoTo Connect APIOperational
  • GoTo StageOperational
  • PSTN Calls - OutboundOperational
  • ReportingOperational
  • GoTo Assist Service Desk APIOperational
  • Messaging - SMSOperational
  • SupportOperational
  • join.meOperational
  • GoTo Assist Remote Support APIOperational
  • LoginOperational
  • Messaging - ChatOperational
  • Rescue Live ControlOperational
  • Administration PortalOperational
  • GoTo Assist Corporate APIOperational
  • IntegrationsOperational
  • Rescue Live GuideOperational
  • FaxOperational
  • GoTo Developer Center FrontendOperational
  • Rescue Live LensOperational
  • Resolve MCP ServerOperational
  • Admin APIOperational
  • Rescue LensOperational
  • SCIM APIOperational
  • Authentication APIOperational
  • GoTo StatusPageOperational
  • GoTo Resolve Recording and Session APIOperational
  • GoTo Resolve MDM APIOperational
  • Goto Resolve Knowledge Base APIOperational

These are GoTo Meeting's components, named and scored by GoTo Meeting. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is GoTo Meeting's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

GoTo Meeting response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 712ms2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-West
1.8sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Asia-Pacific
2.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 3.4s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 3.4s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5

Check your own site while you wait on GoTo Meeting

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not GoTo Meeting. It cannot diagnose GoTo Meeting's own systems.

Email me when GoTo Meeting reports an incident on its status page, and again when it reports it resolved.

Get an email when GoTo Meeting reports an incident

Email me when GoTo Meeting reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is GoTo Meeting's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1808msstatus code: 200checked: Nov 5, 2026, 5:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach GoTo Meeting normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1671msstatus code: 200checked: Nov 5, 2026, 5:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach GoTo Meeting normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionGoTo Meeting is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionGoTo Meeting is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionGoTo Meeting is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 1228msstatus code: 200checked: Nov 5, 2026, 6:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach GoTo Meeting normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionGoTo Meeting is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2048msstatus code: 200checked: Nov 5, 2026, 5:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach GoTo Meeting normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionGoTo Meeting is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionGoTo Meeting is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using GoTo Meeting, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for GoTo Meeting yet, which is not evidence that nothing is wrong.

Recent probe events

LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session failuresdeclared on their status page2026-11-05
LogMeIn Rescue, Pro, Central, and G2ARS v5 - session failure, 9h 7mdeclared on their status page2026-10-29
LogMeIn Rescue and G2ARS v5 - new session fails, 2h 44mdeclared on their status page2026-10-28
GoTo Connect - Inbound calls failing for customers in Brazil, 54mdeclared on their status page2026-10-22
LogMeIn Pro and Central website, 1h 24mdeclared on their status page2026-10-10
GoTo Meeting, Webinar or Training - Webcam or screen share issues, 32mdeclared on their status page2026-09-29
GoTo Connect - Issue with incoming calls, 3h 32mdeclared on their status page2026-09-23
Pro, Central, GoToAssist Remote Support v5 and LogMeIn Rescue - Elevated error rates, 27mdeclared on their status page2026-09-09

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring GoTo Meeting since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for GoTo Meeting covering any window you pick, with our check readings and GoTo Meeting's own claim at the time, side by side.

Full check history for GoTo Meeting: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

GoTo Meeting uptime by RealUptime's checksLive, from this page's own readings.
[![GoTo Meeting uptime by RealUptime's checks](https://realuptime.io/outages/gotomeeting/badge.svg?days=30)](https://realuptime.io/outages/gotomeeting)
<a href="https://realuptime.io/outages/gotomeeting"><img src="https://realuptime.io/outages/gotomeeting/badge.svg?days=30" alt="GoTo Meeting uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is GoTo Meeting down?", https://realuptime.io/outages/gotomeeting. The readings change with every check, so give the date you read them.

What we check

primary
https://www.goto.com/meeting

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.goto.com

RealUptime is not affiliated with GoTo Meeting; the name identifies what we checked, and nothing here speaks for GoTo Meeting's own team. We send a single web request to GoTo Meeting from 4 regions on our own schedule and time the response. We do not see inside GoTo Meeting's systems, do not use an account or real transaction, and are not the same signal GoTo Meeting's own team has access to. Treat this as one external data point, not a verdict. What we check for GoTo Meeting is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. GoTo Meeting operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1275 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

360LearningADPAIGAPRS.fiAXA