История сбоев Google Workspace

1. 28 августа 2026 г. в 19:25 UTCresolved

   ** Резюме:** Пользователи чата Google сталкиваются с проблемой, когда они получают уведомления о новых сообщениях, но фактические сообщения не отображаются в их приложении чата, если пользователь не обновляет свое мнение. **Описание:** Мы испытываем периодические проблемы с Google Chat Friday, 2026-08-28 10:25 PDT. Наша инженерная команда исследовала этот вопрос и в настоящее время работает над его смягчением. Более подробную информацию мы предоставим к пятнице 2026-08-28 14:15 ПДТ с актуальными деталями. Мы приносим извинения всем, кто пострадал от сбоя. ** Симптомы клиента: ** Пользователи сталкиваются с проблемой, когда они получают уведомления о новых сообщениях, но фактические сообщения не отображаются в их приложении чата, если пользователь не обновляет свое мнение. **Работа вокруг:** Пользователи могут обновляться, чтобы видеть новые сообщения

2. 28 августа 2026 г. в 20:55 UTCresolved

   ** Резюме** Пользователи Google Chat столкнулись с проблемой, когда они получали уведомления о новых сообщениях, но фактические сообщения не появлялись в их приложении чата, если пользователь не обновлял свое мнение. **Описание** Проблема с Google Chat была решена для всех пострадавших пользователей по состоянию на пятницу 2026-08-28 13:45 PDT. Из предварительного анализа вопрос был вызван недавними изменениями, которые были отменены для смягчения последствий. Мы благодарим вас за терпение, пока мы работали над решением проблемы. ** Симптомы клиентов** Пользователи столкнулись с проблемой, когда они получали уведомления о новых сообщениях, но фактические сообщения не появлялись в их приложении чата, если пользователь не обновлял свое мнение. **Работа вокруг** Никто, поскольку вопрос решен.

3. 4 сентября 2026 г. в 03:43 UTCresolved

   ##Инцидентный отчет ##Резюме В пятницу, 28 августа 2026 года, между 10:50 США / Тихий океан и 13:34 США / Тихий океан в течение 2 часов и 44 минут пользователи чата Google столкнулись с задержками в получении входящих сообщений в режиме реального времени в активных потоках разговоров через веб-сайты, настольные и мобильные приложения. В то время как пользователи продолжали получать уведомления о новых сообщениях, содержимое сообщений автоматически не отображалось в активных потоках разговора, пока пользователь вручную не обновил приложение или не отправил ответное сообщение. Для наших уважаемых клиентов Google Workspace мы глубоко сожалеем о перерыве в обслуживании, который вы испытали. Мы принимаем незамедлительные и решительные меры для решения этой проблемы и укрепления наших систем против будущих инцидентов. ##Коренная причина Инцидент произошел во время развертывания глобальной схемы базы данных. Несовместимое изменение схемы базы данных привело к тому, что записи базы данных, необходимые для доставки сообщений, начали выходить из строя. В частности, механизм синхронизации схем, разработанный для обеспечения высокой согласованности между первичным хранением и доставкой живых сообщений, столкнулся с редкой ошибкой состояния гонки. Это привело к тому, что диспетчеры бэкэнд-сообщений пытались писать против неготового состояния схемы, что приводило к сбоям в написании. Поскольку доставка сообщений в реальном времени имела активную зависимость от успешного завершения этих записей перед переносом событий на экраны пользователей, сбой вызвал задержки синхронизации входящих сообщений. Отдельные службы push-уведомлений и основное хранилище сообщений работали независимо и не затрагивались, поэтому пользователи по-прежнему получали оповещения о новых сообщениях, в то время как активные потоки разговоров испытывали задержки. ## Реабилитация и профилактика Проблема была обнаружена с помощью автоматического бэкэнд-оповещения об ошибках отправки, наряду с соответствующими отчетами клиентов. Google Engineering инициировала параллельные рабочие потоки для восстановления сервиса. В 12:44 по США / Тихому океану Google Engineering напрямую смягчила источник проблемы, удалив зависимость, которую доставка живого сообщения имела от неисправной записи базы данных. Это позволило новым вводимым сообщениям обойти несостоявшуюся запись и немедленно возобновить нормальную доставку в реальном времени на экраны пользователей. В 13:00 US/Pacific Engineering остановила и вернула изменение схемы базы данных в свою предыдущую проверенную стабильную версию, восстановив полную совместимость базы данных. К 13:34 по США/Тихоокеанскому региону при обработке очередей задержки синхронизации сообщений в реальном времени вернулись к 0% во всех доменах клиентов. Инженеры подтвердили, что полное состояние службы было восстановлено с нулевой потерей сообщений. Чтобы это не повторилось, мы выполняем следующие профилактические действия: ** Затрудненное внутреннее обнаружение:** Усилить автоматическую валидацию и верификацию для охвата этого конкретного сценария отказа на этапах предварительного производства и внутреннего развертывания. Это направлено на улавливание и смягчение несовместимости схем и синхронизацию краевых случаев внутри компании, прежде чем какой-либо трафик клиентов может быть затронут в будущем. ** Устойчивость к расовым условиям:** Внедрить архитектурные улучшения, чтобы сделать архитектуру синхронизации схемы и доставки сообщений устойчивой к условиям гонки. Это направлено на то, чтобы несоответствия фоновой схемы и синхронизации конфигурации не могли нарушить доставку сообщений в режиме реального времени. ## Подробное описание воздействия Окно удара инцидента произошло между 10:50 US/Pacific и 13:34 US/Pacific в пятницу, 28 августа 2026 года. Эта проблема применяется во всем мире ко всем средам чата Google. ** Google Chat: ** *** Отсроченное сообщение:** Новые сообщения не появлялись в активных потоках разговора автоматически. Пользователи должны были вручную обновить свой клиент или отправить новое сообщение/реакцию, чтобы заставить поток синхронизироваться. ***Сортировка почтовых ящиков и состояний чтения** Справочные действия, такие как обновление непрочитанных значков и перемещение активных пространств в верхнюю часть почтового ящика, имели высокую внутреннюю частоту ошибок и были значительно отложены для пользователей. *** Задержки индексации поиска:** Новые сообщения, отправленные во время окна отключения, застопорились в трубопроводе индексации, испытывая задержки в поиске. **Особые исключения:** ** Без потерь данных:** Ни в какой момент данные клиентов не были потеряны или скомпрометированы. Все сообщения, переданные во время окна инцидента, были надежно захвачены в первичном хранилище и успешно доставлены в потоки разговоров после очистки отставания.

Автоматический перевод официального обновления инцидента.

1. 19 августа 2026 г. в 03:57 UTCresolved

   ** Резюме** Некоторые клиенты могут испытывать медлительность при использовании Google Drive. **Описание** Мы испытываем проблемы с Google Drive начиная со вторника, 2026-08-18 16:58 PDT. Наша инженерная команда в настоящее время работает над потенциальным исправлением, продолжая исследовать полную первопричину. Мы предоставим обновление к вторнику, 2026-08-18 22:00 ПДТ с актуальными деталями. Мы приносим извинения всем, кто пострадал от сбоя. **Симптомы** Пострадавшие клиенты могут испытывать медлительность при использовании Google Drive. **Работа вокруг** Ни одного в это время.

2. 19 августа 2026 г. в 04:59 UTCresolved

   ** Резюме** Многие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при использовании Google Drive. **Описание** Мы испытываем проблемы с Google Drive начиная со вторника, 2026-08-18 16:58 PDT. Наша инженерная команда в настоящее время работает над потенциальным исправлением, продолжая исследовать полную первопричину. Мы предоставим обновление до среды 2026-08-19 00:30 ПДТ с актуальными деталями. **Симптомы** Пострадавшие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при использовании Google Drive. Некоторые клиенты также могут наблюдать 502 ошибки с диском, недоступным в течение короткого периода времени. **Работа вокруг** Ни одного в это время.

3. 19 августа 2026 г. в 06:49 UTCresolved

   ** Резюме** Многие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при доступе к Google Drive. **Описание** Мы испытываем проблемы с Google Drive начиная со вторника, 2026-08-18 16:58 PDT. Наша инженерная команда определила первопричину проблемы и активно работает над стратегией смягчения последствий. Нет ETA для полного разрешения. Мы предоставим обновление до среды 2026-08-19 01:30 ПДТ с актуальными деталями. **Симптомы** Пострадавшие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или 502 ошибки, при этом некоторые пользователи не могут получить доступ к диску. **Работа вокруг** Ни одного в это время.

4. 19 августа 2026 г. в 07:59 UTCresolved

   ** Резюме** Многие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при доступе к Google Drive. **Описание** Мы испытываем проблемы с Google Drive начиная со вторника, 2026-08-18 16:58 PDT. Наша инженерная команда определила первопричину проблемы и активно работает над стратегией смягчения последствий. Нет ETA для полного разрешения. Мы предоставим обновление до среды 2026-08-19 02:00 ПДТ с актуальными деталями. **Симптомы** Пострадавшие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или 502 ошибки, при этом некоторые пользователи не могут получить доступ к диску. **Работа вокруг** Ни одного в это время.

5. 19 августа 2026 г. в 08:54 UTCresolved

   ** Резюме** Многие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при доступе к Google Drive. **Описание** Мы испытываем проблемы с Google Drive начиная со вторника, 2026-08-18 16:58 PDT. Наша инженерная команда активно работает над стратегией смягчения последствий. Нет ETA для полного разрешения. Мы предоставим обновление до среды 2026-08-19 03:00 ПДТ с актуальными деталями. **Симптомы** Пострадавшие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или 502 ошибки, при этом некоторые пользователи не могут получить доступ к диску. **Работа вокруг** Ни одного в это время.

6. 19 августа 2026 г. в 09:54 UTCresolved

   ** Резюме** Многие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при доступе к Google Drive. **Описание** Мы испытываем проблемы с Google Drive начиная со вторника, 2026-08-18 16:58 PDT. Наша инженерная команда активно работает над стратегией смягчения последствий. Нет ETA для полного разрешения. Мы предоставим обновление до среды 2026-08-19 04:30 ПДТ с актуальными деталями. **Симптомы** Пострадавшие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или 502 ошибки, при этом некоторые пользователи не могут получить доступ к диску. **Работа вокруг** Ни одного в это время.

7. 19 августа 2026 г. в 11:26 UTCresolved

   ** Резюме** Многие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при доступе к Google Drive. **Описание** Мы испытываем проблемы с Google Drive начиная со вторника, 2026-08-18 16:58 PDT. Наша инженерная команда активно работает над стратегией смягчения последствий. Нет ETA для полного разрешения. Мы предоставим обновление до среды 2026-08-19 06:00 ПДТ с актуальными деталями. **Симптомы** Пострадавшие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или 502 ошибки, при этом некоторые пользователи не могут получить доступ к диску. **Работа вокруг** Ни одного в это время.

8. 19 августа 2026 г. в 13:05 UTCresolved

   ** Резюме** Многие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или ошибки при доступе к Google Drive. **Описание** Проблема с Google Drive была решена для всех пострадавших клиентов по состоянию на среду 2026-08-19 05:40 PDT. Наши инженерные команды определили, что медлительность была результатом проблемы с локализованной пропускной способностью и маршрутизацией в нашей региональной инфраструктуре. Чтобы восстановить сервис, мы внедрили исправление для облегчения перегрузки сети и ускорили запланированное обновление инфраструктуры в пострадавшем регионе для обеспечения нормального уровня производительности. Мы благодарим вас за терпение, пока мы работали над решением проблемы. **Симптомы** Пострадавшие клиенты в Австралии и Новой Зеландии могут испытывать медлительность или 502 ошибки, при этом некоторые пользователи не могут получить доступ к диску. **Работа вокруг** Сейчас этот вопрос смягчен

9. 20 августа 2026 г. в 20:00 UTCresolved

   Предварительный отчет о происшествии Мы приносим искренние извинения за срыв, который этот инцидент причинил вашему бизнесу. Мы знаем, насколько вы доверяете Google Workspace, и сожалеем о влиянии на вашу производительность. Мы работаем над устранением первопричины и предотвращением этого в будущем. Обратите внимание, что эта информация основана на наших лучших знаниях во время публикации и может быть изменена по мере продолжения нашего расследования. Окончательный отчет о происшествии с превентивными действиями будет опубликован после завершения нашего расследования. Если вы испытали воздействие за пределами того, что перечислено ниже, пожалуйста, свяжитесь с Google Workspace Support, используя справочную статью [**https://support.google.com/a/answer/1047213**] (https://support.google.com/a/answer/1047213). ## Дата/Время проблемы (Все время США/Тихоокеанский регион) Инцидент Начало: 18 Август 2026 16:58 Конец инцидента: 19 августа 2026 05:40 Продолжительность: 12 часов 42 минуты ##Резюме 18 августа 2026 года с 16:58 по 19 августа 2026 года 05:40 US/Pacific, Drive клиенты в Австралии, на Филиппинах и в Новой Зеландии испытали ухудшение производительности и медлительность. За это время пользователи также испытали 502 ошибки. Другие сервисы Google Workspace не пострадали. ## Предварительная корневая причина Google использует многоуровневую глобальную архитектуру балансировки нагрузки и маршрутизации сети для эффективного обслуживания трафика. Чтобы обеспечить справедливое использование и предотвратить перегрузку, распределение пропускной способности управляется путем присвоения трафика конкретным службам. Неправильная конфигурация в атрибуции трафика привела к тому, что использование полосы пропускания было неправильно отнесено к самому уровню балансировки нагрузки интерфейсной сети, а не к службе Drive. Последовательность событий, приводящих к воздействию на клиента, была следующей: * Движение с регионального уровня балансировки нагрузки было неправильно отнесено к инфраструктуре балансировки нагрузки, а не к сервису Drive. Несвязанный трафик привел к тому, что использование пропускной способности сети, связанное с инфраструктурой балансировки нагрузки в этом регионе, превысило его квоту. Системы управления пропускной способностью сети применяли дросселирование к этому трафику для обеспечения соблюдения квот, вызывая серьезные перегрузки сети, влияющие на трафик Drive в этом регионе. Эта загруженность привела к увеличению задержки, замедления и частоты ошибок для пользователей, получающих доступ к Drive в пострадавших регионах. ## Восстановление Инженеры Google были предупреждены о проблеме с помощью автоматизированного мониторинга и наплыва случаев поддержки клиентов, с первоначальными группами реагирования на инциденты, привлеченными к 17:21 США / Тихий океан 18 августа 2026 года. Первоначально инженеры пытались облегчить перегрузку, слив региональный фронтенд-трафик в альтернативное географическое положение, но это оказалось неэффективным и было возвращено. Затем команда смягчила проблему, перенеся региональный трафик на обновленную внутреннюю архитектуру маршрутизации сети, которая правильно установила атрибуцию трафика для Drive. Нормальные операции были полностью восстановлены после перехода 100% регионального трафика на обновленную сетевую архитектуру. ## Описание воздействия В период с 18 августа 2026 года в 16:58 по тихоокеанскому времени и 19 августа 2026 года в 05:40 по тихоокеанскому времени пользователи Google Drive в Австралии, на Филиппинах и в Новой Зеландии испытали серьезную задержку, ухудшили производительность и 502 ошибки. В течение этого примерно 12-часового и 42-минутного окна пострадавшие клиенты могли наблюдать значительную медлительность или ошибки при попытке получить доступ к Google Drive или списку файлов через редакторы (например, [docs.google.com] (http: / /docs.google.com)), причем начальное время загрузки значительно задерживалось. Проблема была полностью смягчена по состоянию на 19 августа 2026 года в 05:40 по США/Тихоокеанскому региону, и нормальное обслуживание было восстановлено.

10. 24 августа 2026 г. в 16:31 UTCresolved

    # Incident Report ## Summary On Tuesday, 18 August 2026 at 16:58 US/Pacific, an incident affecting Google Drive occurred for a duration of 12 hours and 42 minutes. Customers located in Australia, Philippines and New Zealand experienced severe latency, sporadic loading failures, and errors when accessing Google Drive.  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. Other Google Workspace services were not affected. ## Root Cause Google utilizes a multi-tiered global load balancing and network routing architecture to serve traffic efficiently. To ensure fair use and prevent congestion, bandwidth allocation is managed by attributing traffic to specific downstream services. A misconfiguration in the attribution of traffic caused the bandwidth usage to be incorrectly attributed to the frontend network load balancing tier itself, rather than to the Drive service. The sequence of events leading to customer impact was as follows: * Traffic from the regional load balancing tier was incorrectly attributed to the load balancing infrastructure rather than the Drive service. * Unrelated traffic caused network bandwidth usage attributed to the load balancing infrastructure in this region to exceed its quota. * Network bandwidth management systems applied throttling to this traffic to enforce quotas, causing severe network congestion affecting Drive traffic in this region. * This congestion led to increased latency, slowness, and error rates for users accessing Drive in the affected regions. ## Remediation and Prevention Google engineers were alerted to the issue via automated monitoring and an influx of customer support cases, with initial incident response teams engaged by 17:21 US/Pacific on 18 August , 2026\. Engineers initially attempted to alleviate the congestion by draining regional frontend traffic to an alternate geographic location, but this proved ineffective and was reverted. The team then mitigated the issue by migrating regional traffic to an upgraded internal network routing architecture, which correctly set the traffic attribution for Drive. Normal operations were fully restored at 05:40 once 100% of the regional traffic was migrated to the upgraded network architecture. To prevent a recurrence of this issue, our engineering teams are undertaking the following structural preventative actions: * **Resilient Network Protocol Migration:** We are expediting the complete migration of all regional frontend traffic to the newer, resilient network routing protocol to ensure accurate bandwidth attribution under all congestion scenarios. * **Delegation Root Cause Remediation:** We are addressing the underlying mechanism that caused the incorrect delegation and analyzing similar cases across the fleet to ensure it does not reoccur. ## Detailed Description of Impact From 18 August 2026, 16:58 to 19 August 2026, 05:40 US/Pacific for a duration of 12 hours, 42 minutes, Google Drive users in Australia, Philippines and New Zealand experienced severe performance degradation, including high latency and errors accessing Drive or listing files via Editors. Service was fully restored as of 19 August, 05:40 US/Pacific. **Google Drive:** * Elevated Latency: Users experienced extreme slowness when loading the Drive interface or accessing files, with initial data retrieval times heavily delayed. * Loading Failures and Errors: Many user requests timed out or returned HTTP 502 errors due to the aggressive network throttling dropping the connections. **Scope Exclusion:** * Customers accessing Google Drive from outside the Australia, Philippines and New Zealand regions were largely unaffected by this localized throttling event. * Other Google Workspace applications not reliant on this specific routing path remained stable during the incident window.

Автоматический перевод официального обновления инцидента.

1. 18 августа 2026 г. в 19:35 UTCresolved

   ** Резюме:** Исследование проблем доступа с новой домашней страницей Classroom. **Описание:** Мы расследуем сообщения о проблемах с доступом к новой домашней странице Classroom, начиная с четверга, 2026-08-13. Наша инженерная команда в настоящее время работает над потенциальным исправлением, продолжая исследовать полную первопричину. Мы предоставим обновление к вторнику, 2026-08-18 13:00 ПДТ с актуальными деталями. Мы приносим извинения всем, кто пострадал от сбоя. **Симптомы:** Администраторы и некоторые преподаватели могут столкнуться с ошибками при доступе к новой домашней странице Classroom. **Работа вокруг:** Пользователи по-прежнему должны иметь возможность перемещаться по другим видам с левой панели интерфейса.

2. 18 августа 2026 г. в 20:00 UTCresolved

   ** Резюме:** Устранение проблем с доступом к новой домашней странице Classroom. **Описание:** В настоящее время работа по смягчению последствий ведется нашей инженерной командой. Ожидается, что смягчение последствий завершится во вторник, 2026-08-18 14:00 ПДТ. Более подробную информацию мы предоставим во вторник, 2026-08-18 14:15 ПДТ. **Симптомы:** Администраторы и некоторые преподаватели могут столкнуться с ошибками при доступе к новой домашней странице Classroom. **Работа вокруг:** Пользователи по-прежнему должны иметь возможность перемещаться по другим видам с левой панели интерфейса.

3. 18 августа 2026 г. в 20:27 UTCresolved

   ** Резюме:** Устранение проблем доступа для администраторов рабочего пространства с веб-страницей Classroom. **Описание:** Наши инженеры определили причину и ведутся работы по смягчению последствий. Ожидается, что развертывание мер по смягчению последствий займет несколько часов. Более подробную информацию мы предоставим в среду, 2026-08-19 8:00 ПДТ. **Симптомы:** Администраторы рабочего пространства могут испытывать ошибки при доступе к домашней странице Classroom. Оставшаяся функциональность класса остается незатронутой. Мобильное приложение Classroom и API Classroom не затронуты этой проблемой. **Работа вокруг:** Все остальные страницы не затронуты, и администраторы могут перемещаться на другие страницы, используя левую панель на интерфейсе. Администраторы рабочего пространства могут создавать классы без каких-либо проблем. Администраторы рабочего пространства также могут просматривать курсы, на которых они находятся, перейдя на https://classroom.google.com/h/tv

4. 18 августа 2026 г. в 23:02 UTCresolved

   ** Резюме** [Смягчено] Проблемы доступа для администраторов рабочего пространства с домашней страницей Classroom. **Описание** Проблема с Classroom была решена для всех пострадавших пользователей по состоянию на вторник, 2026-08-18 15:30 PDT. Из предварительного анализа, проблема была вызвана недавним изменением, которое вызвало несоответствие разрешения, наша инженерная команда выкатила исправление, чтобы смягчить воздействие. Мы благодарим вас за терпение, пока мы работали над решением проблемы. **Симптомы** Администраторы рабочего пространства могут столкнуться с ошибками при доступе к домашней странице Classroom. Оставшаяся функциональность класса осталась незатронутой. Мобильное приложение Classroom и API Classroom не были затронуты этой проблемой. **Работа вокруг** Нет, поскольку вопрос решен

Автоматический перевод официального обновления инцидента.

1. 30 июня 2026 г. в 11:56 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 05:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** None at this time.

2. 30 июня 2026 г. в 12:17 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** None at this time.

3. 30 июня 2026 г. в 12:28 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** Customers can continue to use the portal to add comments / notes.

4. 30 июня 2026 г. в 13:28 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** Customers can continue to use the portal to add comments / notes.

5. 30 июня 2026 г. в 14:06 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. **Workaround** Customers can continue to use the portal to add comments / notes.

6. 30 июня 2026 г. в 14:51 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Tuesday, 2026-06-30 08:45 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

7. 30 июня 2026 г. в 15:48 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Tuesday, 2026-06-30 09:45 PDT. We will provide more information by Tuesday, 2026-06-30 10:00 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

8. 30 июня 2026 г. в 16:36 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineering teams have shifted focus to replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. While there is currently no specific ETA for the email replay to finish, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 11:00 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

9. 30 июня 2026 г. в 17:53 UTCresolved

   **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 12:15 PDT. **Symptoms** Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

10. 30 июня 2026 г. в 19:03 UTCresolved

    **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 17:00 PDT. **Symptoms** Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

11. 1 июля 2026 г. в 00:44 UTCresolved

    **Title** Inbound emails from customers to Google Support are experiencing issues. **Description** The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 21:30 PDT. **Symptoms** Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. **Workaround** Customers can continue to use the portal to add comments / notes.

12. 1 июля 2026 г. в 04:58 UTCresolved

    **Title** [Resolved] Inbound emails from customers to Google Support were experiencing issues. **Description** The issue with inbound emails to Google Cloud Support has been resolved for all affected customers as of Tuesday, 2026-06-30 20:45 PDT. From preliminary analysis, the engineering team identified a recent change which was preventing incoming emails from being processed. We have successfully rolled back the change to mitigate the impact. Backlog processing of all the affected emails is now complete. We thank you for your patience while we worked on resolving the issue. **Symptoms** Inbound emails from customers to Google Support were experiencing issues. Case creation and updates continued to work without any issues. **Workaround** None as the issue is resolved.

1. 22 июня 2026 г. в 22:28 UTCresolved

   **Title** Some consumer Google Voice users are experiencing account suspensions. **Description** We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified the root cause and is actively working to mitigate the issue. We will provide an update by Monday, 2026-06-22 17:30 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Some consumer Google Voice users are experiencing account suspensions

2. 23 июня 2026 г. в 00:29 UTCresolved

   **Title** Some consumer Google Voice users are experiencing account suspensions. **Description** We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified a mitigation strategy and is actively working on mitigation. We do not have an ETA for mitigation at this time. We will provide an update by Monday, 2026-06-22 22:30 PDT with current details. **Symptoms** Some consumer Google Voice users are experiencing account suspensions **Workaround** None at this time.

3. 23 июня 2026 г. в 01:08 UTCresolved

   **Title** Some consumer Google Voice users experienced account suspensions. **Description** The issue with Google Voice has been resolved for all affected users as of Monday, 2026-06-22 17:46 PDT Our engineers have mitigated the issue by rolling back to a previous version and reinstating suspended accounts. We thank you for your patience while we worked on resolving the issue. **Symptoms** Some consumer Google Voice users experienced account suspensions **Workaround** The issue is now mitigated.

1. 10 июня 2026 г. в 12:40 UTCresolved

   **Title** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 06:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Workaround** None at this time.

2. 10 июня 2026 г. в 13:21 UTCresolved

   **Title** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Gemini App in Workspace and Gemini Side Panel (Gemini in Workspace) customers are experiencing “Something Went Wrong” errors. **Workaround** None at this time.

3. 10 июня 2026 г. в 15:10 UTCresolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team continues to investigate the issue and identify a mitigation strategy. We will provide an update by Wednesday, 2026-06-10 09:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong” errors.: * Gemini app in Workspace includes the following platforms; * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

4. 10 июня 2026 г. в 16:24 UTCresolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has identified a mitigation which is currently in progress. We do not have an ETA for mitigation at this time. We will provide an update by Wednesday, 2026-06-10 12:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

5. 10 июня 2026 г. в 18:37 UTCresolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has applied mitigations to reduce impact and continues to investigate the root cause. We are seeing signs of recovery and will continue to monitor progress. We will provide an update by Wednesday, 2026-06-10 14:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

6. 10 июня 2026 г. в 20:19 UTCresolved

   **Title** Gemini App in Workspace customers are experiencing “Something Went Wrong” errors. **Description** We are experiencing an issue with Gemini beginning on Wednesday, 2026-06-10 03:26 PDT. Our engineering team has applied mitigations to reduce impact and confirmed the majority of users are no longer observing impact as of Wednesday, 2026-06-10 10:30 PDT. We will continue to monitor the service for stability. We will provide an update by Wednesday, 2026-06-10 20:30 PDT with current details. **Symptoms** The following services are experiencing “Something Went Wrong 1099 or 1076” errors: Gemini app in Workspace includes the following platforms: * Web, MacOS, iOS and Android * Gemini in Chrome **Workaround** None at this time.

7. 11 июня 2026 г. в 01:07 UTCresolved

   **Title** Gemini App in Workspace users were experiencing “Something Went Wrong” errors. **Description** The issue with Gemini has been resolved for all the affected users as of Wednesday, 2026-06-10 10:30 US/Pacific. From preliminary analysis, the issue was triggered by a performance issue in our backend database which impacted the retrieval of Gemini App tools catalog. Our engineers mitigated the issue by optimizing the load distribution across our backend database fleet. We thank you for your patience while we worked on resolving the issue. **Symptoms** Affected users may have seen "Something went wrong" errors (codes 1099, 1076) when prompting Gemini while using the following services. Gemini App in Workspace includes the following platforms: - Web, MacOS, iOS and Android - Gemini in Chrome **Workaround** None as the issue is now resolved.

8. 12 июня 2026 г. в 11:14 UTCresolved

   # 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. A final Incident Report with preventative actions will be posted once our investigation is complete. 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](https://support.google.com/a/answer/1047213). ## Date/Time of the Issue (All time US/Pacific) Incident Start: 10 June 2026 03:20 Incident End: 10 June 2026 10:25 Duration: 7 hours, 5 minutes ## Summary On Wednesday, 10 June 2026 03:20 US/Pacific, an incident occurred affecting the availability of Gemini services across all surfaces, including web, mobile (iOS and Android), and integrations within Google Chrome. The incident resulted in an elevated error rate for 7 hours and 5 minutes. ## Preliminary Root Cause The disruption was caused by extreme read contention within the foundational database service that manages tool deployment metadata. The primary cause was back-pressure on specific database replicas that experienced high loads. The issue was made worse because of an index design issue within the database where a column used for tracking deployment expirations contained a high volume of rows with a similar fixed value. This resulted in a condition where traffic was concentrated on a very small number of database instances, overwhelming them. Additionally, the service utilized an in-memory cache with a short Time To Live (TTL) of only one minute, requiring frequent database refreshes. The failure sequence was as follows: 1. **Technical Trigger:** The database service became overloaded, causing back-pressure on specific replicas. 2. **Systemic Effect:** An application level caching layer configuration is set to a short 1-minute expiration window for deployed tools. This short window, combined with an indexing anomaly where specific metadata fields containing empty values were clustered on a single database partition. The failed DB queries resulted in failure to populate application level cache. 3. **Contention and Latency:** As request volume increased, the internal tool management service experienced >10x surge in database calls because the cache hit rate dropped significantly. 4. **Failure State:** The underlying storage layer reached its transaction limits, with database response success rates dropping as low as 10% on the affected partitions. ## Remediation The issue was detected by internal real-time monitoring alerts indicating high processing error rates. Engineering teams performed several targeted actions to restore the service: * **Throttling:** Applied rate limiting to the most affected database instances to allow internal caches to recover. * **Index Redistribution:** Gradually redistributed fixed index values in the database to random values in a specific range, effectively spreading the load across multiple instances. * **Cache Policy Update:** Deployed a configuration change to increase the in-memory cache Time To Live (TTL) from 1 minute to 20 minutes, significantly reducing database load. * **Deadline Adjustment:** Shortened the Remote Procedure Call (RPC) deadlines for database queries to prevent request pile-ups during periods of high latency. ## Description of Impact The impact window occurred between 03:20 US/Pacific and 10:25 US/Pacific on 10 June 2026. **Gemini App (Web and Mobile):** * Users experienced a 50% error rate when attempting to send prompts, receiving "Something went wrong" messages. The issue affected both consumer accounts and enterprise Google Workspace customers . **Integrations:** * **Google Chrome Integration:** The Gemini Side Panel and integrated conversational features encountered persistent timeouts.

9. 16 июня 2026 г. в 17:41 UTCresolved

   # Incident Report ## Summary On Wednesday, June 10, 2026, at 03:30 US/Pacific, an incident occurred affecting the availability of Gemini services across all surfaces, including web, mobile (iOS and Android), and integrations within Google Chrome. The incident resulted in an elevated error rate for approximately 6 hours and 55 minutes, with full service restoration confirmed after a total duration of 14 hours and 49 minutes. We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future. ## Root Cause The disruption was caused by extreme read contention within the foundational database service that manages tool deployment metadata. The primary cause was an index design issue within the database where a column used for tracking deployment expirations contained a high volume of rows with similar values. This resulted in "hotspotting," where traffic was concentrated on a very small number of database shards, overwhelming them. Additionally, the service utilized an in-memory cache with a very short Time To Live (TTL) of only one minute, requiring frequent database refreshes. The failure sequence was as follows: 1. **Technical Trigger:** The trigger was an upward spike in the Queries Per Second (QPS) from the frontend. The underlying system was already running close to maximum usage and the incoming QPS crossed a tipping threshold beyond which the underlying spanner started getting overloaded. 2. **Systemic Effect:** This short window, combined with an indexing anomaly where specific metadata fields containing empty values were clustered on a single database partition, led to a "hot shard" condition. 3. **Contention and Latency:** As request volume increased, the internal tool management service experienced a more than 10x surge in database calls because the cache hit rate dropped significantly. 4. **Failure State:** The underlying storage layer reached its capacity for handling incoming queries, and database failure rates skyrocketed to 60%. This led to cache hit rate dropping down to 50%. Automated validation failed to prevent this because the indexing strategy did not sufficiently account for the concentration of data rows when specific identifiers were absent. ## Remediation and Prevention The issue was detected by internal real-time monitoring alerts indicating high processing error rates. Engineering teams performed several targeted actions to restore the service: * **Throttling:** Applied Rate Access Control Lists (RateACLs) to the most affected database shards to allow internal caches to recover. * **Index Redistribution:** Gradually redistributed common values in the database index to random values in a specific target range, effectively spreading the load across multiple shards. * **Cache Policy Update:** Deployed a configuration change to increase the in-memory cache Time To Live (TTL) from 1 minute to 20 minutes, significantly reducing database load. * **Deadline Adjustment:** Shortened the Remote Procedure Call (RPC) deadlines for database queries to prevent request pile-ups during periods of high latency. ## Prevention To prevent a recurrence, Google engineering will be implementing the following actions: * **Index Design Standards:** Restructure of database index to prevent "hotspotting". * **Adaptive Cache Tuning:** Implement more robust cache policies that prevent load amplification during periods of backend stress. * **Enhanced Hotspot Monitoring:** Deploy improved monitoring and alerting specifically designed to detect uneven database load distribution before it impacts user traffic. * **Service Resiliency:** Implement advanced load protection mechanisms, such as smart task resizing and query coalescing for preventing spanner overloads. ## Detailed Description of Impact The impact window occurred between 03:30 US/Pacific and 10:25 US/Pacific on June 10, 2026\. **Gemini App (Web and Mobile):** * High Failure Rates: Users experienced a 50% error rate when attempting to send prompts, receiving "Something went wrong" messages . * Service Unavailability: The issue affected both consumer accounts and enterprise Google Workspace customers . * Enterprise Google Workspace Users encountered disruptions when attempting to attach assets from Google Drive within the web application (gemini.google.com). Affected users observed the "Add from Drive" functionality to be visually disabled and unresponsive following interaction with the "+" prompt. **Integrations:** * **Google Chrome Integration:** The Gemini Side Panel and integrated conversational features encountered persistent timeouts.

1. 31 мая 2026 г. в 04:59 UTCresolved

   **Title** Multiple Workspace Products experiencing Issues. **Description** We are experiencing an issue with Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, Google Docs beginning on Saturday, 2026-05-30 20:28 PDT. Our engineering team continues to investigate the issue. We will provide an update by Saturday, 2026-05-30 22:10 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms** Customers may experience issues loading the application/ intermittent high latency or errors while using the application. **Workaround** None at this time.

2. 31 мая 2026 г. в 05:11 UTCresolved

   **Title** [Mitigated] Multiple Workspace Products experienced Issues. **Description** The issue with Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, Google Docs has been resolved for all affected users as of Saturday, 2026-05-30 21:30 PDT. We thank you for your patience while we worked on resolving the issue. **Symptoms** Customers may have experienced issues loading the application/ intermittent high latency or errors while using the application. **Workaround** None at this time as the issue stands mitigated

3. 2 июня 2026 г. в 03:50 UTCresolved

   # Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Workspace, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced impact outside of what is listed below, please reach out to Google Workspace Support using help article https://support.google.com/a/answer/1047213 ## Date/Time of the Issue (All time US/Pacific) Incident Start: 30 May 2026 20:15 Incident End: 30 May 2026 21:30 Duration: 1 hour, 15 minutes ## Summary Starting on Saturday, 30 May 2026 at 20:15 US/Pacific, multiple Google Workspace products experienced service disruptions for a duration of 1 hour and 15 minutes. The affected services included Google Voice, Google Meet, Google Drive, Google Chat, Google Calendar, Gmail, and Google Docs. During this incident, customers encountered difficulties loading applications, as well as intermittent high latency or errors. ## Preliminary Root Cause The disruption originated from failures in a regional infrastructure component responsible for Google's distributed lock service. This critical system facilitates resource synchronization, manages shared data access, and coordinates background tasks for numerous Google services. A high volume of rapid configuration changes triggered the regional failure, preventing Workspace servers from reliably processing traffic. To mitigate the impact, Google Workspace traffic was redirected to alternative regions. Google engineers have begun a full root cause analysis and will provide additional information once it is available. ## Remediation Google engineers were alerted to the issue via automated monitoring at 20:28 US/Pacific on Saturday, 30 May 2026, and immediately began an investigation. The investigation identified elevated error rates and high latency affecting multiple Google Workspace backend services. Upon investigation our engineering team confirmed errors were primarily originating from some regional servers due to coordination service failures in the region. To mitigate the impact, Google engineers redirected traffic away from the affected servers. ## Description of Impact Affected customers encountered difficulties loading applications or experienced failures when performing tasks within the following products: * Gmail * Google Calendar * Google Chat * Google Docs * Google Drive * Google Meet * Google Voice

4. 4 июня 2026 г. в 20:11 UTCresolved

   # Incident Report ## Summary Starting at 20:15 US/Pacific on Saturday, 30 May 2026, various Google Workspace services encountered service-level disruptions lasting approximately 75 minutes. The scope of impact spanned several products, specifically affecting Gmail, Google Docs, Drive, Calendar, Chat, Meet, and Google Voice. Throughout the duration of this event, users faced obstacles while attempting to initialize applications, in addition to experiencing sporadic instances of elevated latency and request failures. Google offers a sincere apology for the operational interference this issue introduced to your organization. Recognizing the critical nature of Google Cloud to your daily operations, we deeply regret any resulting loss in productivity. Engineering efforts are currently focused on remediating the underlying cause to ensure future stability. ## Root Cause The disruption originated from failures in a critical cluster infrastructure component responsible for Google's service discovery and configuration management systems. This system facilitates resource synchronization, manages shared data access, and coordinates background tasks for numerous Google services. A high volume of rapid configuration changes triggered the regional failure in Workspace Services, preventing Workspace servers from reliably processing traffic. To mitigate the impact, Google Workspace traffic was redirected to alternative regions. ## Remediation and Prevention Google engineers were alerted to the issue via automated monitoring on Saturday, 30 May 2026 at 20:28 US/Pacific and immediately began an investigation. The investigation identified elevated error rates and high latency affecting multiple Google Workspace backend services. Upon investigation our engineering team confirmed errors were primarily originating from some regional servers due to coordination service failures in the region. To mitigate the impact, Google engineers redirected traffic away from the affected servers. Google is committed preventing a repeat of this issue in the future and is completing the following actions: - Prevent recurrence of this incident by rolling out the fix for the latent encryption library issue, which improves the handling of internal log compaction compactions during active file writes, to prevent recurrence of the cluster instability. - Investigating additional resilience in our database layer. ## Detailed Description of Impact On 30 May 2026 from 20:15 to 21:30 US/Pacific, affected customers encountered difficulties while loading applications or experienced failures when performing tasks within the following products: - Gmail - Google Calendar - Google Chat - Google Docs - Google Drive - Google Meet - Google Voice

1. 21 мая 2026 г. в 15:37 UTCresolved

   **Summary** Gmail users are experiencing delayed delivery of messages sent from the bank.in domains. **Description** We are experiencing an issue with Gmail beginning on Thursday, 2026-05-21 at 00:00 PDT. Mitigation efforts are currently underway by our engineering team. We will provide the next update by Thursday, 2026-05-21 at 09:30 PDT. **Diagnosis / Customer Symptoms** Gmail users are experiencing delayed delivery of messages sent from the bank.in domains. **Workaround** None at this time.

2. 21 мая 2026 г. в 16:09 UTCresolved

   **Summary** Gmail users experienced delayed delivery of messages sent from the bank.in domains. **Description** Our internal telemetry shows that the issue with Gmail has been resolved for all affected users as of Thursday, 2026-05-21 at 08:47 US/Pacific. Our engineering team is actively monitoring the system to ensure continued stability. **Diagnosis / Customer Symptoms** Customers should expect new messages to be delivered normally, older emails could take some time as the senders continue to retry. **Workaround** This issue is now mitigated.

1. 20 мая 2026 г. в 01:07 UTCresolved

   **Summary** NotebookLM customers are experiencing an issue where account tiers are being incorrectly downgraded. Affected Ultra & Pro tier users are seeing Free tier features. **Description** We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 20:30 PDT with current details. **Customer Symtomps** Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. **Workaround** None at this time

2. 20 мая 2026 г. в 03:20 UTCresolved

   **Title** NotebookLM customers are experiencing an issue where all premium account tiers are being incorrectly downgraded to free. **Description** We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 22:00 PDT with current details. **Symptoms** Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. **Workaround** None at this time.

3. 20 мая 2026 г. в 04:38 UTCresolved

   **Title** NotebookLM customers may have experienced an issue where all premium account tiers are being incorrectly downgraded to free. **Description** The issue with NotebookLM has been resolved for all affected users as of Tuesday, 2026-05-19 21:04 PDT. From preliminary analysis, the issue was triggered by a recent software update resulting in accounts on premium plans being incorrectly recognized as free accounts. The issue was mitigated by restoring the system to a previous stable state, which successfully reinstated the appropriate service tiers for all affected accounts. We thank you for your patience while we worked on resolving the issue. **Symptoms** Customers may have noticed lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. **Workaround** None at this time.

1. 13 мая 2026 г. в 17:55 UTCresolved

   **Summary** Some Cameyo by Google customers could not start their sessions after rolling out the new channel version. **Description** We were experiencing an issue with Cameyo by Google, beginning on Tuesday, 12 May 2026 09:01 US/Pacific. The issue was mitigated on Tuesday, 12 May 2026 15:16 US/Pacific by restarting the RAP system service, and performing full server reboots. From preliminary investigation, this was caused by a faulty code for logging improvement on the Player VMs. Log files were unexpectedly duplicated until the disk was full leading to the session failures. Some customers were recovered automatically after the channel binaries were rolled back, while the others were required to restart their VMs manually. Currently, the issue is fully mitigated and change is rolled back. We apologise to those who were impacted by this issue. **Customer Symptoms** The customers were experiencing an issue that couldn’t connect to the Player VMs normally. The disk utilization on the affected VMs reaches 99% or even 100%. **Workaround** Not needed because all affected servers have been mitigated.

1. 16 мая 2026 г. в 02:05 UTCresolved

   **Summary** Gmail Android users using Microsoft Exchange Online may fail to log in due to authentication issues. **Description** We are experiencing an issue with Gmail beginning on Saturday 2026-05-06. Our engineering team continues to investigate the issue. We will provide more information by Monday, 2026-05-18 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Impacted users may experience authentication failures while logging in to Microsoft Exchange Online through Gmail App on Android devices. **Workaround** Affected users can use Microsoft web app to access the Inbox.

2. 18 мая 2026 г. в 21:45 UTCresolved

   **Summary** Gmail Android users using Microsoft Exchange Online accounts may fail to Log In and Sync due to authentication issues. **Description** We are experiencing an issue with Gmail Android client connecting with Microsoft Exchange Online accounts beginning on Saturday 2026-05-06. Our engineering team has identified the issue and is actively working on rolling out a fix to unblock all the affected customers. We will provide more information by Tuesday, 2026-05-19 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Affected users can use Microsoft Web App to access the Inbox.

3. 19 мая 2026 г. в 21:55 UTCresolved

   **Summary** Gmail Android users using Microsoft Exchange Online accounts may fail to Log In and Sync due to authentication issues. **Description** We are experiencing an issue with Gmail Android client connecting with Microsoft Exchange Online accounts beginning on Saturday 2026-05-06. Our engineering team has identified the issue and started rolling out a new version of Gmail Android release that contains the fix to unblock users. Users already on the new app version will be able to Log In and Sync their accounts successfully. We will provide more information by Thursday, 2026-05-21 17:00 US/Pacific with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Affected users can use Microsoft Web App to access the Inbox.

4. 22 мая 2026 г. в 00:04 UTCresolved

   **Summary** Gmail Android users using Microsoft Exchange Online accounts may fail to Log In and Sync due to authentication issues. **Description** Our engineering team identified the issue and released a new version of the Gmail Android application (version 2026.05.11) to the Google Play Store, which contains a fix to unblock affected users. If you are currently encountering this issue, please upgrade to the latest version of the Gmail Android app. Users operating on the new app version should be able to successfully log in and sync their accounts. We will provide more information by Friday, 2026-05-22 17:00 US/Pacific with current details. We thank you for your patience while we are working on resolving the issue. **Symptoms** Impacted users may experience authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Affected users could update to the latest version of Gmail Android (version 2026.05.11) in Google Play Store.

5. 22 мая 2026 г. в 18:57 UTCresolved

   **Summary** [Resolved] Gmail Android users utilizing Microsoft Exchange Online accounts experienced authentication and synchronization failures. **Description** The issue with Gmail has been resolved in the new Gmail android release (version 2026.05.11) as of Thursday, 2026-05-21 15:00 PDT. Our engineering team identified the issue and released a new version of the Gmail Android application to the Google Play Store, which contains a fix to unblock affected users. If you are currently encountering this issue, please upgrade to the latest version of the Gmail Android app. Users operating on the new app version will be able to successfully log in and sync their accounts. We thank you for your patience while we worked on resolving the issue. **Symptoms** Impacted users might have experienced authentication and sync failures while using Microsoft Exchange Online accounts through Gmail App on Android devices. **Workaround** Update to the latest version of Gmail Android (2026.05.11) in Google Play Store.

1. 5 мая 2026 г. в 23:35 UTCresolved

   **Summary** Investigating elevated error rates with Gemini conversations. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Tuesday, 2026-05-05 20:30 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

2. 6 мая 2026 г. в 03:22 UTCresolved

   **Summary** Investigating elevated error rates with Gemini conversations. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2026-05-06 09:00 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

3. 6 мая 2026 г. в 19:11 UTCresolved

   **Summary** Gemini conversations are experiencing elevated error rates. **Description** Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-05-07 17:00 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

4. 7 мая 2026 г. в 23:52 UTCresolved

   **Summary** Gemini conversations are experiencing elevated error rates. **Description** Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-05-07 20:30 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

5. 8 мая 2026 г. в 01:00 UTCresolved

   **Summary** Gemini conversations may have experienced elevated error rates. **Description** The issue with Gemini has been resolved for all affected users as of Thursday, 2026-05-07 17:00 PDT. The issue was triggered due to a combination of insufficient database resources, and application issues. The database capacity issues were resolved, and further code changes are being made to mitigate the application issues. We thank you for your patience while we worked on resolving the issue. **Symptoms** Affected customers may have experienced the "Something went wrong(13)" error message in their Gemini conversations.

6. 8 мая 2026 г. в 05:16 UTCresolved

   **Summary** Gemini conversations are experiencing elevated error rates. **Description** Our engineering team has determined that further investigation is required to mitigate the issue. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-05-08 01:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

7. 8 мая 2026 г. в 07:29 UTCresolved

   **Summary** Gemini conversations may experience elevated error rates. **Description** Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 04:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

8. 8 мая 2026 г. в 10:23 UTCresolved

   **Summary** Gemini conversations may experience elevated error rates. **Description** Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 09:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

9. 8 мая 2026 г. в 15:53 UTCresolved

   **Summary** Gemini conversations may experience elevated error rates. **Description** Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact. We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively. We will provide more information by Friday, 2026-05-08 12:00 PDT. **Symptoms** Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

10. 8 мая 2026 г. в 18:58 UTCresolved

    **Summary** Gemini conversations may have experienced elevated error rates. **Description** The issue with Gemini has been resolved for all affected users as of Friday, 2026-05-08 11:53 PDT. The issue was triggered due to a combination of insufficient database resources, and application bugs. The database capacity issues were resolved, and further code changes are being made to mitigate the application issue. We thank you for your patience while we worked on resolving the issue. **Symptoms** Affected customers may have experienced "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.

1. 29 апреля 2026 г. в 19:17 UTCresolved

   **Title:** Investigating issues with Classroom. **Description:** We are experiencing an issue with Classroom beginning at Wednesday, 2026-04-29 11:30 PDT. Our engineering team continues to investigate the issue. We will provide more information by Wednesday, 2026-04-29 13:00 PDT. **Symptoms:** Affected users may experience issues accessing classroom. **Workaround:** No workarounds available at this time.

2. 29 апреля 2026 г. в 19:53 UTCresolved

   **Title:** Investigating issues with Classroom. **Description:** Our engineering team has identified the cause and working on mitigation of the issue . The mitigation is expected to complete by Wednesday, 2026-04-29 15:00 PDT. We will provide more information by Wednesday, 2026-04-29 15:15 PDT. **Symptoms:** Affected users may experience issues accessing classroom. **Workaround:** No workarounds available at this time.

3. 29 апреля 2026 г. в 20:13 UTCresolved

   **Title:** Investigating issues with Classroom. **Description:** A fix has been deployed, and services have stabilized for the majority of users. We are aware that a small subset of users may still encounter errors. Our engineering team is actively working on a secondary resolution to address these remaining users. Full resolution for remaining users is expected to complete by Wednesday, 2026-04-29 14:00 PDT. We will provide an update by Wednesday, 2026-04-29 14:15 PDT with current details. **Symptoms:** Affected users may experience issues accessing classroom. **Workaround:** No workarounds available at this time.

4. 29 апреля 2026 г. в 21:07 UTCresolved

   **Title:** An issue with Classroom is resolved. **Description:** A fix has been deployed, and services have stabilized for all users. The issue with Google Classroom has been resolved for all affected users as of Wednesday, 2026-04-29 13:45 PDT. The issue was due to an internal software migration. Our engineers have mitigated the issue by rolling back the migration for impacted users. We thank you for your patience while we worked on resolving the issue. **Symptoms:** Affected users may have experienced issues accessing the classroom. **Workaround:** The issue is resolved.

1. 28 апреля 2026 г. в 15:20 UTCresolved

   **Title:** Investigating issues with slow loading of AppSheet **Description:** We are experiencing an issue with AppSheet beginning at Tuesday, 2026-04-28 00:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-04-28 09:00 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms:** Affected customers would experience slow loading times and internal server errors for AppSheet apps. **Workaround:** None at this time.

2. 28 апреля 2026 г. в 16:00 UTCresolved

   **Title:** Investigating issues with slow loading of AppSheet. **Description:** Our engineering team has implemented a fix and system telemetry indicates that latency and error rates have returned to normal levels. We are continuing to monitor the environment closely to ensure full stability. We will provide an update by Tuesday, 2026-04-28 10:30 PDT with current details. We apologize to all who are affected by the disruption. **Symptoms:** Affected customers would experience slow loading times and internal server errors for AppSheet apps. **Workaround:** None at this time.

3. 28 апреля 2026 г. в 16:50 UTCresolved

   **Title:** Mitigated issues with slow loading of AppSheet apps. **Description:** The issue with AppSheet has been resolved for all affected users as of Tuesday, 2026-04-28 08:50 PDT. We thank you for your patience while we worked on resolving the issue. **Symptoms:** Affected customers would have experienced slow loading times and internal server errors for AppSheet apps.

1. 10 апреля 2026 г. в 10:07 UTCresolved

   **Summary** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Description** We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 04:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

2. 10 апреля 2026 г. в 10:55 UTCresolved

   **Summary** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Description** We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 05:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

3. 10 апреля 2026 г. в 11:27 UTCresolved

   **Summary** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Description** Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-04-10 09:00 PDT. **Customer Symptoms** Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

4. 10 апреля 2026 г. в 15:06 UTCresolved

   **Summary** Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. **Description** The issue with Admin Console has been resolved for all affected users as of Friday, 2026-04-10 07:50 PDT. Suspected CL have been rolled back and we are seeing in our graphs errors rate have gone down. Customers also confirmed that issues have been mitigated. We thank you for your patience while we worked on resolving the issue. **Customer Symptoms** Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. **Workaround** Below steps should be performed by Admin as the workaround: * Admin should revoke the key. * Admin to create the verification code to sign-in. * The user should sign-in using Backup verification code and then re-enrolls the security key.

1. 8 апреля 2026 г. в 22:22 UTCresolved

   **Summary** AppSheet customers are experiencing redirection to asia-southeast.appsheet.com instead of their intended application URLs. **Description** Beginning on Wednesday, 2026-04-08 14:05 PDT, we are experiencing an issue with AppSheet that caused users to be erroneously redirected to the asia-southeast region. Our engineers have identified the cause was due to a recent change and have reverted. Our internal telemetry shows the signs of recovery and are currently monitoring the recovery status. We expect full service recovery within an hour. We will provide an update by Wednesday, 2026-04-08 16:30 PDT with current details **Customer Symptoms** Users are automatically redirected to asia-southeast.appsheet.com, which may cause "Forbidden" or 403 errors when attempting to access their apps. **Workaround** None at this time.

2. 8 апреля 2026 г. в 23:27 UTCresolved

   **Summary** AppSheet customers experienced redirection to asia-southeast.appsheet.com instead of their intended application URLs. **Description** The issue with AppSheet has been resolved for all the affected customers as of Wednesday, 2026-04-08 15:40 US/Pacific. As per the preliminary analysis, the issue was triggered by a recent change that caused the users to be erroneously redirected to the asia-southeast region. Our engineering team rolled back the change to mitigate the impact and verified the service stability. We thank you for your patience while we worked on resolving the issue. **Customer Symptoms** Users may have experienced automatic redirection to asia-southeast.appsheet.com, resulting in errors when attempting to access their apps. **Workaround** None at this time.

1. 8 апреля 2026 г. в 18:22 UTCresolved

   **Title:** Customers may experience delays in receiving and sending emails. **Description:** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 12:00 PDT with current details. **Symptoms:** Customers may experience delays in receiving and sending emails. **Workaround:** None at this time.

2. 8 апреля 2026 г. в 19:02 UTCresolved

   **Title:** Customers may experience delays in receiving and sending emails. **Description:** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 13:00 PDT with current details. **Symptoms:** Customers may experience delays in receiving and sending emails. **Workaround:** None at this time.

3. 8 апреля 2026 г. в 20:03 UTCresolved

   **Title:** Customers may experience delays in receiving and sending emails. **Description:** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 15:00 PDT with current details. **Symptoms:** Customers may experience delays in receiving and sending emails. **Workaround:** None at this time.

4. 8 апреля 2026 г. в 21:49 UTCresolved

   **Title** Customers may have experienced delays in receiving and sending emails. **Description** We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning on Wednesday, 2026-04-08 06:30 PDT. Our engineering team has applied the mitigation, and our internal monitoring indicates that delays and errors have subsided. We will continue to monitor for service stability to ensure full recovery. We will provide an update by Wednesday, 2026-04-08 16:00 PDT with current details. **Symptoms** Customers may have experienced delays in receiving and sending emails. **Workaround** None at this time.

5. 8 апреля 2026 г. в 22:54 UTCresolved

   **Title** Customers may have experienced delays in receiving and sending emails. **Description** The issue with Gmail has been resolved for all affected users as of Wednesday, 2026-04-08 14:49 PDT. Our engineering team identified a potential issue with a noisy neighbour and has successfully mitigated impact. A full root cause analysis is in progress and further details will be shared through a subsequent incident report. We thank you for your patience while we worked on resolving the issue. **Symptoms** Customers may have experienced delays in receiving and sending emails. **Workaround** None at this time.

6. 10 апреля 2026 г. в 02:32 UTCresolved

   # Preliminary Incident Report We apologize for the inconvenience this Gmail 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. A final Incident Report with preventative actions will be posted once our investigation is complete. 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. ## Date/Time of the Issue (All time US/Pacific) - Incident Start: 08 April 2026 06:30 - Incident End: 08 April 2026 14:40 - Duration: 8 hours, 10 minutes ## Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. ## Preliminary Root Cause The preliminary root cause was identified as increased connection errors to some external mail services. Google engineers have begun a full root cause analysis and will provide additional information once it is available. ## Remediation The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: **Account Suspension:** One of the domains responsible for spamming was identified, resulting in the suspension of the abusive account after review. **Traffic Blocking:** A block rule was implemented to specifically address and stop traffic originating from an abusive sending domain. Teams monitored rejection rates until they returned to normal levels, confirming that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. A comprehensive Incident Report that will be published to provide further details and outline preventative measures. ## Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

7. 17 апреля 2026 г. в 09:10 UTCresolved

   # Incident Report ## Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. ## Root Cause The root cause was identified as increased connection errors to external mail services hosted by a specific 3rd party provider. ## Remediation and Prevention The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: **External Mail Provider Reachout:** Google worked with the external mail provider to unblock connections and prevent similar issues in the future. Teams monitored rejection rates until they returned to normal levels, verifying that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. Google is committed to preventing a repeat of this issue in the future and is completing the following actions: - Deploy systems to proactively track external blocklists and alert on degradation before users are impacted. - Improve monitoring and alerting systems to proactively detect errors related to external email recipient communication. ## Detailed Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30 PDT, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

1. 21 марта 2026 г. в 03:19 UTCresolved

   **Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.

2. 21 марта 2026 г. в 03:46 UTCresolved

   **Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 23:00 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.

3. 21 марта 2026 г. в 05:33 UTCresolved

   **Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our mitigation efforts are underway and we are seeing the signs of recovery. We do not have an ETA for full mitigation. We will provide the next update by Saturday, 2026-03-21 00:30 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.

4. 21 марта 2026 г. в 07:17 UTCresolved

   **Description** The issue has been mitigated as of Friday, 2026-03-20 22:03 US/Pacific. The service issue which resulted in connection timeouts and 502 error pages, was caused by excess traffic impacting the keep.google.com. Our engineering team has implemented a mitigation and is continuing to work to ensure long-term service stability and prevent recurrence. We thank you for your patience while we worked on resolving the issue.

1. 13 марта 2026 г. в 13:58 UTCresolved

   **Description** We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. Our engineering teams are actively working to mitigate the impact. We will provide an update by Friday, 2026-03-13 08:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** A subset of customers may experience elevated error rates when accessing the impacted products in the US region. **Workaround** Impacted users may re-attempt the unsuccessful action.

2. 13 марта 2026 г. в 14:34 UTCresolved

   **Description** We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. We have confirmed that the issue affecting Google Drive is now mitigated. Users should no longer experience unavailability when accessing or interacting with Drive files. Our engineering teams continue to actively work on mitigating the remaining impacted products. We will provide an update by Friday, 2026-03-13 09:00 PDT with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** A subset of customers may experience elevated error rates when accessing the impacted products in the US region. **Workaround** Impacted users may re-attempt the unsuccessful action.

3. 13 марта 2026 г. в 14:56 UTCresolved

   **Description** The issue with Google Workspace has been resolved for all affected users as of Friday, 2026-03-13 07:30 PDT. From preliminary analysis, the incident was triggered by resource contention in the impacted location, following a recent update. This led to elevated error rates and latency for several Workspace products. Our engineering teams mitigated the impact by increasing infrastructure capacity,performing traffic restarts, and rolling back the identified change We thank you for your patience while we worked to resolve this issue. **Customer Symptoms** A subset of customers may have experienced elevated error rates when accessing the impacted products in the US region. **Workaround** NA. Issue is now mitigated

1. 23 февраля 2026 г. в 08:17 UTCresolved

   **Summary** Google Chat is experiencing Issue with creating a new conversations **Description** Our engineering team continues to investigate the issue. We will provide an update by Monday, 2026-02-23 00:45 PST with current details. We apologize to all who are affected by the disruption. **Customer Symptoms** Users may experience errors when attempting to create new conversations or spaces in Google Chat. Existing conversations remain functional. **Workaround** None at the moment

2. 23 февраля 2026 г. в 08:34 UTCresolved

   **Summary** Google Chat is experiencing issues with creating new conversations. **Description** Our engineering teams are actively working on mitigation efforts to restore the ability to create new conversations as quickly as possible. We do not have any ETA at the moment. We will provide an update by Monday, 2026-02-23 01:30 PST with current details. **Customer Symptoms** Users may experience errors when attempting to create new Direct Messages (DM) or new chat spaces in Google Chat. This issue specifically affects the creation of new conversations; however, users can continue to send and receive messages in existing conversations and spaces **Workaround** None at the moment

3. 23 февраля 2026 г. в 08:54 UTCresolved

   The issue with Google Chat has been resolved for all affected users as of Monday, 2026-02-23 00:35 PST. As per our preliminary analysis, the incident was triggered by a recent configuration update. Our engineering team performed a rollback to mitigate the impact and verified the stability. We thank you for your patience while we worked on resolving the issue.