Google Workspace Status : Google Meet - AVAILABLE - 2025-12-02 12:53:24 UTC

[back...@gmail.com]

Product: Google Meet
Status: AVAILABLE
Published: 2025-12-02 12:53:24 UTC

**# 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. If you have experienced 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**
Between 25 November 2025 21:34 US/Pacific and 26 November 2025 2:30
US/Pacific, Google Meet experienced a service disruption for a total
duration of 5 hours and 10 minutes. A subset of Google Meet users in
the Asia region were unable to start or join meetings via the web and
on meeting devices.
Google is committed to quickly and continually improving our
technology and operations to prevent service disruptions. We
appreciate your patience and apologize again for the impact to your
organization. We thank you for your business.
**## Root Cause**
The incident was caused by an issue within the Meet web frontend
server located in the Singapore (SIN) metropolitan area, which is a
critical component and responsible for handling Google Meet
connections for users in the Asia region.
The issue began with a software update to the Meet web frontend
server. Approximately three hours after this update was complete, a
combination of traffic patterns and a code change creating a thread
deadlock risk which is currently being investigated further, acted as
the trigger for the outage.
This trigger led to a sustained period of long-hanging requests in the
server's processing queue. This abnormal workload ultimately consumed
all available resources, causing the server to experience
Out-Of-Memory (OOM) errors and subsequent task crashes. The result
(effect) was that the server could not properly process requests,
leading to failures when users attempted to load the meeting UI or
join meetings.
Furthermore, the issue detection was slightly delayed because traffic
patterns in the immediate interval after the software update did not
trigger the issue, delaying our response and mitigation efforts.
**## Remediation**
The issue started on 25 November 2025 at 21:34 US/Pacific and the
problem was first detected by Google's internal alerting systems at
21:41 US/Pacific. Our engineers promptly began working to restore
service by taking the following actions in chronological order:
**25 November, 22:08 US/Pacific** - Draining of the most affected cluster
Efforts were made to shift traffic away from the specific server
cluster experiencing the crashes.
**25 November, 22:20 US/Pacific** - Increase in capacity
Our engineers increased the resources available to the affected service.
**25 November, 23:27 US/Pacific** - Rollback of the webfrontend binary
The most effective step taken was reverting the software on the Meet
web frontend server back to the previous stable version. This action
mitigated the issue and restored service availability.
Service was fully restored on **26 November 2025 at 02:30 US/Pacific.**
**## Detailed Description of Impact**
A subset of Google Meet users in the Asia Pacific region experienced
issues loading the meeting user interface (meet.google.com) or were
unable to start or join meetings between 25 November 2025 21:34
US/Pacific and 26 November 2025 2:30 US/Pacific. The issue primarily
affected users accessing Google Meet via Web browsers and Meeting
Devices. Mobile users were not affected.

Link to official detail of this status:
https://www.google.com/appsstatus/dashboard/incidents/F9Tft7xb3xqenFoKvY4W