Google Workspace 中断历史

1. 2026年8月28日 UTC 19:25resolved

   ** 摘要:** Google Chat用户正在经历一个问题,即他们收到新消息的通知,但实际消息无法出现在他们的聊天应用程序中,除非用户刷新他们的视图. ** 说明:** Google Chat Friday 2026-08-28 10: 我们的工程组已经调查了这一问题,目前正在努力减轻这一问题。 我们将在星期五2026-08-28 14:15之前提供更多资料,并提供最新详情。 我们向所有受到干扰影响的人道歉。 ** 客户症状:** 用户正在经历一个问题,即他们收到新消息的通知,但除非用户刷新其视图,否则实际消息无法出现在聊天应用程序中 ** 工作:** 用户可以刷新到查看新信件

2. 2026年8月28日 UTC 20:55resolved

   ** 概要** Google Chat用户经历了一个问题,他们收到了新消息的通知,但实际消息未能出现在他们的聊天应用程序中,除非用户刷新了他们的视图. ** 说明** Google Chat的问题已经解决,截至2026-08-28 13:45 PDT 周五,所有受影响的用户. 从初步分析来看,这一问题是最近为减轻影响而回滚而发生的。 我们感谢你在我们努力解决这一问题时的耐心。 ** 客户症状** 用户正在经历一个问题,即他们收到了新消息的通知,但除非用户刷新了他们的视图,否则实际消息无法出现在他们的聊天应用程序中. ** 工作** 这个问题没有得到解决.

3. 2026年9月4日 UTC 03:43resolved

   □事件报告 □ 总结 2026年8月28日星期五,10:50 US/Pacific和13:34 US/Pacific时间相隔2小时44分,Google Chat用户在网络,桌面,移动应用程序等活跃对话流中,遭遇了实时接收消息的延迟. 虽然用户继续收到新消息的通知,但消息内容在主动对话流中不会自动渲染,直到用户手动刷新应用程序或发送回覆消息. 对我们宝贵的谷歌工作空间客户 我们对你经历的服务中断深表遗憾 我们正在立即采取果断行动,以解决这一问题,并针对未来事件加强我们的系统。 □ 根源 这一事件是在全球数据库计划推出期间引发的。 一个不相容的数据库计划更改导致信件发送开始失败所需的数据库写入. 具体地说,一种旨在确保初级存储和实时信息发送高度一致的同步计划机制遇到了罕见的种族条件错误。 这导致后端消息发送器试图针对一个未准备好的策略状态来写,导致写入失败. 由于直播消息的发送在将事件推向用户屏幕之前,积极依赖这些写作成功完成,因此故障导致来信体验同步延迟. 单独的推取通知服务和核心消息存储独立运行且未受影响,这就是为什么用户仍然收到新消息的提醒,而活动的对话流则出现延迟. □ 补救和预防 通过自动后端提醒发送出错率以及相应的客户报告,发现了这一问题。 Google Engine启动了并行的工作流来恢复服务. * 在12:44的美国/太平洋,Google Engineering直接减轻了问题的根源,消除了现场信息发送对失败的数据库书写的依赖。 这使得新收到的信件可以绕过失败的写入,并立即恢复正常的实时发送到用户屏幕. * 在下午1:00美国/太平洋,Engineering停止并恢复了数据库计划的改变,使其恢复到先前核实的稳定版本,恢复了数据库的完全兼容性。 * 至13:34 US/Pacific,由于已排队处理信件,所有客户域的实时信件同步延迟恢复到0%. 工程证实,在零信息损失的情况下,全面恢复了服务健康. 为了防止这种情况再次发生,我们正在采取以下预防行动: *** 内部固化探测器:** 加强自动化验证和核查,以涵盖生产前和内部推出阶段的这一具体故障情况。 其目的是在将来任何客户流量都可能受到影响之前,在内部捕捉和减轻计划不兼容和同步边缘的情况。 * ** 反对种族条件:** 实施建筑改造,使计划同步和消息传递架构适应种族条件. 这样做的目的是确保背景计划和配置同步不一致不能干扰实时信息发送. □ 关于影响的详细说明 事故撞击窗口发生于2026年8月28日星期五10:50美国/太平洋和13:34美国/太平洋之间. 这个问题在全球适用于所有谷歌聊天环境. ** 谷歌聊天:** * ** 延迟电文渲染:** 新消息没有自动出现在活动对话流中 。 用户需要手动刷新客户端或发送新消息/反应来迫使流同步. * ** 总计读取状态和收件箱排序:** 背景动作,如更新未读徽章和将活动空间移到收件箱上方,经历了沉重的内部出错率并被大量延迟给用户. * ** 搜索索引延迟:** 断电窗口期间发出的新信息在索引管道中停滞,出现无法搜索的延误. ** 范围排除:** * ** 无数据损失:** 客户数据从未丢失或泄露。 事件窗口期间发送的所有信息都安全地保存在主存储室,一旦积压处理完毕,就成功传送到对话流程.

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

1. 2026年8月19日 UTC 03:57resolved

   ** 概要** 一些客户在使用Google Drive时可能会经历缓慢. ** 说明** 2026-08-18 16:58 PDT. 我们的工程小组目前正在研究潜在的解决办法,同时继续调查全部根源。 我们将在2026-08-18 22:00之前提供最新资料,说明最新详情。 我们向所有受到干扰影响的人道歉。 ** 现象** 受影响的客户在使用Google Drive时可能会经历缓慢. ** 工作** 此时无.

2. 2026年8月19日 UTC 04:59resolved

   ** 概要** 澳大利亚和新西兰的多位客户在使用Google Drive时可能会出现缓慢或出错. ** 说明** 2026-08-18 16:58 PDT. 我们的工程小组目前正在研究潜在的解决办法,同时继续调查全部根源。 我们将在2026-08-19:30的星期三之前提供最新资料,说明最新的详情。 ** 现象** 澳大利亚和新西兰受到影响的客户在使用Google Drive时可能会遇到缓慢或出错. 一些客户还可能在短时间内观察到有502个Drive无法访问的错误. ** 工作** 此时无.

3. 2026年8月19日 UTC 06:49resolved

   ** 概要** 澳大利亚和新西兰的多位客户在访问Google Drive时可能会经历缓慢或出错. ** 说明** 2026-08-18 16:58 PDT. 我们的工程队已经查明问题的根源,并正在积极制定减缓战略。 没有完全解决的ETA. 我们将在2026-08-19:30之前提供最新资料,说明最新详情。 ** 现象** 澳大利亚和新西兰受到影响的客户可能遇到缓慢或502个错误,部分用户短暂无法访问Drive. ** 工作** 此时无.

4. 2026年8月19日 UTC 07:59resolved

   ** 概要** 澳大利亚和新西兰的多位客户在访问Google Drive时可能会经历缓慢或出错. ** 说明** 2026-08-18 16:58 PDT. 我们的工程队已经查明问题的根源,并正在积极制定减缓战略。 没有完全解决的ETA. 我们将在2026-08-19:00的星期三前提供最新资料,说明最新详情。 ** 现象** 澳大利亚和新西兰受到影响的客户可能遇到缓慢或502个错误,部分用户短暂无法访问Drive. ** 工作** 此时无.

5. 2026年8月19日 UTC 08:54resolved

   ** 概要** 澳大利亚和新西兰的多位客户在访问Google Drive时可能会经历缓慢或出错. ** 说明** 2026-08-18 16:58 PDT. 我们的工程队正在积极制定减缓战略。 没有完全解决的ETA. 我们将在2026-08-19:00的星期三前提供最新消息,说明最新详情。 ** 现象** 澳大利亚和新西兰受到影响的客户可能遇到缓慢或502个错误,部分用户短暂无法访问Drive. ** 工作** 此时无.

6. 2026年8月19日 UTC 09:54resolved

   ** 概要** 澳大利亚和新西兰的多位客户在访问Google Drive时可能会经历缓慢或出错. ** 说明** 2026-08-18 16:58 PDT. 我们的工程队正在积极制定减缓战略。 没有完全解决的ETA. 我们将在2026-08-19 04:30之前提供最新资料,说明最新详情。 ** 现象** 澳大利亚和新西兰受到影响的客户可能遇到缓慢或502个错误,部分用户短暂无法访问Drive. ** 工作** 此时无.

7. 2026年8月19日 UTC 11:26resolved

   ** 概要** 澳大利亚和新西兰的多位客户在访问Google Drive时可能会经历缓慢或出错. ** 说明** 2026-08-18 16:58 PDT. 我们的工程队正在积极制定减缓战略。 没有完全解决的ETA. 我们将在2026-08-19:00的星期三之前提供最新资料,说明最新详情。 ** 现象** 澳大利亚和新西兰受到影响的客户可能遇到缓慢或502个错误,部分用户短暂无法访问Drive. ** 工作** 此时无.

8. 2026年8月19日 UTC 13:05resolved

   ** 概要** 澳大利亚和新西兰的多位客户在访问Google Drive时可能经历了缓慢或出错. ** 说明** Google Drive的问题已经解决,截至2026-08-19 05:40 PDT星期三,所有受影响的客户都得到了解决. 我们的工程队确定速度缓慢,是因为我们区域基础设施内部存在局部能力和线路问题。 为了恢复服务,我们实施了一个缓解网络拥堵的固定方案,并加速了受影响地区计划中的基础设施升级,以确保正常的性能水平。 我们感谢你在我们努力解决这一问题时的耐心。 ** 现象** 澳大利亚和新西兰受影响的客户可能经历了缓慢或502个出错,部分用户短暂无法访问Drive. ** 工作** 这个问题现已得到缓解

9. 2026年8月20日 UTC 20:00resolved

   # 初步事件报告 我们为这次事件对你的生意造成的干扰 表示诚挚的歉意 我们知道你有多依赖谷歌工作空间, 我们很遗憾这对你生产力的影响。 我们正在努力解决根源问题,防止今后发生这种情况。 请注意,这一信息是根据我们公布时的最好知识提供的,随着我们调查的继续进行,可能会有所改变。 我们调查完成后,将公布一份包含预防行动的最后事件报告。 如果您在下文所列项目之外曾遇到过影响,请使用帮助文章[**https://support.google.com/a/sanswer/1047213**](https://support.google.com/a/sanswer/1047213)联系Google工作空间支助。 □ 发行日期/时间(全美国/太平洋) 事发时间:2026年8月18日 16:58 事件结束:2026年8月19日 05:40 会期:12小时42分 □ 总结 2026年8月18日,从16:58到8月19日,2026年05:40美国/太平洋,Drive客户在澳大利亚,菲律宾和新西兰经历了性能退化和缓慢. 在此期间,用户也经历了502个错误. 其他谷歌工作空间服务没有受到影响. □ 初步根源 Google利用多层次的全球负荷平衡和网络路由架构来高效地服务于交通. 为确保公平使用和防止拥堵,对带宽分配的管理是将流量分配给特定的下游服务。 交通归属的错位导致带宽使用被错误地归因于前端网络负载平衡层本身,而不是Drive服务. 导致影响客户的事件顺序如下: * 来自区域负载平衡等级的交通不正确归因于负载平衡基础设施,而不是驱动器服务。 * 不相干流量造成本区域负载平衡基础设施造成的网络带宽使用超过其配额。 * 网络带宽管理系统对这种流量施加了节流,以强制实行配额制,造成严重的网络拥堵,影响到本区域的驱动交通。 * 这种拥堵导致受影响地区用户进入Drive的延迟、缓慢和出错率增加。 □ 补救 Google工程师通过自动监控和大量客户支持案例的涌入来提醒人们注意这个问题,2026年8月18日17:21美国/太平洋开始接触事件反应小组. 工程师们最初试图通过将区域前端交通排入另一个地理位置来缓解拥堵,但事实证明这样做是无效的并被恢复. 团队随后通过将区域交通迁移到升级后的内部网络通路架构来缓解了这一问题,这为Drive正确设定了交通归属. 一旦100%的区域交通被迁移到升级的网络架构,正常业务就完全恢复。 □ 影响描述 在2026年8月18日16:58 US/Pacific和2026年8月19日05:40 US/Pacific之间,Google Drive在澳大利亚,菲律宾和新西兰的用户经历了严重的耐久,性能退化和502出错. 在这个大约12小时和42分钟的窗口中,受影响的客户在试图通过编辑器(如[docs.google.com](http://docs.google.com))访问Google Drive或上市文件时可能观察到显著的慢或出错,初始负载时间被大大地延迟. 至2026年8月19日05:40US/Pacific上,该问题得到全面缓解,恢复正常服务.

10. 2026年8月24日 UTC 16:31resolved

    # 事件报告 □ 总结 2026年8月18日星期二16:58美国/太平洋发生影响Google Drive的事件,持续时间为12小时42分. 位于澳大利亚、菲律宾和新西兰的客户在访问Google Drive时遭遇了严重的延迟、零星的装载故障和出错。 对我们宝贵的谷歌工作空间客户 我们对你经历的服务中断深表遗憾 我们正在立即采取果断行动,以解决这一问题,并针对未来事件加强我们的系统。 其他谷歌工作空间服务没有受到影响. □ 根源 Google利用多层次的全球负荷平衡和网络路由架构来高效地服务于交通. 为确保公平使用和防止拥堵,对带宽分配的管理是将流量分配给特定的下游服务。 交通归属的错位导致带宽使用被错误地归因于前端网络负载平衡层本身,而不是Drive服务. 导致影响客户的事件顺序如下: * 来自区域负载平衡等级的交通不正确归因于负载平衡基础设施,而不是驱动器服务。 * 不相干流量造成本区域负载平衡基础设施造成的网络带宽使用超过其配额。 * 网络带宽管理系统对这种流量施加了节流,以强制实行配额制,造成严重的网络拥堵,影响到本区域的驱动交通。 * 这种拥堵导致受影响地区用户进入Drive的延迟、缓慢和出错率增加。 □ 补救和预防 Google工程师通过自动监控和大量涌入的客户支持案件来提醒这个问题,最初的事件反应小组于2026年8月18日17:21开始介入. 工程师们最初试图通过将区域前端交通排入另一个地理位置来缓解拥堵,但事实证明这样做是无效的并被恢复. 团队随后通过将区域交通迁移到升级后的内部网络通路架构来缓解了这一问题,这为Drive正确设定了交通归属. 正常运营在5:40完全恢复,一旦100%的区域交通被迁移到升级的网络架构. 为防止再次出现这一问题,我们的工程小组正在采取下列结构性预防行动: * ** 反应网络议定书:** 我们正在加快将所有区域前端交通完全迁移到更新的、具有弹性的网络线路协议,以确保在所有拥堵情况下准确的带宽归属。 * ** 授权根源补救:** 我们正在处理造成整个舰队不正确的授权和分析类似案件以确保不再发生的根本机制。 □ 关于影响的详细说明 从2026年8月18日16:58到2026年8月19日05:40 US/Pacific持续12小时42分,Google Drive在澳大利亚,菲律宾和新西兰的用户都经历了严重的性能退化,包括高潜伏度和错误通过编辑器访问Drive或上市文件. 8月19日05:40美国/太平洋全面恢复服务. ** 谷歌驱动器:** * Elevated Latency:用户在加载 Drive 接口或访问文件时经历了极度缓慢,初始数据检索时间被严重延迟. * 装入故障和出错:许多用户请求超时出错或回回HTTP 502出错,因为主动性的网络减速降下连接. ** 范围排除:** * 来自澳大利亚、菲律宾和新西兰以外地区的用户使用Google Drive, * 在事件窗口期间,不依赖这一具体路径的其他Google工作空间应用保持稳定.

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

1. 2026年8月18日 UTC 19:35resolved

   ** 摘要:** 调查课堂新主页的访问问题。 ** 说明:** 校对:Soup 我们的工程小组目前正在研究潜在的解决办法,同时继续调查全部根源。 我们将在2026-08-18:00之前提供最新资料。 我们向所有受到干扰影响的人道歉。 ** 现象:** 校对:Soup ** 工作:** 用户仍应能够从界面的左手相框导航到其他视图.

2. 2026年8月18日 UTC 20:00resolved

   ** 摘要:** 校对:Soup ** 说明:** 我们的工程组目前正在开展缓解工作。 缓解工作预计于2026-08-18 14:00 PDT星期二完成. 我们将在2026-08-18 14:15之前提供更多信息。 ** 现象:** 校对:Soup ** 工作:** 用户仍应能够从界面的左手相框导航到其他视图.

3. 2026年8月18日 UTC 20:27resolved

   ** 摘要:** 减少工作空间管理员在课堂主页上的访问问题。 ** 说明:** 我们的工程已经查明了原因,目前正在开展缓解工作。 减缓工作预计需要几个小时。 我们将在2026-08-19 8:00之前提供更多信息。 ** 现象:** 工作空间管理员在访问教室网页主页时可能遇到许可错误。 其余教室功能没有受到影响。 教室移动App和教室API不受此问题的影响. ** 工作:** 所有其他页面都不受影响,管理员可以使用界面上左手相框导航到其他页面. 工作空间管理员仍然可以不设任何问题地创建课程. 工作空间管理员也可通过前往https://classroom.google.com/h/tv查看他们正在学习的课程

4. 2026年8月18日 UTC 23:02resolved

   ** 概要** [缓解] 课堂网页上的工作空间管理员的访问问题。 ** 说明** 从2026-08-18 15:30起,所有受影响用户的课堂问题已经得到解决。 从初步分析来看,这个问题是由于最近发生的一次变化引起的,这一变化造成了许可不匹配,因此我们的工程小组已经推出固定装置来减轻影响。 我们感谢你在我们努力解决这一问题时的耐心。 ** 现象** 工作空间管理员在访问教室网页主页时可能遇到许可错误。 其余的教室功能没有受到影响。 课室移动App和课室API没有受到这个问题的影响. ** 工作** 没有问题解决

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

1. 2026年6月30日 UTC 11:56resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 05:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** None at this time.

2. 2026年6月30日 UTC 12:17resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** None at this time.

3. 2026年6月30日 UTC 12:28resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** Customers can continue to use the portal to add comments / notes.

4. 2026年6月30日 UTC 13:28resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** Customers can continue to use the portal to add comments / notes.

5. 2026年6月30日 UTC 14:06resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** Customers can continue to use the portal to add comments / notes.

6. 2026年6月30日 UTC 14:51resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Tuesday, 2026-06-30 08:45 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

7. 2026年6月30日 UTC 15:48resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Tuesday, 2026-06-30 09:45 PDT. We will provide more information by Tuesday, 2026-06-30 10:00 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

8. 2026年6月30日 UTC 16:36resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineering teams have shifted focus to replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. While there is currently no specific ETA for the email replay to finish, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 11:00 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

9. 2026年6月30日 UTC 17:53resolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 12:15 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

10. 2026年6月30日 UTC 19:03resolved

    **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 17:00 PDT. **Symptoms** Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

11. 2026年7月1日 UTC 00:44resolved

    **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 21:30 PDT. **Symptoms** Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

12. 2026年7月1日 UTC 04:58resolved

    **Title** [Resolved] Inbound emails from customers to Google Support were experiencing issues. **Description** The issue with inbound emails to Google Cloud Support has been resolved for all affected customers as of Tuesday, 2026-06-30 20:45 PDT. From preliminary analysis, the engineering team identified a recent change which was preventing incoming emails from being processed. We have successfully rolled back the change to mitigate the impact. Backlog processing of all the affected emails is now complete. We thank you for your patience while we worked on resolving the issue. **Symptoms** Inbound emails from customers to Google Support were experiencing issues. Case creation and updates continued to work without any issues. **Workaround** None as the issue is resolved.

1. 2026年6月22日 UTC 22:28resolved

   **Title** Some consumer Google Voice users are experiencing account suspensions. **Description** We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified the root cause and is actively working to mitigate the issue. We will provide an update by Monday, 2026-06-22 17:30 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Some consumer Google Voice users are experiencing account suspensions

2. 2026年6月23日 UTC 00:29resolved

   **Title** Some consumer Google Voice users are experiencing account suspensions. **Description** We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified a mitigation strategy and is actively working on mitigation. We do not have an ETA for mitigation at this time. We will provide an update by Monday, 2026-06-22 22:30 PDT with current details. **Symptoms** Some consumer Google Voice users are experiencing account suspensions **Workaround** None at this time.

3. 2026年6月23日 UTC 01:08resolved

   **Title** Some consumer Google Voice users experienced account suspensions. **Description** The issue with Google Voice has been resolved for all affected users as of Monday, 2026-06-22 17:46 PDT Our engineers have mitigated the issue by rolling back to a previous version and reinstating suspended accounts. We thank you for your patience while we worked on resolving the issue. **Symptoms** Some consumer Google Voice users experienced account suspensions **Workaround** The issue is now mitigated.

1. 2026年6月10日 UTC 12:40resolved

   **Title** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 06:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Workaround** None at this time.

2. 2026年6月10日 UTC 13:21resolved

   **Title** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Workaround** None at this time.

3. 2026年6月10日 UTC 15:10resolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue and identify a mitigation strategy. We will provide an update by Wednesday, 2026-06-10 09:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong” errors.: * Gemini app in Workspace includes the following platforms; * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

4. 2026年6月10日 UTC 16:24resolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has identified a mitigation which is currently in progress. We do not have an ETA for mitigation at this time. We will provide an update by Wednesday, 2026-06-10 12:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

5. 2026年6月10日 UTC 18:37resolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has applied mitigations to reduce impact and continues to investigate the root cause. We are seeing signs of recovery and will continue to monitor progress. We will provide an update by Wednesday, 2026-06-10 14:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

6. 2026年6月10日 UTC 20:19resolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has applied mitigations to reduce impact and confirmed the majority of users are no longer observing impact as of Wednesday, 2026-06-10 10:30 PDT. We will continue to monitor the service for stability. We will provide an update by Wednesday, 2026-06-10 20:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

7. 2026年6月11日 UTC 01:07resolved

   **Title** Gemini App in Workspace users were experiencing “Something Went Wrong” errors. **Description** The issue with Gemini has been resolved for all the affected users as of Wednesday, 2026-06-10 10:30 US/Pacific. From preliminary analysis, the issue was triggered by a performance issue in our backend database which impacted the retrieval of Gemini App tools catalog. Our engineers mitigated the issue by optimizing the load distribution across our backend database fleet. We thank you for your patience while we worked on resolving the issue. **Symptoms** Affected users may have seen "Something went wrong" errors (codes 1099, 1076) when prompting Gemini while using the following services. Gemini App in Workspace includes the following platforms: - Web, MacOS, iOS and Android - Gemini in Chrome **Workaround** None as the issue is now resolved.

8. 2026年6月12日 UTC 11:14resolved

   # Preliminary Incident Report We apologize for the inconvenience this service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced an impact outside of what is listed below, please reach out to Google Workspace Support using the help article [https://support.google.com/a/answer/1047213](https://support.google.com/a/answer/1047213). ## Date/Time of the Issue (All time US/Pacific) Incident Start: 10 June 2026 03:20 Incident End: 10 June 2026 10:25 Duration: 7 hours, 5 minutes ## Summary On Wednesday, 10 June 2026 03:20 US/Pacific, an incident occurred affecting the availability of Gemini services across all surfaces, including web, mobile (iOS and Android), and integrations within Google Chrome. The incident resulted in an elevated error rate for 7 hours and 5 minutes. ## Preliminary Root Cause The disruption was caused by extreme read contention within the foundational database service that manages tool deployment metadata. The primary cause was back-pressure on specific database replicas that experienced high loads. The issue was made worse because of an index design issue within the database where a column used for tracking deployment expirations contained a high volume of rows with a similar fixed value. This resulted in a condition where traffic was concentrated on a very small number of database instances, overwhelming them. Additionally, the service utilized an in-memory cache with a short Time To Live (TTL) of only one minute, requiring frequent database refreshes. The failure sequence was as follows: 1. **Technical Trigger:** The database service became overloaded, causing back-pressure on specific replicas. 2. **Systemic Effect:** An application level caching layer configuration is set to a short 1-minute expiration window for deployed tools. This short window, combined with an indexing anomaly where specific metadata fields containing empty values were clustered on a single database partition. The failed DB queries resulted in failure to populate application level cache. 3. **Contention and Latency:** As request volume increased, the internal tool management service experienced >10x surge in database calls because the cache hit rate dropped significantly. 4. **Failure State:** The underlying storage layer reached its transaction limits, with database response success rates dropping as low as 10% on the affected partitions. ## Remediation The issue was detected by internal real-time monitoring alerts indicating high processing error rates. Engineering teams performed several targeted actions to restore the service: * **Throttling:** Applied rate limiting to the most affected database instances to allow internal caches to recover. * **Index Redistribution:** Gradually redistributed fixed index values in the database to random values in a specific range, effectively spreading the load across multiple instances. * **Cache Policy Update:** Deployed a configuration change to increase the in-memory cache Time To Live (TTL) from 1 minute to 20 minutes, significantly reducing database load. * **Deadline Adjustment:** Shortened the Remote Procedure Call (RPC) deadlines for database queries to prevent request pile-ups during periods of high latency. ## Description of Impact The impact window occurred between 03:20 US/Pacific and 10:25 US/Pacific on 10 June 2026. **Gemini App (Web and Mobile):** * Users experienced a 50% error rate when attempting to send prompts, receiving "Something went wrong" messages. The issue affected both consumer accounts and enterprise Google Workspace customers . **Integrations:** * **Google Chrome Integration:** The Gemini Side Panel and integrated conversational features encountered persistent timeouts.

9. 2026年6月16日 UTC 17:41resolved

   # Incident Report ## Summary On Wednesday, June 10, 2026, at 03:30 US/Pacific, an incident occurred affecting the availability of Gemini services across all surfaces, including web, mobile (iOS and Android), and integrations within Google Chrome. The incident resulted in an elevated error rate for approximately 6 hours and 55 minutes, with full service restoration confirmed after a total duration of 14 hours and 49 minutes. We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future. ## Root Cause The disruption was caused by extreme read contention within the foundational database service that manages tool deployment metadata. The primary cause was an index design issue within the database where a column used for tracking deployment expirations contained a high volume of rows with similar values. This resulted in "hotspotting," where traffic was concentrated on a very small number of database shards, overwhelming them. Additionally, the service utilized an in-memory cache with a very short Time To Live (TTL) of only one minute, requiring frequent database refreshes. The failure sequence was as follows: 1. **Technical Trigger:** The trigger was an upward spike in the Queries Per Second (QPS) from the frontend. The underlying system was already running close to maximum usage and the incoming QPS crossed a tipping threshold beyond which the underlying spanner started getting overloaded. 2. **Systemic Effect:** This short window, combined with an indexing anomaly where specific metadata fields containing empty values were clustered on a single database partition, led to a "hot shard" condition. 3. **Contention and Latency:** As request volume increased, the internal tool management service experienced a more than 10x surge in database calls because the cache hit rate dropped significantly. 4. **Failure State:** The underlying storage layer reached its capacity for handling incoming queries, and database failure rates skyrocketed to 60%. This led to cache hit rate dropping down to 50%. Automated validation failed to prevent this because the indexing strategy did not sufficiently account for the concentration of data rows when specific identifiers were absent. ## Remediation and Prevention The issue was detected by internal real-time monitoring alerts indicating high processing error rates. Engineering teams performed several targeted actions to restore the service: * **Throttling:** Applied Rate Access Control Lists (RateACLs) to the most affected database shards to allow internal caches to recover. * **Index Redistribution:** Gradually redistributed common values in the database index to random values in a specific target range, effectively spreading the load across multiple shards. * **Cache Policy Update:** Deployed a configuration change to increase the in-memory cache Time To Live (TTL) from 1 minute to 20 minutes, significantly reducing database load. * **Deadline Adjustment:** Shortened the Remote Procedure Call (RPC) deadlines for database queries to prevent request pile-ups during periods of high latency. ## Prevention To prevent a recurrence, Google engineering will be implementing the following actions: * **Index Design Standards:** Restructure of database index to prevent "hotspotting". * **Adaptive Cache Tuning:** Implement more robust cache policies that prevent load amplification during periods of backend stress. * **Enhanced Hotspot Monitoring:** Deploy improved monitoring and alerting specifically designed to detect uneven database load distribution before it impacts user traffic. * **Service Resiliency:** Implement advanced load protection mechanisms, such as smart task resizing and query coalescing for preventing spanner overloads. ## Detailed Description of Impact The impact window occurred between 03:30 US/Pacific and 10:25 US/Pacific on June 10, 2026\. **Gemini App (Web and Mobile):** * High Failure Rates: Users experienced a 50% error rate when attempting to send prompts, receiving "Something went wrong" messages . * Service Unavailability: The issue affected both consumer accounts and enterprise Google Workspace customers . * Enterprise Google Workspace Users encountered disruptions when attempting to attach assets from Google Drive within the web application (gemini.google.com). Affected users observed the "Add from Drive" functionality to be visually disabled and unresponsive following interaction with the "+" prompt. **Integrations:** * **Google Chrome Integration:** The Gemini Side Panel and integrated conversational features encountered persistent timeouts.

1. 2026年5月31日 UTC 04:59resolved

   **Title** Multiple Workspace Products experiencing Issues. **Description** We are experiencing an issue with Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, Google Docs beginning on Saturday, 2026-05-30 20:28 PDT. Our engineering team continues to investigate the issue. We will provide an update by Saturday, 2026-05-30 22:10 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Customers may experience issues loading the application/ intermittent high latency or errors while using the application. **Workaround** None at this time.

2. 2026年5月31日 UTC 05:11resolved

   **Title** [Mitigated] Multiple Workspace Products experienced Issues. **Description** The issue with Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, Google Docs has been resolved for all affected users as of Saturday, 2026-05-30 21:30 PDT. We thank you for your patience while we worked on resolving the issue. **Symptoms** Customers may have experienced issues loading the application/ intermittent high latency or errors while using the application. **Workaround** None at this time as the issue stands mitigated

3. 2026年6月2日 UTC 03:50resolved

   # Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Workspace, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced impact outside of what is listed below, please reach out to Google Workspace Support using help article https://support.google.com/a/answer/1047213 ## Date/Time of the Issue (All time US/Pacific) Incident Start: 30 May 2026 20:15 Incident End: 30 May 2026 21:30 Duration: 1 hour, 15 minutes ## Summary Starting on Saturday, 30 May 2026 at 20:15 US/Pacific, multiple Google Workspace products experienced service disruptions for a duration of 1 hour and 15 minutes. The affected services included Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, and Google Docs. During this incident, customers encountered difficulties loading applications, as well as intermittent high latency or errors. ## Preliminary Root Cause The disruption originated from failures in a regional infrastructure component responsible for Google's distributed lock service. This critical system facilitates resource synchronization, manages shared data access, and coordinates background tasks for numerous Google services. A high volume of rapid configuration changes triggered the regional failure, preventing Workspace servers from reliably processing traffic. To mitigate the impact, Google Workspace traffic was redirected to alternative regions. Google engineers have begun a full root cause analysis and will provide additional information once it is available. ## Remediation Google engineers were alerted to the issue via automated monitoring at 20:28 US/Pacific on Saturday, 30 May 2026, and immediately began an investigation. The investigation identified elevated error rates and high latency affecting multiple Google Workspace backend services. Upon investigation our engineering team confirmed errors were primarily originating from some regional servers due to coordination service failures in the region. To mitigate the impact, Google engineers redirected traffic away from the affected servers. ## Description of Impact Affected customers encountered difficulties loading applications or experienced failures when performing tasks within the following products: * Gmail * Google Calendar * Google Chat * Google Docs * Google Drive * Google Meet * Google Voice

4. 2026年6月4日 UTC 20:11resolved

   # Incident Report ## Summary Starting at 20:15 US/Pacific on Saturday, 30 May 2026, various Google Workspace services encountered service-level disruptions lasting approximately 75 minutes. The scope of impact spanned several products, specifically affecting Gmail, Google Docs, Drive, Calendar, Chat, Meet, and Google Voice. Throughout the duration of this event, users faced obstacles while attempting to initialize applications, in addition to experiencing sporadic instances of elevated latency and request failures. Google offers a sincere apology for the operational interference this issue introduced to your organization. Recognizing the critical nature of Google Cloud to your daily operations, we deeply regret any resulting loss in productivity. Engineering efforts are currently focused on remediating the underlying cause to ensure future stability. ## Root Cause The disruption originated from failures in a critical cluster infrastructure component responsible for Google's service discovery and configuration management systems. This system facilitates resource synchronization, manages shared data access, and coordinates background tasks for numerous Google services. A high volume of rapid configuration changes triggered the regional failure in Workspace Services, preventing Workspace servers from reliably processing traffic. To mitigate the impact, Google Workspace traffic was redirected to alternative regions. ## Remediation and Prevention Google engineers were alerted to the issue via automated monitoring on Saturday, 30 May 2026 at 20:28 US/Pacific and immediately began an investigation. The investigation identified elevated error rates and high latency affecting multiple Google Workspace backend services. Upon investigation our engineering team confirmed errors were primarily originating from some regional servers due to coordination service failures in the region. To mitigate the impact, Google engineers redirected traffic away from the affected servers. Google is committed preventing a repeat of this issue in the future and is completing the following actions: - Prevent recurrence of this incident by rolling out the fix for the latent encryption library issue, which improves the handling of internal log compaction compactions during active file writes, to prevent recurrence of the cluster instability. - Investigating additional resilience in our database layer. ## Detailed Description of Impact On 30 May 2026 from 20:15 to 21:30 US/Pacific, affected customers encountered difficulties while loading applications or experienced failures when performing tasks within the following products: - Gmail - Google Calendar - Google Chat - Google Docs - Google Drive - Google Meet - Google Voice

1. 2026年5月21日 UTC 15:37resolved

   **Summary** Gmail users are experiencing delayed delivery of messages sent from the bank.in domains. **Description** We are experiencing an issue with Gmail beginning on Thursday, 2026-05-21 at 00:00 PDT. Mitigation efforts are currently underway by our engineering team. We will provide the next update by Thursday, 2026-05-21 at 09:30 PDT. **Diagnosis / Customer Symptoms** Gmail users are experiencing delayed delivery of messages sent from the bank.in domains. **Workaround** None at this time.

2. 2026年5月21日 UTC 16:09resolved

   **Summary** Gmail users experienced delayed delivery of messages sent from the bank.in domains. **Description** Our internal telemetry shows that the issue with Gmail has been resolved for all affected users as of Thursday, 2026-05-21 at 08:47 US/Pacific. Our engineering team is actively monitoring the system to ensure continued stability. **Diagnosis / Customer Symptoms** Customers should expect new messages to be delivered normally, older emails could take some time as the senders continue to retry. **Workaround** This issue is now mitigated.

1. 2026年5月20日 UTC 01:07resolved

   **Summary** NotebookLM customers are experiencing an issue where account tiers are being incorrectly downgraded. Affected Ultra & Pro tier users are seeing Free tier features. **Description** We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 20:30 PDT with current details. **Customer Symtomps** Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. **Workaround** None at this time

2. 2026年5月20日 UTC 03:20resolved

   **Title** NotebookLM customers are experiencing an issue where all premium account tiers are being incorrectly downgraded to free. **Description** We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 22:00 PDT with current details. **Symptoms** Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. **Workaround** None at this time.

3. 2026年5月20日 UTC 04:38resolved

   **Title** NotebookLM customers may have experienced an issue where all premium account tiers are being incorrectly downgraded to free. **Description** The issue with NotebookLM has been resolved for all affected users as of Tuesday, 2026-05-19 21:04 PDT. From preliminary analysis, the issue was triggered by a recent software update resulting in accounts on premium plans being incorrectly recognized as free accounts. The issue was mitigated by restoring the system to a previous stable state, which successfully reinstated the appropriate service tiers for all affected accounts. We thank you for your patience while we worked on resolving the issue. **Symptoms** Customers may have noticed lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. **Workaround** None at this time.

1. 2026年5月13日 UTC 17:55resolved

   **Summary** Some Cameyo by Google customers could not start their sessions after rolling out the new channel version. **Description** We were experiencing an issue with Cameyo by Google, beginning on Tuesday, 12 May 2026 09:01 US/Pacific. The issue was mitigated on Tuesday, 12 May 2026 15:16 US/Pacific by restarting the RAP system service, and performing full server reboots. From preliminary investigation, this was caused by a faulty code for logging improvement on the Player VMs. Log files were unexpectedly duplicated until the disk was full leading to the session failures. Some customers were recovered automatically after the channel binaries were rolled back, while the others were required to restart their VMs manually. Currently, the issue is fully mitigated and change is rolled back. We apologise to those who were impacted by this issue. **Customer Symptoms** The customers were experiencing an issue that couldn’t connect to the Player VMs normally. The disk utilization on the affected VMs reaches 99% or even 100%. **Workaround** Not needed because all affected servers have been mitigated.

1. 2026年5月16日 UTC 02:05resolved

   **Summary** Gmail Android users using Microsoft Exchange Online may fail to log in due to authentication issues. **Description** We are experiencing an issue with Gmail beginning on Saturday 2026-05-06. Our engineering team continues to investigate the issue. We will provide more information by Monday, 2026-05-18 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Impacted users may experience authentication failures while logging in to Microsoft Exchange Online through Gmail App on Android devices. **Workaround** Affected users can use Microsoft web app to access the Inbox.

2. 2026年5月18日 UTC 21:45resolved

   **Summary** Gmail Android users using Microsoft Exchange Online accounts may fail to Log In and Sync due to authentication issues. **Description** We are experiencing an issue with Gmail Android client connecting with Microsoft Exchange Online accounts beginning on Saturday 2026-05-06. Our engineering team has identified the issue and is actively working on rolling out a fix to unblock all the affected customers. We will provide more information by Tuesday, 2026-05-19 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Affected users can use Microsoft Web App to access the Inbox.

3. 2026年5月19日 UTC 21:55resolved

   **Summary** Gmail Android users using Microsoft Exchange Online accounts may fail to Log In and Sync due to authentication issues. **Description** We are experiencing an issue with Gmail Android client connecting with Microsoft Exchange Online accounts beginning on Saturday 2026-05-06. Our engineering team has identified the issue and started rolling out a new version of Gmail Android release that contains the fix to unblock users. Users already on the new app version will be able to Log In and Sync their accounts successfully. We will provide more information by Thursday, 2026-05-21 17:00 US/Pacific with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Affected users can use Microsoft Web App to access the Inbox.

4. 2026年5月22日 UTC 00:04resolved

   **Summary** Gmail Android users using Microsoft Exchange Online accounts may fail to Log In and Sync due to authentication issues. **Description** Our engineering team identified the issue and released a new version of the Gmail Android application (version 2026.05.11) to the Google Play Store, which contains a fix to unblock affected users. If you are currently encountering this issue, please upgrade to the latest version of the Gmail Android app. Users operating on the new app version should be able to successfully log in and sync their accounts. We will provide more information by Friday, 2026-05-22 17:00 US/Pacific with current details. We thank you for your patience while we are working on resolving the issue. **Symptoms** Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Affected users could update to the latest version of Gmail Android (version 2026.05.11) in Google Play Store.

5. 2026年5月22日 UTC 18:57resolved

   **Summary** [Resolved] Gmail Android users utilizing Microsoft Exchange Online accounts experienced authentication and synchronization failures. **Description** The issue with Gmail has been resolved in the new Gmail android release (version 2026.05.11) as of Thursday, 2026-05-21 15:00 PDT. Our engineering team identified the issue and released a new version of the Gmail Android application to the Google Play Store, which contains a fix to unblock affected users. If you are currently encountering this issue, please upgrade to the latest version of the Gmail Android app. Users operating on the new app version will be able to successfully log in and sync their accounts. We thank you for your patience while we worked on resolving the issue. **Symptoms** Impacted users might have experienced authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Update to the latest version of Gmail Android (2026.05.11) in Google Play Store.

1. 2026年5月5日 UTC 23:35resolved

   **Summary** Investigating elevated error rates with Gemini conversations. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Tuesday, 2026-05-05 20:30 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

2. 2026年5月6日 UTC 03:22resolved

   **Summary** Investigating elevated error rates with Gemini conversations. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2026-05-06 09:00 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

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

   **Summary** Gemini conversations are experiencing elevated error rates. **Description** Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-05-07 17:00 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

4. 2026年5月7日 UTC 23:52resolved

   **Summary** Gemini conversations are experiencing elevated error rates. **Description** Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-05-07 20:30 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

5. 2026年5月8日 UTC 01:00resolved

   **Summary** Gemini conversations may have experienced elevated error rates. **Description** The issue with Gemini has been resolved for all affected users as of Thursday, 2026-05-07 17:00 PDT. The issue was triggered due to a combination of insufficient database resources, and application issues. The database capacity issues were resolved, and further code changes are being made to mitigate the application issues. We thank you for your patience while we worked on resolving the issue. **Symptoms** Affected customers may have experienced the "Something went wrong(13)" error message in their Gemini conversations.

6. 2026年5月8日 UTC 05:16resolved

   **Summary** Gemini conversations are experiencing elevated error rates. **Description** Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-05-08 01:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

7. 2026年5月8日 UTC 07:29resolved

   **Summary** Gemini conversations may experience elevated error rates. **Description** Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 04:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

8. 2026年5月8日 UTC 10:23resolved

   **Summary** Gemini conversations may experience elevated error rates. **Description** Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 09:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

9. 2026年5月8日 UTC 15:53resolved

   **Summary** Gemini conversations may experience elevated error rates. **Description** Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 12:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

10. 2026年5月8日 UTC 18:58resolved

    **Summary** Gemini conversations may have experienced elevated error rates. **Description** The issue with Gemini has been resolved for all affected users as of Friday, 2026-05-08 11:53 PDT. The issue was triggered due to a combination of insufficient database resources, and application bugs. The database capacity issues were resolved, and further code changes are being made to mitigate the application issue. We thank you for your patience while we worked on resolving the issue. **Symptoms** Affected customers may have experienced "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

1. 2026年4月29日 UTC 19:17resolved

   **Title:** Investigating issues with Classroom. **Description:** We are experiencing an issue with Classroom beginning at Wednesday, 2026-04-29 11:30 PDT. Our engineering team continues to investigate the issue. We will provide more information by Wednesday, 2026-04-29 13:00 PDT. **Symptoms:** Affected users may experience issues accessing classroom. **Workaround:** No workarounds available at this time.

2. 2026年4月29日 UTC 19:53resolved

   **Title:** Investigating issues with Classroom. **Description:** Our engineering team has identified the cause and working on mitigation of the issue . The mitigation is expected to complete by Wednesday, 2026-04-29 15:00 PDT. We will provide more information by Wednesday, 2026-04-29 15:15 PDT. **Symptoms:** Affected users may experience issues accessing classroom. **Workaround:** No workarounds available at this time.

3. 2026年4月29日 UTC 20:13resolved

   **Title:** Investigating issues with Classroom. **Description:** A fix has been deployed, and services have stabilized for the majority of users. We are aware that a small subset of users may still encounter errors. Our engineering team is actively working on a secondary resolution to address these remaining users. Full resolution for remaining users is expected to complete by Wednesday, 2026-04-29 14:00 PDT. We will provide an update by Wednesday, 2026-04-29 14:15 PDT with current details. **Symptoms:** Affected users may experience issues accessing classroom. **Workaround:** No workarounds available at this time.

4. 2026年4月29日 UTC 21:07resolved

   **Title:** An issue with Classroom is resolved. **Description:** A fix has been deployed, and services have stabilized for all users. The issue with Google Classroom has been resolved for all affected users as of Wednesday, 2026-04-29 13:45 PDT. The issue was due to an internal software migration. Our engineers have mitigated the issue by rolling back the migration for impacted users. We thank you for your patience while we worked on resolving the issue. **Symptoms:** Affected users may have experienced issues accessing the classroom. **Workaround:** The issue is resolved.

1. 2026年4月28日 UTC 15:20resolved

   **Title:** Investigating issues with slow loading of AppSheet **Description:** We are experiencing an issue with AppSheet beginning at Tuesday, 2026-04-28 00:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-04-28 09:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms:** Affected customers would experience slow loading times and internal server errors for AppSheet apps. **Workaround:** None at this time.

2. 2026年4月28日 UTC 16:00resolved

   **Title:** Investigating issues with slow loading of AppSheet. **Description:** Our engineering team has implemented a fix and system telemetry indicates that latency and error rates have returned to normal levels. We are continuing to monitor the environment closely to ensure full stability. We will provide an update by Tuesday, 2026-04-28 10:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms:** Affected customers would experience slow loading times and internal server errors for AppSheet apps. **Workaround:** None at this time.

3. 2026年4月28日 UTC 16:50resolved

   **Title:** Mitigated issues with slow loading of AppSheet apps. **Description:** The issue with AppSheet has been resolved for all affected users as of Tuesday, 2026-04-28 08:50 PDT. We thank you for your patience while we worked on resolving the issue. **Symptoms:** Affected customers would have experienced slow loading times and internal server errors for AppSheet apps.

1. 2026年4月10日 UTC 10:07resolved

   **Summary** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Description** We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 04:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

2. 2026年4月10日 UTC 10:55resolved

   **Summary** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Description** We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 05:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

3. 2026年4月10日 UTC 11:27resolved

   **Summary** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-04-10 09:00 PDT. **Customer Symptoms** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

4. 2026年4月10日 UTC 15:06resolved

   **Summary** Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. **Description** The issue with Admin Console has been resolved for all affected users as of Friday, 2026-04-10 07:50 PDT. Suspected CL have been rolled back and we are seeing in our graphs errors rate have gone down. Customers also confirmed that issues have been mitigated. We thank you for your patience while we worked on resolving the issue. **Customer Symptoms** Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: * Admin should revoke the key. * Admin to create the verification code to sign-in. * The user should sign-in using Backup verification code and then re-enrolls the security key.

1. 2026年4月8日 UTC 22:22resolved

   **Summary** AppSheet customers are experiencing redirection to asia-southeast.appsheet.com instead of their intended application URLs. **Description** Beginning on Wednesday, 2026-04-08 14:05 PDT, we are experiencing an issue with AppSheet that caused users to be erroneously redirected to the asia-southeast region. Our engineers have identified the cause was due to a recent change and have reverted. Our internal telemetry shows the signs of recovery and are currently monitoring the recovery status. We expect full service recovery within an hour. We will provide an update by Wednesday, 2026-04-08 16:30 PDT with current details **Customer Symptoms** Users are automatically redirected to asia-southeast.appsheet.com, which may cause "Forbidden" or 403 errors when attempting to access their apps. **Workaround** None at this time.

2. 2026年4月8日 UTC 23:27resolved

   **Summary** AppSheet customers experienced redirection to asia-southeast.appsheet.com instead of their intended application URLs. **Description** The issue with AppSheet has been resolved for all the affected customers as of Wednesday, 2026-04-08 15:40 US/Pacific. As per the preliminary analysis, the issue was triggered by a recent change that caused the users to be erroneously redirected to the asia-southeast region. Our engineering team rolled back the change to mitigate the impact and verified the service stability. We thank you for your patience while we worked on resolving the issue. **Customer Symptoms** Users may have experienced automatic redirection to asia-southeast.appsheet.com, resulting in errors when attempting to access their apps. **Workaround** None at this time.

1. 2026年4月8日 UTC 18:22resolved

   **Title:** Customers may experience delays in receiving and sending emails. **Description:** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 12:00 PDT with current details. **Symptoms:** Customers may experience delays in receiving and sending emails. **Workaround:** None at this time.

2. 2026年4月8日 UTC 19:02resolved

   **Title:** Customers may experience delays in receiving and sending emails. **Description:** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 13:00 PDT with current details. **Symptoms:** Customers may experience delays in receiving and sending emails. **Workaround:** None at this time.

3. 2026年4月8日 UTC 20:03resolved

   **Title:** Customers may experience delays in receiving and sending emails. **Description:** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 15:00 PDT with current details. **Symptoms:** Customers may experience delays in receiving and sending emails. **Workaround:** None at this time.

4. 2026年4月8日 UTC 21:49resolved

   **Title** Customers may have experienced delays in receiving and sending emails. **Description** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning on Wednesday, 2026-04-08 06:30 PDT. Our engineering team has applied the mitigation, and our internal monitoring indicates that delays and errors have subsided. We will continue to monitor for service stability to ensure full recovery. We will provide an update by Wednesday, 2026-04-08 16:00 PDT with current details. **Symptoms** Customers may have experienced delays in receiving and sending emails. **Workaround** None at this time.

5. 2026年4月8日 UTC 22:54resolved

   **Title** Customers may have experienced delays in receiving and sending emails. **Description** The issue with Gmail has been resolved for all affected users as of Wednesday, 2026-04-08 14:49 PDT. Our engineering team identified a potential issue with a noisy neighbour and has successfully mitigated impact. A full root cause analysis is in progress and further details will be shared through a subsequent incident report. We thank you for your patience while we worked on resolving the issue. **Symptoms** Customers may have experienced delays in receiving and sending emails. **Workaround** None at this time.

6. 2026年4月10日 UTC 02:32resolved

   # Preliminary Incident Report We apologize for the inconvenience this Gmail service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced an impact outside of what is listed below, please reach out to Google Workspace Support using the help article https://support.google.com/a/answer/1047213. ## Date/Time of the Issue (All time US/Pacific) - Incident Start: 08 April 2026 06:30 - Incident End: 08 April 2026 14:40 - Duration: 8 hours, 10 minutes ## Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. ## Preliminary Root Cause The preliminary root cause was identified as increased connection errors to some external mail services. Google engineers have begun a full root cause analysis and will provide additional information once it is available. ## Remediation The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: **Account Suspension:** One of the domains responsible for spamming was identified, resulting in the suspension of the abusive account after review. **Traffic Blocking:** A block rule was implemented to specifically address and stop traffic originating from an abusive sending domain. Teams monitored rejection rates until they returned to normal levels, confirming that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. A comprehensive Incident Report that will be published to provide further details and outline preventative measures. ## Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

7. 2026年4月17日 UTC 09:10resolved

   # Incident Report ## Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. ## Root Cause The root cause was identified as increased connection errors to external mail services hosted by a specific 3rd party provider. ## Remediation and Prevention The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: **External Mail Provider Reachout:** Google worked with the external mail provider to unblock connections and prevent similar issues in the future. Teams monitored rejection rates until they returned to normal levels, verifying that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. Google is committed to preventing a repeat of this issue in the future and is completing the following actions: - Deploy systems to proactively track external blocklists and alert on degradation before users are impacted. - Improve monitoring and alerting systems to proactively detect errors related to external email recipient communication. ## Detailed Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30 PDT, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

1. 2026年3月21日 UTC 03:19resolved

   **Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.

2. 2026年3月21日 UTC 03:46resolved

   **Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 23:00 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.

3. 2026年3月21日 UTC 05:33resolved

   **Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our mitigation efforts are underway and we are seeing the signs of recovery. We do not have an ETA for full mitigation. We will provide the next update by Saturday, 2026-03-21 00:30 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.

4. 2026年3月21日 UTC 07:17resolved

   **Description** The issue has been mitigated as of Friday, 2026-03-20 22:03 US/Pacific. The service issue which resulted in connection timeouts and 502 error pages, was caused by excess traffic impacting the keep.google.com. Our engineering team has implemented a mitigation and is continuing to work to ensure long-term service stability and prevent recurrence. We thank you for your patience while we worked on resolving the issue.

1. 2026年3月13日 UTC 13:58resolved

   **Description** We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. Our engineering teams are actively working to mitigate the impact. We will provide an update by Friday, 2026-03-13 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** A subset of customers may experience elevated error rates when accessing the impacted products in the US region. **Workaround** Impacted users may re-attempt the unsuccessful action.

2. 2026年3月13日 UTC 14:34resolved

   **Description** We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. We have confirmed that the issue affecting Google Drive is now mitigated. Users should no longer experience unavailability when accessing or interacting with Drive files. Our engineering teams continue to actively work on mitigating the remaining impacted products. We will provide an update by Friday, 2026-03-13 09:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** A subset of customers may experience elevated error rates when accessing the impacted products in the US region. **Workaround** Impacted users may re-attempt the unsuccessful action.

3. 2026年3月13日 UTC 14:56resolved

   **Description** The issue with Google Workspace has been resolved for all affected users as of Friday, 2026-03-13 07:30 PDT. From preliminary analysis, the incident was triggered by resource contention in the impacted location, following a recent update. This led to elevated error rates and latency for several Workspace products. Our engineering teams mitigated the impact by increasing infrastructure capacity,performing traffic restarts, and rolling back the identified change We thank you for your patience while we worked to resolve this issue. **Customer Symptoms** A subset of customers may have experienced elevated error rates when accessing the impacted products in the US region. **Workaround** NA. Issue is now mitigated

1. 2026年2月23日 UTC 08:17resolved

   **Summary** Google Chat is experiencing Issue with creating a new conversations **Description** Our engineering team continues to investigate the issue. We will provide an update by Monday, 2026-02-23 00:45 PST with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Users may experience errors when attempting to create new conversations or spaces in Google Chat. Existing conversations remain functional. **Workaround** None at the moment

2. 2026年2月23日 UTC 08:34resolved

   **Summary** Google Chat is experiencing issues with creating new conversations. **Description** Our engineering teams are actively working on mitigation efforts to restore the ability to create new conversations as quickly as possible. We do not have any ETA at the moment. We will provide an update by Monday, 2026-02-23 01:30 PST with current details. **Customer Symptoms** Users may experience errors when attempting to create new Direct Messages (DM) or new chat spaces in Google Chat. This issue specifically affects the creation of new conversations; however, users can continue to send and receive messages in existing conversations and spaces **Workaround** None at the moment

3. 2026年2月23日 UTC 08:54resolved

   The issue with Google Chat has been resolved for all affected users as of Monday, 2026-02-23 00:35 PST. As per our preliminary analysis, the incident was triggered by a recent configuration update. Our engineering team performed a rollback to mitigate the impact and verified the stability. We thank you for your patience while we worked on resolving the issue.