Operational GoTo status
goto.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread GoTo problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Rescue, Pro/Central
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 22 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “LogMeIn Rescue, Pro, Central, and G2ARS v5 - session failure”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside GoTo's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on GoTo. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on GoTo, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers GoTo may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with GoTo. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
LogMeIn Rescue, Pro, Central, and G2ARS v5 - session failure
major resolved · started · resolved
7 updates
- investigating
We are actively investigating reports that some LogMeIn Rescue, Pro, Central, and G2ARS v5 customers may be experiencing attended session not starting and unattended devices not deployed. Our engineers are working to identify the issue and will provide another update shortly.
- investigating
We are still actively investigating LogMeIn Rescue, Pro, Central, and G2ARS v5 attended session not starting and unattended devices not deployed. LogMeIn Rescue customers can trust the applet as a workaround. Pro, Central and G2ARS v5 customers can continue to retry. Our engineers are working to identify the issue. Another update will follow.
- identified
Our engineers are seeing improvements and are actively working towards a full resolution. We will provide another update shortly.
- monitoring
Our engineers are confirming that all services are functional. We will continue monitoring the situation for an extended period and provide a final update later.
- monitoring
We are investigating a renewed increase in activity related to the recent issue affecting LogMeIn Rescue, Pro, Central, and G2ARS v5. Our engineers have not yet observed a corresponding increase in signing failures and are validating service health and customer impact. We’ll provide another update momentarily.
- monitoring
Our engineers we are confirming that all services are functional once again. We will continue monitoring the situation and provide updates as needed.
- 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.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.