Vendor reports: partial outageResolved · vendor status “resolved”Official status API
GoTo Connect - Contact Center and Call Reports Issue
Reported by GoTo · Communication & Messaging · source last read 3 min ago
- Vendor start
- Jun 19, 2026, 08:33 UTC
- Vendor's clock
- Resolved
- Jun 19, 2026, 13:11 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 4 h 38 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: Contact Center.[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-06-19 13:11 UTC · summary s1, evidence aabe55921ff40b42
Evidence (7)
- E1GoTo reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "GoTo Connect - Contact Center and Call Reports Issue". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-06-19 08:33 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Contact Center. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-06-19 13:11 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Contact Center
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
GoTo is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Jun 19, 2026, 08:33 UTCVendor-reported startVendor time
- Jun 19, 2026, 13:11 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.