Is Google Meet down? › Outage history › Nov 26, 2025

Google Meet partial outage on Nov 26, 2025: what happened

On Nov 26, 2025, the Google Workspace status dashboard reported "Google Meet customers are experiencing issues loading meet.google.com in the Asia region.". About 4 hours 56 min: from Nov 26, 2025, 05:34 UTC to Nov 26, 2025, 10:30 UTC, by the official start and resolution times.

Started

Nov 26, 2025, 05:34 UTC

Resolved

Nov 26, 2025, 10:30 UTC

Duration

4 hours 56 min

Official impact

Service disruption

Affected

Google Meet

Source

Google Meet customers are experiencing issues loading meet.google.com in the Asia region. on the Google Workspace status dashboard

The Google Workspace status dashboard rated the impact "Service disruption": a partial outage. Some parts or some users were affected; it was not a complete outage.

What caused the Google Meet partial outage?

"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 trigger was a combination of regional traffic patterns and latency accessing the dependency involved."

From the Google Workspace status dashboard, Dec 2, 2025, 12:52 UTC.

When was it fixed?

The Google Workspace status dashboard marked it resolved at Nov 26, 2025, 10:30 UTC, 4 hours 56 min after it started. Its resolution note: "# 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 ..."

Timeline of official updates

Every update the Google Workspace status dashboard posted, oldest first. Times are UTC.

1. Nov 26, 2025, 07:38 UTC service disruption

   Title Google Meet customers are experiencing issues loading meet.google.com in the Asia region. Description We are experiencing an issue with Google Meet beginning on Tuesday, 2025-11-25 21:34 PST. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-11-26 02:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms Customers are experiencing issues loading meet.google.com. Workaround Customers can use the mobile version to load Meet.

2. Nov 26, 2025, 08:38 UTC service disruption

   Title Google Meet customers are experiencing issues loading meet.google.com in the Asia region. Description We are experiencing an issue with Google Meet beginning on Tuesday, 2025-11-25 21:34 PST. Our engineering team continues to investigate the issue and work on a mitigation strategy. We will provide an update by Wednesday, 2025-11-26 02:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms Customers are experiencing issues loading meet.google.com. Workaround Customers can use the mobile version to load Meet.

3. Nov 26, 2025, 09:33 UTC service disruption

   Title Google Meet customers are experiencing issues loading meet.google.com in the Asia region. Description We are experiencing an issue with Google Meet beginning on Tuesday, 2025-11-25 21:34 PST. Our engineering team continues to investigate the issue and work on a mitigation strategy. We will provide an update by Wednesday, 2025-11-26 03:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms Customers are experiencing issues loading meet.google.com. Workaround Customers can use the mobile version to load Meet.

4. Nov 26, 2025, 10:46 UTC resolved

   Title Google Meet customers experienced issues loading meet.google.com in the Asia region. Description The issue with Google Meet has been resolved for all affected users as of Wednesday, 2025-11-26 02:30 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 Customers experienced issues loading meet.google.com. This issue affected Google Meet traffic in Asia. Other regions were not affected. Workaround None as the issue has been mitigated.

5. Nov 27, 2025, 13:49 UTC resolved

   # 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 ...

6. Dec 2, 2025, 12:52 UTC resolved

   # 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 ...

Google Meet partial outage questions

Other recent Google Meet incidents

• Multiple Workspace Products experiencing Issues. May 31, 2026, 03:28 UTC, 56 minutes
• Some Google Meet customers may experience an issue with 'Continuous meeting chat' feature Dec 1, 2025, 08:00 UTC, 3 days 13 hours
• Google Meet meetings are seeing elevated error rates in upgrading the call on Android. Oct 30, 2025, 15:05 UTC, 20 hours 51 min

Full Google Meet outage history and biggest outages → · Recent outages across all services →

Quotes are the Google Workspace status dashboard's own words, from the official incident. Is It Up or Down is independent and not affiliated with Google Meet. Times are UTC.