Historial de interrupciones de Google Workspace

1. August 28, 2026 at 7:25 PM UTCresolved

   **Summary:** Los usuarios de Google Chat están experimentando un problema donde reciben notificaciones para nuevos mensajes, pero los mensajes reales no aparecen en su aplicación de chat a menos que el usuario refresque su vista. **Descripción** Estamos experimentando un problema intermitente con Google Chat Viernes, 2026-08-28 10:25 PDT. Nuestro equipo de ingeniería ha investigado el tema y actualmente está trabajando para mitigar el problema. Proporcionaremos más información para el viernes, 2026-08-28 14:15 PDT con detalles actuales. Nos disculpamos con todos los afectados por la perturbación. **Síntomas del cliente:** Los usuarios están experimentando un problema donde reciben notificaciones para nuevos mensajes, pero los mensajes reales no aparecen en su aplicación de chat a menos que el usuario refresque su vista **Trabajando:** Los usuarios pueden refrescarse para ver nuevos mensajes

2. August 28, 2026 at 8:55 PM UTCresolved

   **Summary** Los usuarios de Google Chat experimentaron un problema donde recibieron notificaciones para nuevos mensajes, pero los mensajes reales no aparecieron en su aplicación de chat a menos que el usuario refrescase su vista. **Descripción** El problema con Google Chat se ha resuelto para todos los usuarios afectados a partir del viernes, 2026-08-28 13:45 PDT. A partir del análisis preliminar, la cuestión se desencadenó debido a un cambio reciente que se hizo retroceder para mitigar el impacto. Le agradecemos su paciencia mientras trabajamos para resolver el problema. **Síntomas del cliente** Los usuarios estaban experimentando un problema en el que recibieron notificaciones para nuevos mensajes, pero los mensajes reales no aparecieron en su aplicación de chat a menos que el usuario refrescase su opinión. *Trabajando* Ninguna como la cuestión se resuelve.

3. September 4, 2026 at 3:43 AM UTCresolved

   ## Incident Report ## Summary El viernes 28 de agosto de 2026, entre 10:50 US/Pacific y 13:34 US/Pacific por una duración de 2 horas y 44 minutos, los usuarios de Google Chat experimentaron retrasos en la recepción de mensajes entrantes en tiempo real dentro de flujos de conversaciones activas a través de aplicaciones web, de escritorio y móviles. Si bien los usuarios continuaron recibiendo notificaciones para nuevos mensajes, el contenido del mensaje no se renderizó automáticamente en secuencias de conversaciones activas hasta que el usuario refrescó manualmente la aplicación o envió un mensaje de respuesta. A nuestros valiosos clientes de Google Workspace, nos sentimos profundamente por la interrupción del servicio que experimentó. Estamos tomando medidas inmediatas y decisivas para abordar la cuestión y fortalecer nuestros sistemas contra futuros incidentes. ## Root Cause El incidente fue desencadenado durante un lanzamiento global de esquemas de base de datos. Un cambio de esquema de base de datos incompatible causó que la base de datos es necesaria para que la entrega de mensajes comience a fallar. Específicamente, un mecanismo de sincronización de esquemas — diseñado para asegurar una alta consistencia entre el almacenamiento primario y la entrega de mensajes en vivo— cuenta con un error de condición de raza rara. Esto causó que los despachadores del mensaje de backend intentaran escribir contra un estado de esquema no leído, lo que llevó a escribir fallas. Debido a que la entrega de mensajes en vivo tenía una dependencia activa de estos escritos completando con éxito antes de empujar los eventos a las pantallas de usuario, el fracaso causó que los mensajes entrantes experimentaran retrasos de sincronización. Los servicios separados de notificación de empuje y almacenamiento de mensajes básicos funcionaron independientemente y no fueron afectados, por lo que los usuarios todavía recibieron alertas de nuevos mensajes mientras que los flujos de conversaciones activos experimentaron retrasos. ## Remediation and Prevention El problema se detectó mediante alerta automática de backend sobre las tasas de error de envío, junto con los informes correspondientes de los clientes. Google Engineering inició flujos de trabajo paralelos para restaurar el servicio. * A las 12:44 EE.UU./Pacífico, Google Engineering mitigó directamente la fuente de la cuestión eliminando la dependencia que la entrega de mensajes en vivo tenía en la escritura de la base de datos. Esto permitió que nuevos mensajes entrantes pasaran por alto la escritura fallida y reanudar inmediatamente la entrega normal en tiempo real a las pantallas de usuario. * A las 13:00 EE.UU./Pacífico, Engineering detuvo y revertió el cambio de esquema de bases de datos a su versión estable verificada anterior, restaurando la compatibilidad completa de la base de datos. * Para 13:34 EE.UU./Pacífico, ya que los mensajes solicitados fueron procesados, los retrasos de sincronización de mensajes en tiempo real regresaron al 0% en todos los dominios del cliente. Ingeniería verificó que la salud del servicio completo fue restaurada con cero pérdida de mensajes. Para evitar que esto suceda de nuevo, estamos ejecutando las siguientes acciones preventivas: * **Detección interna ardiente:** Fortalecer la validación y verificación automatizadas para cubrir este escenario específico de fallos en las etapas previas a la producción y la implantación interna. Este objetivo es capturar y mitigar incompatibilidades de esquema y casos de sincronización internamente antes de que cualquier tráfico de clientes pueda ser impactado en el futuro. * **Resilience Against Race Conditions:** Implementar mejoras arquitectónicas para hacer la sincronización de esquemas y la arquitectura de entrega de mensajes resiliente a las condiciones de carrera. Este objetivo es asegurar que el esquema de fondo y las inconsistencias de sincronización de config no puedan interrumpir la entrega de mensajes en tiempo real. ## Descripción detallada del impacto La ventana de impacto ocurrió entre 10:50 US/Pacific y 13:34 US/Pacific el viernes, 28 de agosto de 2026\. Este tema se aplica globalmente a todos los entornos de Google Chat. #Google Chat: # * **Delayed message rendering:** Nuevos mensajes no aparecieron en flujos de conversación activos automáticamente. Se pidió a los usuarios que actualizaran manualmente a su cliente o enviaran un nuevo mensaje/reacto para obligar al flujo a sincronizarse. * **Stalled read states and inbox sorting:** Las acciones de fondo, como actualizar insignias no leídos y mover espacios activos a la parte superior de la bandeja de entrada, experimentaron fuertes tasas de error interno y se retrasaron significativamente para los usuarios. * **Retrasos de indexación de búsqueda:** Nuevos mensajes enviados durante la ventana de salida estancados en la tubería de indexación, experimentando retrasos en la búsqueda. **Exclusiones de humo:** * **Sin pérdida de datos:** En ningún momento se perdieron o comprometieron los datos del cliente. Todos los mensajes transmitidos durante la ventana del incidente fueron capturados de forma segura en el almacenamiento primario y entregados con éxito a las secuencias de conversaciones una vez que el atraso se despejó.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 19, 2026 at 3:57 AM UTCresolved

   **Summary** Algunos clientes pueden experimentar lentitud mientras usan Google Drive. **Descripción** Estamos experimentando un problema con Google Drive a partir del martes, 2026-08-18 16:58 PDT. Nuestro equipo de ingeniería está trabajando actualmente en una solución potencial mientras continúa investigando la causa raíz completa. Ofrecemos una actualización para el martes, 2026-08-18 22:00 PDT con los detalles actuales. Nos disculpamos con todos los afectados por la perturbación. *Síntomas* Los clientes afectados pueden experimentar lentitud mientras usan Google Drive. *Trabajando* Nada en este momento.

2. August 19, 2026 at 4:59 AM UTCresolved

   **Summary** Múltiples clientes en Australia y Nueva Zelanda pueden experimentar lentitud o errores al usar Google Drive. **Descripción** Estamos experimentando un problema con Google Drive a partir del martes, 2026-08-18 16:58 PDT. Nuestro equipo de ingeniería está trabajando actualmente en una solución potencial mientras continúa investigando la causa raíz completa. Ofrecemos una actualización para el miércoles, 2026-08-19 00:30 PDT con los detalles actuales. *Síntomas* Los clientes afectados en Australia y Nueva Zelanda pueden experimentar lentitud o errores al usar Google Drive. Algunos clientes también pueden observar errores 502 con Drive inaccesible durante un breve período. *Trabajando* Nada en este momento.

3. August 19, 2026 at 6:49 AM UTCresolved

   **Summary** Múltiples clientes en Australia y Nueva Zelanda pueden experimentar lentitud o errores al acceder a Google Drive. **Descripción** Estamos experimentando un problema con Google Drive a partir del martes, 2026-08-18 16:58 PDT. Nuestro equipo de ingeniería ha identificado la causa raíz de la cuestión y está trabajando activamente en una estrategia de mitigación. No hay ETA para la resolución completa. Ofrecemos una actualización para el miércoles, 2026-08-19 01:30 PDT con los detalles actuales. *Síntomas* Los clientes afectados en Australia y Nueva Zelanda pueden experimentar lentitud o errores de 502, con algunos usuarios brevemente incapaz de acceder a Drive. *Trabajando* Nada en este momento.

4. August 19, 2026 at 7:59 AM UTCresolved

   **Summary** Múltiples clientes en Australia y Nueva Zelanda pueden experimentar lentitud o errores al acceder a Google Drive. **Descripción** Estamos experimentando un problema con Google Drive a partir del martes, 2026-08-18 16:58 PDT. Nuestro equipo de ingeniería ha identificado la causa raíz de la cuestión y está trabajando activamente en una estrategia de mitigación. No hay ETA para la resolución completa. Ofrecemos una actualización para el miércoles, 2026-08-19 02:00 PDT con los detalles actuales. *Síntomas* Los clientes afectados en Australia y Nueva Zelanda pueden experimentar lentitud o errores de 502, con algunos usuarios brevemente incapaz de acceder a Drive. *Trabajando* Nada en este momento.

5. August 19, 2026 at 8:54 AM UTCresolved

   **Summary** Múltiples clientes en Australia y Nueva Zelanda pueden experimentar lentitud o errores al acceder a Google Drive. **Descripción** Estamos experimentando un problema con Google Drive a partir del martes, 2026-08-18 16:58 PDT. Nuestro equipo de ingeniería está trabajando activamente en una estrategia de mitigación. No hay ETA para la resolución completa. Ofrecemos una actualización para el miércoles, 2026-08-19 03:00 PDT con los detalles actuales. *Síntomas* Los clientes afectados en Australia y Nueva Zelanda pueden experimentar lentitud o errores de 502, con algunos usuarios brevemente incapaz de acceder a Drive. *Trabajando* Nada en este momento.

6. August 19, 2026 at 9:54 AM UTCresolved

   **Summary** Múltiples clientes en Australia y Nueva Zelanda pueden experimentar lentitud o errores al acceder a Google Drive. **Descripción** Estamos experimentando un problema con Google Drive a partir del martes, 2026-08-18 16:58 PDT. Nuestro equipo de ingeniería está trabajando activamente en una estrategia de mitigación. No hay ETA para la resolución completa. Proporcionaremos una actualización para el miércoles, 2026-08-19 04:30 PDT con los detalles actuales. *Síntomas* Los clientes afectados en Australia y Nueva Zelanda pueden experimentar lentitud o errores de 502, con algunos usuarios brevemente incapaz de acceder a Drive. *Trabajando* Nada en este momento.

7. August 19, 2026 at 11:26 AM UTCresolved

   **Summary** Múltiples clientes en Australia y Nueva Zelanda pueden experimentar lentitud o errores al acceder a Google Drive. **Descripción** Estamos experimentando un problema con Google Drive a partir del martes, 2026-08-18 16:58 PDT. Nuestro equipo de ingeniería está trabajando activamente en una estrategia de mitigación. No hay ETA para la resolución completa. Ofrecemos una actualización para el miércoles, 2026-08-19 06:00 PDT con los detalles actuales. *Síntomas* Los clientes afectados en Australia y Nueva Zelanda pueden experimentar lentitud o errores de 502, con algunos usuarios brevemente incapaz de acceder a Drive. *Trabajando* Nada en este momento.

8. August 19, 2026 at 1:05 PM UTCresolved

   **Summary** Múltiples clientes en Australia y Nueva Zelanda pueden haber experimentado lentitud o errores al acceder a Google Drive. **Descripción** El problema con Google Drive se ha resuelto para todos los clientes afectados a partir del miércoles, 2026-08-19 05:40 PDT. Nuestros equipos de ingeniería determinaron la lentitud fue el resultado de una cuestión de capacidad localizada y de enrutamiento dentro de nuestra infraestructura regional. Para restaurar el servicio, implementamos una solución para aliviar la congestión de la red y aceleró una actualización de infraestructura prevista en la región afectada para asegurar niveles normales de rendimiento. Le agradecemos su paciencia mientras trabajamos para resolver el problema. *Síntomas* Los clientes afectados en Australia y Nueva Zelanda pueden haber experimentado retrasos o errores de 502, con algunos usuarios brevemente incapaz de acceder a Drive. *Trabajando* La cuestión se ha mitigado ahora

9. August 20, 2026 at 8:00 PM UTCresolved

   Informe preliminar sobre incidentes Sinceramente nos disculpamos por la interrupción de este incidente causado a su negocio. Sabemos cuánto confías en Google Workspace, y lamentamos el impacto en tu productividad. Estamos trabajando para abordar la causa raíz y evitar que esto ocurra en el futuro. Tenga en cuenta que esta información se basa en nuestro mejor conocimiento en el momento de la publicación y está sujeta a cambios a medida que continúa nuestra investigación. Un informe final de incidentes con acciones preventivas será publicado una vez que nuestra investigación esté completa. Si ha tenido efectos fuera de lo que se enumera a continuación, sírvase comunicarse con Google Workspace Support utilizando el artículo de ayuda [**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: 18 August 2026 16:58 Incident End: 19 August 2026 05:40 Duración: 12 horas, 42 minutos ## Summary El 18 de agosto de 2026 de 16:58 a 19 de agosto de 2026 05:40 US/Pacific, Los clientes de Drive en Australia, Filipinas y Nueva Zelanda experimentaron un rendimiento y una lentitud degradados. Durante este período los usuarios también experimentaron 502 errores. Otros servicios de Google Workspace no se vieron afectados. ## Preliminary Root Cause Google utiliza una arquitectura de equilibrio de carga global multi-tierra y enrutamiento de red para servir el tráfico eficientemente. Para asegurar un uso justo y prevenir la congestión, la asignación de ancho de banda se gestiona atribuyendo tráfico a servicios específicos de aguas abajo. Una malconfiguración en la atribución del tráfico hizo que el uso del ancho de banda fuera atribuido incorrectamente a la red de frontend equilibrando el tier mismo, en lugar del servicio Drive. La secuencia de eventos que llevaron al impacto del cliente fue la siguiente: * El tráfico del nivel de equilibrio de carga regional se atribuyó incorrectamente a la infraestructura de equilibrio de carga en lugar del servicio Drive. * El tráfico no relacionado causó el uso de ancho de red atribuido a la infraestructura de equilibrio de carga en esta región para superar su cuota. * Sistemas de gestión del ancho de banda de red aplicaron oscilación a este tráfico para hacer cumplir cuotas, causando congestión de red severa que afecta el tráfico de Drive en esta región. * Esta congestión dio lugar a un aumento de latencia, la lentitud y las tasas de error para los usuarios que acceden a Drive en las regiones afectadas. ## Remediation Los ingenieros de Google fueron alertados a la cuestión mediante monitoreo automatizado y una afluencia de casos de atención al cliente, con equipos de respuesta de incidentes iniciales comprometidos por 17:21 US/Pacific el 18 de agosto de 2026\. Inicialmente los ingenieros intentaron aliviar la congestión drenando el tráfico de frontend regional a una ubicación geográfica alternativa, pero esto resultó ineficaz y fue revertido. El equipo entonces mitigó la cuestión migrando el tráfico regional a una arquitectura de enrutamiento de red interna actualizada, que correctamente estableció la atribución de tráfico para Drive. Las operaciones normales fueron totalmente restauradas una vez que el 100% del tráfico regional fue migrado a la arquitectura de red actualizada. ## Descripción del impacto Entre el 18 de agosto de 2026, a las 16:58 EE.UU./Pacífico y el 19 de agosto de 2026, a las 05:40 US/Pacífico, los usuarios de Google Drive en Australia, Filipinas y Nueva Zelanda experimentaron latencia severa, el rendimiento degradado y 502 errores. Durante esta ventana de aproximadamente 12 horas y 42 minutos, los clientes afectados pueden haber observado una lentitud o errores significativos cuando intentan acceder a Google Drive o enumerar archivos a través de Editores (por ejemplo [docs.google.com](http://docs.google.com)), con tiempos iniciales de carga significativamente retrasados. El tema se mitigó totalmente a partir del 19 de agosto de 2026, a las 05:40 US/Pacific, y se ha restaurado el servicio normal.

10. August 24, 2026 at 4:31 PM UTCresolved

    # Incident Report ## Summary El martes 18 de agosto de 2026 a las 16:58 US/Pacific, un incidente que afectó a Google Drive ocurrió durante 12 horas y 42 minutos. Los clientes ubicados en Australia, Filipinas y Nueva Zelanda experimentaron graves retrasos, fallas de carga esporádicas y errores al acceder a Google Drive. A nuestros valiosos clientes de Google Workspace, nos sentimos profundamente por la interrupción del servicio que experimentó. Estamos tomando medidas inmediatas y decisivas para abordar la cuestión y fortalecer nuestros sistemas contra futuros incidentes. Otros servicios de Google Workspace no se vieron afectados. ## Root Cause Google utiliza una arquitectura de equilibrio de carga global multi-tierra y enrutamiento de red para servir el tráfico eficientemente. Para asegurar un uso justo y prevenir la congestión, la asignación de ancho de banda se gestiona atribuyendo tráfico a servicios específicos de aguas abajo. Una malconfiguración en la atribución del tráfico hizo que el uso del ancho de banda fuera atribuido incorrectamente a la red de frontend equilibrando el tier mismo, en lugar del servicio Drive. La secuencia de eventos que llevaron al impacto del cliente fue la siguiente: * El tráfico del nivel de equilibrio de carga regional se atribuyó incorrectamente a la infraestructura de equilibrio de carga en lugar del servicio Drive. * El tráfico no relacionado causó el uso de ancho de red atribuido a la infraestructura de equilibrio de carga en esta región para superar su cuota. * Sistemas de gestión del ancho de banda de red aplicaron oscilación a este tráfico para hacer cumplir cuotas, causando congestión de red severa que afecta el tráfico de Drive en esta región. * Esta congestión dio lugar a un aumento de latencia, la lentitud y las tasas de error para los usuarios que acceden a Drive en las regiones afectadas. ## Remediation and Prevention Los ingenieros de Google fueron alertados a la cuestión mediante monitoreo automatizado y una afluencia de casos de atención al cliente, con equipos de respuesta de incidentes iniciales comprometidos por 17:21 US/Pacific el 18 de agosto, 2026\. Inicialmente los ingenieros intentaron aliviar la congestión drenando el tráfico de frontend regional a una ubicación geográfica alternativa, pero esto resultó ineficaz y fue revertido. El equipo entonces mitigó la cuestión migrando el tráfico regional a una arquitectura de enrutamiento de red interna actualizada, que correctamente estableció la atribución de tráfico para Drive. Las operaciones normales fueron totalmente restauradas a las 05:40 una vez que el 100% del tráfico regional fue migrado a la arquitectura de red actualizada. Para evitar la repetición de esta cuestión, nuestros equipos de ingeniería están llevando a cabo las siguientes acciones preventivas estructurales: * **Migración del Protocolo de Red resistente:** Estamos acelerando la migración completa de todo el tráfico de frontend regional al protocolo de enrutamiento de red más nuevo y resistente para asegurar la atribución precisa del ancho de banda bajo todos los escenarios de congestión. * **Delegation Root Cause Remediation:** Estamos abordando el mecanismo subyacente que causó la delegación incorrecta y analizando casos similares en toda la flota para asegurar que no vuelva a ocurrir. ## Descripción detallada del impacto Del 18 de agosto de 2026, 16:58 al 19 de agosto de 2026, 05:40 US/Pacific durante 12 horas, 42 minutos, los usuarios de Google Drive en Australia, Filipinas y Nueva Zelanda experimentaron una grave degradación del rendimiento, incluyendo alta latencia y errores accediendo a archivos Drive o listados a través de Editores. El servicio fue totalmente restaurado al 19 de agosto, 05:40 US/Pacific. *Google Drive* * Elevated Latency: Los usuarios experimentaron extrema lentitud al cargar la interfaz Drive o acceder a los archivos, con tiempos iniciales de recuperación de datos muy retrasados. * Carga de fallos y errores: Muchos usuarios solicitan errores de HTTP 502 ocasionados o devueltos debido a la red agresiva que prospera bajando las conexiones. *Exclusión de la piel* * Los clientes que accedieron a Google Drive desde fuera de las regiones de Australia, Filipinas y Nueva Zelanda no se vieron afectados en gran medida por este evento de trineo localizado. * Otras aplicaciones de Google Workspace que no dependían de esta ruta de enrutamiento específica permanecieron estables durante la ventana del incidente.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 18, 2026 at 7:35 PM UTCresolved

   **Summary:** Investigando problemas de acceso con la nueva página web de Classroom. **Descripción** Estamos investigando informes de problemas de acceso con la nueva página web de Classroom a partir del jueves, 2026-08-13. Nuestro equipo de ingeniería está trabajando actualmente en una solución potencial mientras continúa investigando la causa raíz completa. Ofrecemos una actualización para el martes, 2026-08-18 13:00 PDT con los detalles actuales. Nos disculpamos con todos los afectados por la perturbación. *Síntomas* Los administradores y algunos profesores pueden experimentar errores de permiso al acceder a la nueva página web de Classroom. **Trabajando:** Los usuarios todavía deben poder navegar a otras vistas desde el panel izquierdo de la interfaz.

2. August 18, 2026 at 8:00 PM UTCresolved

   **Summary:** Mitigando problemas de acceso con la nueva página web de Classroom. **Descripción** Mitigation work is currently underway by our engineering team. Se espera que la mitigación termine el martes 2026-08-18 14:00 PDT. Proporcionaremos más información para el martes, 2026-08-18 14:15 PDT. *Síntomas* Los administradores y algunos profesores pueden experimentar errores de permiso al acceder a la nueva página web de Classroom. **Trabajando:** Los usuarios todavía deben poder navegar a otras vistas desde el panel izquierdo de la interfaz.

3. August 18, 2026 at 8:27 PM UTCresolved

   **Summary:** Mitigating access issues for Workspace Admins with Classroom’s web homepage. **Descripción** Nuestra ingeniería ha identificado la causa y el trabajo de mitigación está en marcha. Se espera que el despliegue de mitigación dure varias horas. Proporcionaremos más información para el miércoles, 2026-08-19 8:00 PDT. *Síntomas* Workspace Admins puede experimentar errores de permiso al acceder a la página web de Classroom. La funcionalidad restante de aulas sigue sin afectar. La aplicación móvil de aulas y la API de aulas no son afectados por el problema. **Trabajando:** Todas las otras páginas no son afectadas y los administradores pueden navegar a otras páginas utilizando el panel izquierdo de la mano en la interfaz. Los administradores del espacio de trabajo todavía pueden crear clases sin ningún problema. Workspace Admins también puede ver los cursos en los que están yendo a https://classroom.google.com/h/tv

4. August 18, 2026 at 11:02 PM UTCresolved

   **Summary** [Mitigated] Problemas de acceso para el Workspace Admins con la página web de Classroom. **Descripción** El tema con Classroom se ha resuelto para todos los usuarios afectados el martes, 2026-08-18 15:30 PDT. Desde el análisis preliminar, la cuestión se inició debido a un cambio reciente que causó el desajuste de permiso, nuestro equipo de Ingeniería ha lanzado la solución para mitigar el impacto. Le agradecemos su paciencia mientras trabajamos para resolver el problema. *Síntomas* Workspace Admins puede haber experimentado errores de permiso al acceder a la página web de Classroom. La funcionalidad restante de la sala de clases no se vio afectada. La aplicación móvil de aula y la API de aula no se vieron afectados por el problema. *Trabajando* Ninguna como la cuestión se resuelve

Traducido automáticamente desde la actualización oficial del incidente.

1. June 30, 2026 at 11:56 AM 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. June 30, 2026 at 12:17 PM 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. June 30, 2026 at 12:28 PM 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. June 30, 2026 at 1:28 PM 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. June 30, 2026 at 2:06 PM 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. June 30, 2026 at 2:51 PM 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. June 30, 2026 at 3:48 PM 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. June 30, 2026 at 4:36 PM 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. June 30, 2026 at 5:53 PM 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. June 30, 2026 at 7:03 PM 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. July 1, 2026 at 12:44 AM 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. July 1, 2026 at 4:58 AM 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. June 22, 2026 at 10:28 PM 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. June 23, 2026 at 12:29 AM 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. June 23, 2026 at 1:08 AM 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. June 10, 2026 at 12:40 PM 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. June 10, 2026 at 1:21 PM 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. June 10, 2026 at 3:10 PM 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. June 10, 2026 at 4:24 PM 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. June 10, 2026 at 6:37 PM 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. June 10, 2026 at 8:19 PM 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. June 11, 2026 at 1:07 AM 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. June 12, 2026 at 11:14 AM 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. June 16, 2026 at 5:41 PM 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. May 31, 2026 at 4:59 AM 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. May 31, 2026 at 5:11 AM 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. June 2, 2026 at 3:50 AM 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. June 4, 2026 at 8:11 PM 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. May 21, 2026 at 3:37 PM 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. May 21, 2026 at 4:09 PM 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. May 20, 2026 at 1:07 AM 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. May 20, 2026 at 3:20 AM 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. May 20, 2026 at 4:38 AM 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. May 13, 2026 at 5:55 PM 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. May 16, 2026 at 2:05 AM 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. May 18, 2026 at 9:45 PM 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. May 19, 2026 at 9:55 PM 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. May 22, 2026 at 12:04 AM 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. May 22, 2026 at 6:57 PM 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. May 5, 2026 at 11:35 PM 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. May 6, 2026 at 3:22 AM 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. May 6, 2026 at 7:11 PM 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. May 7, 2026 at 11:52 PM 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. May 8, 2026 at 1:00 AM 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. May 8, 2026 at 5:16 AM 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. May 8, 2026 at 7:29 AM 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. May 8, 2026 at 10:23 AM 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. May 8, 2026 at 3:53 PM 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. May 8, 2026 at 6:58 PM 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. April 29, 2026 at 7:17 PM 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. April 29, 2026 at 7:53 PM 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. April 29, 2026 at 8:13 PM 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. April 29, 2026 at 9:07 PM 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. April 28, 2026 at 3:20 PM 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. April 28, 2026 at 4:00 PM 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. April 28, 2026 at 4:50 PM 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. April 10, 2026 at 10:07 AM 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. April 10, 2026 at 10:55 AM 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. April 10, 2026 at 11:27 AM 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. April 10, 2026 at 3:06 PM 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. April 8, 2026 at 10:22 PM 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. April 8, 2026 at 11:27 PM 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. April 8, 2026 at 6:22 PM 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. April 8, 2026 at 7:02 PM 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. April 8, 2026 at 8:03 PM 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. April 8, 2026 at 9:49 PM 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. April 8, 2026 at 10:54 PM 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. April 10, 2026 at 2:32 AM 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. April 17, 2026 at 9:10 AM 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. March 21, 2026 at 3:19 AM 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. March 21, 2026 at 3:46 AM 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. March 21, 2026 at 5:33 AM 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. March 21, 2026 at 7:17 AM 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. March 13, 2026 at 1:58 PM 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. March 13, 2026 at 2:34 PM 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. March 13, 2026 at 2:56 PM 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. February 23, 2026 at 8:17 AM 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. February 23, 2026 at 8:34 AM 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. February 23, 2026 at 8:54 AM 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.