Grasshopper 中断历史

1. 2026年9月4日 UTC 12:31investigating

   我们正在积极调查关于一些客户在接受GoTo电子邮件时可能遇到问题的报道,特别是2FA对GoToMyPC的确认。 我们的工程师正在努力找出问题,不久将提供另一个最新情况.

2. 2026年9月4日 UTC 12:47identified

   我们的工程师已经确定电子邮件传送率正在提高,并正在继续与我们的邮件传送伙伴一起努力解决问题。 我们将很快提供另一个最新情况.

3. 2026年9月4日 UTC 12:59monitoring

   我们的伙伴纠正了这个问题,我们看到电子邮件服务持续稳定。 我们将继续监测局势,并很快提供最后最新情况.

4. 2026年9月4日 UTC 13:31resolved

   我们已经证实,这个问题已经解决,所有系统都100%地运作。 我们将对这一问题进行内部审查,并适当改进我们的系统,以帮助防止或尽量减少今后再次发生.

自动翻译自官方事件更新。

1. 2026年8月27日 UTC 15:55identified

   我们的工程师正在调查一些问题 代号为"救援",GoToAssist v5,Pro和Central, 这会导致间歇性故障 开始会话。 我们将很快提供另一个最新情况.

2. 2026年8月27日 UTC 16:38identified

   我们的工程师继续调查"救援","GoTo Assist v5","Pro"和"Central"报道的代码签名问题. 我们将很快提供另一个最新情况.

3. 2026年8月27日 UTC 17:40monitoring

   我们的工程师看到情况有了改善,我们确认所有服务都运转正常。 我们将继续监测局势,并很快提供最后最新情况.

4. 2026年8月28日 UTC 16:24resolved

   我们已经证实,这个问题已经解决,所有系统都100%地运作。 我们将对这一问题进行内部审查,并适当改进我们的系统,以帮助防止或尽量减少今后再次发生.

自动翻译自官方事件更新。

1. 2026年8月15日 UTC 15:02identified

   我们的工程师意识到一个影响到密码重置的问题,检察官办公室的电子邮件影响到Microsoft365和Outlook用户。 我们已把这个问题确定为供应商问题,我们已同它们一起努力争取解决。 我们将很快提供另一个最新情况.

2. 2026年8月15日 UTC 15:52monitoring

   我们的工程师开始看到内部缓解后恢复的迹象,因为他们继续争取供应商的最终解决。 我们看到,复试是成功的,因此受影响的用户能够接收密码和认证流量。 我们将继续监测局势,并很快提供最后最新情况.

3. 2026年8月15日 UTC 16:33resolved

   我们已经证实,这个问题已经解决,所有系统都100%地运作。 我们将对这一问题进行内部审查,并适当改进我们的系统,以帮助防止或尽量减少今后再次发生.

自动翻译自官方事件更新。

1. 2026年8月4日 UTC 18:11identified

   我们的团队正在研究一个有关WhatsApp运动的问题。 在解决之前,我们暂时取消了以下功能,并为受影响的客户增加了申请通知。 - 客户不能进行宣传活动或对外谈话 - 客户不能登上新的WhatsApp号码 短消息运动不受此影响,继续发挥作用。 我们正与梅塔合作解决这种情况,并将尽快公布最新情况.

2. 2026年8月7日 UTC 19:44identified

   我们仍然在全力解决这个事件 并且正在利用一切手段 和Meta一起把事情升级 局势一有进展,我们将公布另一份最新情况.

3. 2026年8月13日 UTC 17:48identified

   Our engineers have made progress on the escalation with Meta and we are working to re-enable the Whatsapp 1-to-1 template features for all affected customers. WhatsApp campaigns are being addressed separately and remain unavailable for now. We will update this page as soon as we have a restoration estimate for this feature.

4. 2026年8月14日 UTC 15:11monitoring

   Following the re-enablement of 1-to-1 templates yesterday, our engineers have re-enabled WhatAapp campaigns for all affected customers. A reload of the GoTo App will be necessary to access this feature again.

5. 2026年8月14日 UTC 16:09resolved

   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.

自动翻译自官方事件更新。

1. 2026年7月3日 UTC 12:03investigating

   我们正在积极调查关于一些Pro和Central客户在尝试登录时可能遇到问题的报道. 我们的工程师正在努力找出问题,不久将提供另一个最新情况.

2. 2026年7月3日 UTC 12:39investigating

   我们的工程师仍在努力找出这个问题的来源,不久将提供另一个最新情况.

3. 2026年7月3日 UTC 13:23identified

   我们的工程师已经查明了这个问题,目前正在积极努力争取解决。 我们将很快提供另一个最新情况.

4. 2026年7月3日 UTC 14:05identified

   我们的工程师做了一个改变,有助于恢复功能。 然而,要充分发挥作用,需要4小时。 在此期间,登录可以间歇地工作. 团队也在寻找其他选择,以更快地恢复. 我们将很快提供另一个最新情况.

5. 2026年7月3日 UTC 15:08identified

   我们的工程师为了恢复功能做了一个改变。 全面生效的工作仍在进行之中。 在此期间,登录可以间歇地工作. 球队还在寻找其他选择,以更快地恢复. 一旦掌握了新的信息,我们将提供另一个最新情况.

6. 2026年7月3日 UTC 16:02identified

   我们的工程师们密切注视着这个变化走向解决,同时调查一个更快的选择. 登录仍然可以间歇地工作. 我们将很快提供另一个最新情况.

7. 2026年7月3日 UTC 18:21identified

   我们的工程师已经确定,这种变化没有产生预期的结果,目前正在设法找到另一种解决办法。 我们将很快提供另一个最新情况.

8. 2026年7月3日 UTC 19:21identified

   我们的工程师们看到JUING.me、Pro和Central的改进迹象,仍在为GOTOMYPC进行解析。 我们将很快提供另一个最新情况.

9. 2026年7月3日 UTC 19:55monitoring

   我们的工程师已经纠正了这个问题,我们正在确认所有服务都运转正常。 我们将继续监测局势并提供最后最新情况.

10. 2026年7月3日 UTC 20:25resolved

    我们已经证实,这个问题已经解决,所有系统都100%地运作。 我们将对这一问题进行内部审查,并适当改进我们的系统,以帮助防止或尽量减少今后再次发生.

自动翻译自官方事件更新。

1. 2026年7月2日 UTC 11:49investigating

   我们正积极调查关于GoTo Connect客户的子公司可能遇到出入境电话问题的报道。 我们的工程师正在努力找出问题,不久将提供另一个最新情况.

2. 2026年7月2日 UTC 11:54identified

   我们的工程师已经查明了这个问题,目前正在积极努力争取解决。 我们将很快提供另一个最新情况.

3. 2026年7月2日 UTC 13:43identified

   我们的工程师继续调查这个问题,并正在积极努力确定解决问题的最佳途径。 我们将很快提供另一个最新情况.

4. 2026年7月2日 UTC 14:12identified

   我们的工程师目前正在制定一项计划来缓解这些问题并继续努力解决问题。 我们将很快提供另一个最新情况.

5. 2026年7月2日 UTC 15:14identified

   我们的工程师们正在继续解决这个问题。 我们将很快提供另一个最新情况.

6. 2026年7月2日 UTC 16:06identified

   我们的工程师正在继续调查导致已知问题的几个根本原因。 这包括查明和遵循模式,以及了解客户的全面影响。 目前,调查仍在进行。 我们不久将提供补充最新情况.

7. 2026年7月2日 UTC 16:36monitoring

   我们的工程师已经实施了一项固定措施,解决了所报道的进出呼叫问题,我们现在正在监测持续稳定。 我们不久将提供最后最新情况.

8. 2026年7月2日 UTC 18:27resolved

   我们的工程师现在看到所有服务都正常运转。 我们将对这一问题进行内部审查并作适当改进,以确保这一问题不再出现.

自动翻译自官方事件更新。

1. 2026年7月1日 UTC 09:43investigating

   我们正积极调查关于GoTo Connect客户的子公司可能遇到出入境电话问题的报道。 我们的工程师正在努力找出问题,不久将提供另一个最新情况.

2. 2026年7月1日 UTC 10:08identified

   我们的工程师已经查明了这个问题,目前正在积极努力争取解决。 我们将很快提供另一个最新情况.

3. 2026年7月1日 UTC 10:40monitoring

   我们的工程师已经纠正了这个问题,我们正在确认所有服务都运转正常。 我们将继续监测局势并很快提供最后最新情况.

4. 2026年7月1日 UTC 10:43monitoring

   我们正在继续监测任何其他问题.

5. 2026年7月1日 UTC 10:50resolved

   我们已经证实,这个问题已经解决,所有系统都100%地运作。 我们将对这一问题进行内部审查,并适当改进我们的系统,以帮助防止或尽量减少今后再次发生.

自动翻译自官方事件更新。

1. 2026年6月19日 UTC 08:33investigating

   We are actively investigating reports of an impact affecting GoTo Connect, including Call History, Virtual Receptionist Reporting, Voicemail Deletion, and Call-Report Ingestion. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年6月19日 UTC 08:38identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年6月19日 UTC 10:08identified

   Our engineers continue to investigate the issue. We will provide another update as soon as it is available.

4. 2026年6月19日 UTC 12:39monitoring

   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.

5. 2026年6月19日 UTC 13:11resolved

   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.

1. 2026年5月28日 UTC 14:17investigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing authentication issues accessing the GoTo app or GoTo Admin or Analytics portals. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年5月28日 UTC 14:28identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年5月28日 UTC 14:49monitoring

   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.

4. 2026年5月28日 UTC 14:57resolved

   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.

1. 2026年5月27日 UTC 15:17investigating

   We are actively investigating an issue with Logmein Rescue may have issues starting or joining remote sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年5月27日 UTC 15:45identified

   Our engineers have identified the issue and are now actively working towards a resolution. We are seeing gradual improvement and continuing to monitor the progress. We will provide another update shortly.

3. 2026年5月27日 UTC 15:48monitoring

   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.

4. 2026年5月27日 UTC 15:57resolved

   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.

1. 2026年5月13日 UTC 18:58investigating

   We are actively investigating reports that some LogMeIn Rescue and Central customers may be experiencing issues downloading the applet to start or join remote sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年5月13日 UTC 19:22identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年5月13日 UTC 20:04identified

   Our engineers are continuing to work on this issue and continue to work towards a resolution. We will provide another update shortly.

4. 2026年5月13日 UTC 21:13identified

   Our engineers are continuing to work on isolating the source of this issue. Due to its intermittent nature, trying again can allow to establish a proper connection. We will provide another update shortly.

5. 2026年5月13日 UTC 22:28monitoring

   A potential fix was applied to resolve the issue, and we are continuing to monitor for stability. We will continue monitoring the situation and provide a final update shortly.

6. 2026年5月13日 UTC 22:40identified

   Our engineers are still seeing some intermittent issues after the fix and are continuing to investigate those. We will provide a status update once we have further information. We will provide another update shortly.

7. 2026年5月14日 UTC 00:37identified

   We are continuing to work towards a resolution to ensure stability in starting and joining sessions. We will provide another update shortly.

8. 2026年5月14日 UTC 01:12identified

   Our engineers have identified a plan to get back the system to stustained stability and are starting to execute on it. We will provide another update shortly.

9. 2026年5月14日 UTC 02:03identified

   Our engineers are executing on the established plan to get back the system to prolonged stability We will provide another update shortly.

10. 2026年5月14日 UTC 02:12monitoring

    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.

11. 2026年5月14日 UTC 02:22resolved

    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.

1. 2026年5月8日 UTC 01:22investigating

   We are actively investigating reports that some Grasshopper customers may be experiencing login issues on apps. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年5月8日 UTC 02:09investigating

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年5月8日 UTC 04:10monitoring

   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.

4. 2026年5月8日 UTC 17:11resolved

   We have confirmed that the issue has been resolved and all systems are 100% operational at this time. We will conduct an internal investigation of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 2026年5月7日 UTC 18:31identified

   Our engineers have identified the issue with call recordings and transcripts availability delay and are now actively working towards a resolution. We will provide another update shortly.

2. 2026年5月8日 UTC 01:54monitoring

   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.

3. 2026年5月8日 UTC 02:01resolved

   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.

1. 2026年5月6日 UTC 16:55investigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing issue opening the app. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年5月6日 UTC 16:57identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年5月6日 UTC 17:06monitoring

   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.

4. 2026年5月6日 UTC 17:23resolved

   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.

1. 2026年4月20日 UTC 14:14investigating

   We are actively investigating reports that some GoTo Meeting and GoTo Admin customers may be experiencing timeouts when performing operations in GoTo Admin and GoTo Meeting components. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年4月20日 UTC 14:34identified

   Our engineers have identified the issue and are actively working to correct the underlying cause. This issue appears to have impacted functionality with GoTo Admin, GoTo Connect, Contact Center, Analytics, Resolve, and other related services. We will provide another update shortly.

3. 2026年4月20日 UTC 14:55identified

   This issue affects authentication to the various GoTo applications, which also affects Resolve, Pro/Central, in addition to GoTo Admin, Connect and Meetings. We will provide another update shortly.

4. 2026年4月20日 UTC 15:12identified

   Our engineers are seeing signs of recovery for login to our applications. Our team is still engaged in ensuring prolonged stability of the applications. We will provide another update shortly.

5. 2026年4月20日 UTC 15:16monitoring

   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.

6. 2026年4月20日 UTC 15:23resolved

   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.

1. 2026年4月15日 UTC 21:08investigating

   We are actively investigating reports that some GoTo Connect VoIP Phones Calls customers may be experiencing intermittent issues completing inbound calls. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年4月15日 UTC 21:15identified

   Our engineers have identified the issue as being caused by an ongoing incident with one of our underlying third-party service providers who are actively working towards a resolution. We will provide another update as soon as they become available.

3. 2026年4月15日 UTC 21:38monitoring

   Our underlying third-party service provider has corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 2026年4月15日 UTC 21:41resolved

   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.

1. 2026年4月6日 UTC 12:58investigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing issues with call quality for GoToConnect Web, Desktop and Mobile. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年4月6日 UTC 13:16identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年4月6日 UTC 13:43monitoring

   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.

4. 2026年4月6日 UTC 13:47resolved

   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.

1. 2026年3月25日 UTC 16:08investigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing audio issues on calls Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年3月25日 UTC 16:15identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年3月25日 UTC 16:20monitoring

   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.

4. 2026年3月25日 UTC 16:35resolved

   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.

1. 2026年3月18日 UTC 15:37investigating

   We are actively investigating reports that some GoTo Webinar customers may be experiencing an issue starting sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年3月18日 UTC 15:51identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 2026年3月18日 UTC 15:58identified

   We are seeing improvements in GoTo Webinar, Training and Meeting as mitigating actions are being deployed. We will provide another update shortly.

4. 2026年3月18日 UTC 16:04monitoring

   Our engineers have corrected the issue and we are monitoring recovery across all services which were affected. We will continue monitoring the situation and provide a final update shortly.

5. 2026年3月18日 UTC 18:19resolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational.

1. 2026年2月27日 UTC 15:52investigating

   We are actively investigating reports that some Contact Center – Call Queue customers may be experiencing issues with queue calls not being distributed to Contact Center agents. Our engineers are working to identify the issue and will provide another update shortly.

2. 2026年2月27日 UTC 17:20investigating

   We are continuing to investigate the reports of call queue distribution issues. Our engineers are still fully engaged to identify the source of issue and will provide another update shortly.

3. 2026年2月27日 UTC 18:00identified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

4. 2026年2月27日 UTC 18:42monitoring

   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.

5. 2026年2月27日 UTC 19:15resolved

   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.