Google Workspace outage, 28 August 2026
**Summary:** Google Chat users are experiencing an issue where they receive notifications for new messages, but the actual messages fail to appear in their chat...
- Started
- Resolved
- 28 Aug 2026, 20:34 UTC (after 2 h 44 min)
- Impact
- Not stated
- Affected
- Google Chat
Is this still happening?
No. Google Workspace marked this incident resolved on 28 Aug 2026, 20:34 UTC, 2 h 44 min after it began.
Right now: Google Workspace reports all systems operational. (as of 5 Nov, 00:11 UTC) Live Google Workspace status
What caused it: Google Workspace's root cause analysis
Incident Report Summary On Friday, August 28, 2026, between 10:50 US/Pacific and 13:34 US/Pacific for a duration of 2 hours and 44 minutes, Google Chat users experienced delays in receiving real-time incoming messages within active conversation streams across web, desktop, and mobile applications. While users continued to receive notifications for new messages, the message contents did not automatically render in active conversation streams until the user manually refreshed the application or sent a reply message. To our valued Google Workspace customers, we are deeply sorry for the service interruption you experienced. We are taking immediate and decisive action to address the issue and strengthen our systems against future incidents. Root Cause The incident was triggered during a global database schema rollout. An incompatible database schema change caused database writes required for message delivery to start failing. Specifically, a mechanism for schema synchronization-designed to ensure high consistency between primary storage and live message delivery-encountered a rare race condition bug. This caused backend message dispatchers to attempt writes against an unready schema state, leading to write failures. Because live message delivery had an active dependency on these writes completing successfully before pushing events to user screens, the failure caused incoming messages to experience synchronization delays. Separate push notification services and core message storage operated independently and were unaffected, which is why users still received alerts for new messages while active conversation streams experienced delays. Remediation and Prevention The issue was detected through automated backend alerting on dispatch error rates, alongside corresponding customer reports. Google Engineering initiated parallel workstreams to restore service. * At 12:44 US/Pacific, Google Engineering directly mitigated the source of the issue by removing the dependency that live message delivery had on the failing database write. This allowed new incoming messages to bypass the failed write and immediately resume normal real-time delivery to user screens. * At 13:00 US/Pacific, Engineering halted and reverted the database schema change to its previous verified stable version, restoring full database compatibility. * By 13:34 US/Pacific, as queued messages were processed, real-time message synchronization delays returned to 0% across all customer domains. Engineering ve...
Last update from Google Workspace
Incident Report Summary On Friday, August 28, 2026, between 10:50 US/Pacific and 13:34 US/Pacific for a duration of 2 hours and 44 minutes, Google Chat users experienced delays in receiving real-time incoming messages within active conversation streams across web, desktop, and mobile applications. While users continued to receive notifications for new messages, the message contents did not automatically render in active conversation streams until the user manually refreshed the application or sent a reply message. To our valued Google Workspace customers, we are deeply sorry for the service interruption you experienced. We are taking immediate and decisive action to address the issue and str...
Read the full incident on the official Google Workspace status page
Similar Google Workspace incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 2 h 3 min
-
, resolved after 6 h 15 min
-
, resolved after 3 h 27 min
-
, resolved after 56 min
-
, resolved after 8 h 47 min