Google Workspace Status Dashboard
Incidents
**Summary** Google Chat users might not be able to open chat while connecting from Europe. **Description** We are experiencing an issue with Google Chat beginning on Monday, 2025-11-24 00:02 PST. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2025-11-24 03:00 PST with current details. We apologize to all who are affected by the disruption. **Symptoms** Google Chat users might not be able to open chat while connecting from Europe. **Workaround** None at this time.

This page provides status information on the services that are part of Google Workspace. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://workspace.google.com/. For incidents related to Google Analytics, visit the Google Ads Status Dashboard.

Available
Service information
Service disruption
Service outage

Incident affecting Google Chat

Incident began at 2025-11-24 08:02 and ended at 2025-11-24 09:55 (times are in Coordinated Universal Time (UTC)).

Date	Time	Description
Nov 25, 2025	6:28 PM UTC	Preliminary Incident Report We apologize for the inconvenience this service disruption/outage 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. 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. Summary On Monday, 24 November 2025, Google Chat experienced an overload which led to service disruptions for users for a duration of 1 hour and 53 minutes. Customers encountered issues including the inability to send messages, load the chat application, and start new conversations. Some notifications were also incorrectly displayed with "Anonymous" as the sender Root Cause The trigger of the outage was transient errors served from an internal microservice in Europe that caused Chat backend processes to execute a fallback path to retrieve this data. The root cause was that the data retrieved from the fallback path subsequently caused an update to Chat metadata which were sent to user devices, causing those devices to reload data from Chat backend servers, thereby causing more updates to be sent to user devices, resulting in a cascading effect that overloaded Chat servers in Europe. Google engineers have implemented a mitigation to limit high rates of requests to prevent this cascading loop from recurring. Remediation Google engineers were alerted to the incident via alerts and immediately started an investigation. To fully mitigate the impact, our engineering teams took the following steps: Increased Server Capacity: To handle the unexpected surge in traffic, we significantly increased the capacity of our servers in the affected region to ensure the system could process all incoming requests smoothly. Limited the Rate of Metadata Updates: To prevent the cascading loop of requests from overloading Chat servers again, Google engineers have limited the rate of metadata updates so that Chat servers will not be overloaded in this way. Paused Non-Essential Background Tasks: To prioritize the restoration of core chat functions, we temporarily halted several internal background processes. This action helped to reduce the overall load on our systems, freeing up resources to serve user traffic more effectively. Gradual Traffic Restoration: Our automated defenses had initially blocked some traffic to prevent a complete system overload. A crucial part of the recovery was to gradually and carefully allow this traffic back. This controlled approach ensured that as users reconnected, the system wouldn't be overwhelmed again, allowing everyone to successfully re-establish their connection to Google Chat without getting stuck in a retry loop. Detailed Description of Impact For a duration of 1 hour and 53 minutes, Google Chat users in Europe experienced a service disruption which manifested as an inability to use core features of the service, such as sending messages and starting conversations.
Nov 24, 2025	10:06 AM UTC	Summary Google Chat users might not be able to open chat while connecting from Europe. Description The issue with Google Chat has been resolved for all affected users as of Monday, 2025-11-24 01:55 PST. We will publish an analysis of this incident once we have completed our internal investigation. We thank you for your patience while we worked on resolving the issue. Symptoms Google Chat users might not be able to open chat while connecting from Europe. Workaround None at this time.
Nov 24, 2025	9:47 AM UTC	Summary Google Chat users might not be able to open chat while connecting from Europe. Description We are experiencing an issue with Google Chat beginning on Monday, 2025-11-24 00:02 PST. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2025-11-24 03:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms Google Chat users might not be able to open chat while connecting from Europe. Workaround None at this time.

Date

Time

Description

Nov 25, 2025

6:28 PM UTC

Preliminary Incident Report

We apologize for the inconvenience this service disruption/outage 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. 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.

Summary

On Monday, 24 November 2025, Google Chat experienced an overload which led to service disruptions for users for a duration of 1 hour and 53 minutes. Customers encountered issues including the inability to send messages, load the chat application, and start new conversations. Some notifications were also incorrectly displayed with "Anonymous" as the sender

Root Cause

The trigger of the outage was transient errors served from an internal microservice in Europe that caused Chat backend processes to execute a fallback path to retrieve this data. The root cause was that the data retrieved from the fallback path subsequently caused an update to Chat metadata which were sent to user devices, causing those devices to reload data from Chat backend servers, thereby causing more updates to be sent to user devices, resulting in a cascading effect that overloaded Chat servers in Europe.

Google engineers have implemented a mitigation to limit high rates of requests to prevent this cascading loop from recurring.

Remediation

Google engineers were alerted to the incident via alerts and immediately started an investigation.

To fully mitigate the impact, our engineering teams took the following steps:

Increased Server Capacity: To handle the unexpected surge in traffic, we significantly increased the capacity of our servers in the affected region to ensure the system could process all incoming requests smoothly.
Limited the Rate of Metadata Updates: To prevent the cascading loop of requests from overloading Chat servers again, Google engineers have limited the rate of metadata updates so that Chat servers will not be overloaded in this way.
Paused Non-Essential Background Tasks: To prioritize the restoration of core chat functions, we temporarily halted several internal background processes. This action helped to reduce the overall load on our systems, freeing up resources to serve user traffic more effectively.
Gradual Traffic Restoration: Our automated defenses had initially blocked some traffic to prevent a complete system overload. A crucial part of the recovery was to gradually and carefully allow this traffic back. This controlled approach ensured that as users reconnected, the system wouldn't be overwhelmed again, allowing everyone to successfully re-establish their connection to Google Chat without getting stuck in a retry loop.

Detailed Description of Impact

For a duration of 1 hour and 53 minutes, Google Chat users in Europe experienced a service disruption which manifested as an inability to use core features of the service, such as sending messages and starting conversations.

Nov 24, 2025

10:06 AM UTC

Summary

Google Chat users might not be able to open chat while connecting from Europe.

Description

The issue with Google Chat has been resolved for all affected users as of Monday, 2025-11-24 01:55 PST.

We will publish an analysis of this incident once we have completed our internal investigation.

We thank you for your patience while we worked on resolving the issue.

Symptoms

Google Chat users might not be able to open chat while connecting from Europe.

Workaround

None at this time.

Nov 24, 2025

9:47 AM UTC

Summary

Google Chat users might not be able to open chat while connecting from Europe.

Description

We are experiencing an issue with Google Chat beginning on Monday, 2025-11-24 00:02 PST.

Our engineering team continues to investigate the issue.

We will provide an update by Monday, 2025-11-24 03:00 PST with current details.

We apologize to all who are affected by the disruption.

Symptoms

Google Chat users might not be able to open chat while connecting from Europe.

Workaround

None at this time.

Times are listed in Coordinated Universal Time (UTC)

Google Workspace Status Dashboard

Preliminary Incident Report

Summary

Root Cause

Remediation

Detailed Description of Impact