Google Workspace Status : Google Meet - AVAILABLE - 2025-12-02 12:56:02 UTC

[back...@gmail.com]

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

**# Incident Report**
**## 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 4 hours and 56 minutes. A subset of Google Meet users in
Asia 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 root cause of the issue was a software update to the Meet web
frontend server. The update introduced a blocking call to a dependency
in a critical code path, creating a thread deadlock risk.
Approximately three hours after the update was complete, tasks started
deadlocking. The trigger was a combination of regional traffic
patterns and latency accessing the dependency involved. This led to
stuck requests, Out-Of-Memory (OOM) errors and subsequent task crashes
leading to failures when users attempted to load the meeting UI or
join meetings.
**## Remediation and Prevention**
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** - Shifted traffic away from the most
affected Meet web frontend servers.
Efforts were made to shift traffic away from the specific Meet web
frontend servers 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**
after the rollback was complete.
Google is completing the following actions to prevent a repeat of this issue:
We are reviewing critical code paths to identify and address potential
blocking operations for the dependency that resulted in the
deadlocking.
We are adding additional checks to prevent adding blocking operations
in critical code paths.
Increase the load in our canary environments to make it more likely to
detect similar issues.
**## 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