Cronologia delle interruzioni di Google Workspace

1. 28 agosto 2026 alle ore 19:25 UTCresolved

   ♪ Sommario ♪ Gli utenti di Google Chat stanno vivendo un problema in cui ricevono le notifiche per i nuovi messaggi, ma i messaggi reali non appaiono nella loro applicazione di chat a meno che l'utente non aggiorna la loro vista. **Descrizione: Stiamo vivendo un problema intermittente con Google Chat Venerdì, 2026-08-28 10:25 PDT. Il nostro team di ingegneri ha indagato il problema e attualmente sta lavorando per mitigare il problema. Forniamo ulteriori informazioni entro venerdì, 2026-08-28 14:15 PDT con i dettagli attuali. Ci scusiamo con tutti coloro che sono colpiti dalla rottura. # I sintomi del cliente # Gli utenti stanno vivendo un problema in cui ricevono notifiche per nuovi messaggi, ma i messaggi effettivi non appaiono nella loro applicazione di chat a meno che l'utente non aggiorna la loro vista # Workaround # Gli utenti possono rinfrescarsi per vedere nuovi messaggi

2. 28 agosto 2026 alle ore 20:55 UTCresolved

   # Sommario # Gli utenti di Google Chat hanno sperimentato un problema in cui hanno ricevuto le notifiche per nuovi messaggi, ma i messaggi reali non sono riusciti a comparire nella loro applicazione di chat a meno che l'utente non abbia aggiornato la loro vista. #Descrizione # Il problema con Google Chat è stato risolto per tutti gli utenti interessati a partire da Venerdì, 2026-08-28 13:45 PDT. Dall'analisi preliminare il problema è stato innescato a causa di una recente modifica che è stata rimossa per mitigare l'impatto. Vi ringraziamo per la vostra pazienza mentre abbiamo lavorato per risolvere il problema. # I sintomi del cliente # Gli utenti stavano vivendo un problema in cui hanno ricevuto le notifiche per i nuovi messaggi, ma i messaggi effettivi non sono comparsi nella loro applicazione di chat a meno che l'utente abbia aggiornato la loro vista. # Workaround # Nessuno come il problema è risolto.

3. 4 settembre 2026 alle ore 03:43 UTCresolved

   ## Rapporto incidente # Venerdì 28 agosto 2026, tra 10:50 US/Pacific e 13:34 US/Pacific per una durata di 2 ore e 44 minuti, gli utenti di Google Chat hanno sperimentato ritardi nella ricezione di messaggi in arrivo in tempo reale all'interno di flussi di conversazione attivi attraverso applicazioni web, desktop e mobile. Mentre gli utenti hanno continuato a ricevere notifiche per nuovi messaggi, il contenuto del messaggio non ha automaticamente reso in flussi di conversazione attiva fino a quando l'utente ha aggiornato manualmente l'applicazione o inviato un messaggio di risposta. Ai nostri stimati clienti di Google Workspace, siamo profondamente dispiaciuti per l'interruzione di servizio che avete sperimentato. Stiamo facendo un'azione immediata e decisiva per affrontare il problema e rafforzare i nostri sistemi contro gli incidenti futuri. # Causa radice # L'incidente è stato innescato durante un rollout globale dello schema di database. Un cambiamento dello schema del database incompatibile ha causato le scritture del database necessarie per la consegna del messaggio per iniziare a fallire. Nello specifico, un meccanismo per la sincronizzazione degli schemi – progettato per garantire un'elevata coerenza tra lo storage primario e la consegna dei messaggi dal vivo – ha rilevato un bug raro condizione di gara. Questo ha causato i dispacciatori di messaggi di backend per tentare scrive contro uno stato schema non pronto, portando a scrivere guasti. Poiché la consegna dei messaggi dal vivo ha avuto una dipendenza attiva da queste scritture completando con successo prima di spingere gli eventi alle schermate degli utenti, il fallimento ha causato i messaggi in arrivo per sperimentare ritardi di sincronizzazione. Servizi di notifica push separati e archiviazione dei messaggi core operati in modo indipendente e non sono stati colpiti, motivo per cui gli utenti hanno ancora ricevuto avvisi per nuovi messaggi, mentre i flussi di conversazione attivi hanno sperimentato ritardi. ## Rimediazione e prevenzione Il problema è stato rilevato tramite avviso automatico di backend sui tassi di errore di invio, insieme ai rapporti dei clienti corrispondenti. Google Engineering ha avviato flussi di lavoro paralleli per ripristinare il servizio. * Alle 12:44 US/Pacific, Google Engineering ha mitigato direttamente la fonte del problema rimuovendo la dipendenza che la consegna dei messaggi dal vivo ha avuto sul database inadeguato scrivere. Questo ha permesso ai nuovi messaggi in arrivo di bypassare la scrittura fallita e riprendere immediatamente la normale consegna in tempo reale agli schermi degli utenti. * Alle 13:00 US/Pacific, Engineering ha interrotto e reindirizzato la modifica dello schema del database alla sua precedente versione stabile verificata, ripristinando la piena compatibilità del database. * Entro 13:34 US/Pacific, come i messaggi in coda sono stati elaborati, i ritardi di sincronizzazione dei messaggi in tempo reale sono tornati al 0% in tutti i domini dei clienti. Ingegneria ha verificato che la salute del servizio completo è stato ripristinato con zero perdita di messaggi. Per evitare che questo accada di nuovo, stiamo eseguendo le seguenti azioni preventive: # Rilevamento interno garantito # Rafforzare la validazione e la verifica automatizzati per coprire questo scenario di guasto specifico attraverso fasi di pre-produzione e rollout interno. Questo mira a catturare e mitigare le incompatibilità dello schema e i casi di bordo di sincronizzazione internamente prima che qualsiasi traffico del cliente possa essere influenzato in futuro. # Resilienza contro le condizioni di gara # Miglioramenti architettonici per rendere lo schema sincronizzazione e l'architettura di consegna dei messaggi resiliente alle condizioni di gara. Questo mira a garantire che lo schema di sfondo e le incongruenze di sincronizzazione di configurazione non possano interrompere la consegna dei messaggi in tempo reale. ## Descrizione dettagliata dell'impatto La finestra di impatto incidente si è verificata tra 10:50 US/Pacifico e 13:34 US/Pacifico di venerdì 28 agosto 2026\. Questo problema è stato applicato a livello globale a tutti gli ambienti di Google Chat. **Google Chat:** Traduzione: Nuovi messaggi non sono comparsi in flussi di conversazione attivi automaticamente. Gli utenti sono stati tenuti a aggiornare manualmente il loro cliente o inviare un nuovo messaggio/riagire per costringere il flusso a sincronizzare. Revisione: Le azioni di sfondo, come l'aggiornamento di badge non letti e lo spostamento di spazi attivi in cima alla casella di posta, i tassi di errore interni pesanti e sono stati significativamente ritardati per gli utenti. ***Ricerca ritardi di indicizzazione:** Nuovi messaggi inviati durante la finestra di outage bloccato nella pipeline di indicizzazione, vivendo ritardi nel diventare ricercabile. Esclusioni: # No Data Loss # A nessun punto i dati dei clienti persi o compromessi. Tutti i messaggi trasmessi durante la finestra incidente sono stati catturati in modo sicuro nella conservazione primaria e consegnati con successo ai flussi di conversazione una volta che il backlog è stato cancellato.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 19 agosto 2026 alle ore 03:57 UTCresolved

   # Sommario # Alcuni clienti possono sperimentare la lentezza durante l'utilizzo di Google Drive. #Descrizione # Stiamo vivendo un problema con Google Drive a partire da martedì, 2026-08-18 16:58 PDT. Il nostro team di ingegneri sta attualmente lavorando a una soluzione potenziale, continuando a indagare sulla causa radice completa. Forniamo un aggiornamento di martedì, 2026-08-18 22:00 PDT con i dettagli attuali. Ci scusiamo con tutti coloro che sono colpiti dalla rottura. # Simptoms # I clienti interessati possono provare lentezza durante l'utilizzo di Google Drive. # Workaround # Nessuno in questo momento.

2. 19 agosto 2026 alle ore 04:59 UTCresolved

   # Sommario # Più clienti in Australia e Nuova Zelanda possono sperimentare lentezza o errori durante l'utilizzo di Google Drive. #Descrizione # Stiamo vivendo un problema con Google Drive a partire da martedì, 2026-08-18 16:58 PDT. Il nostro team di ingegneri sta attualmente lavorando a una soluzione potenziale, continuando a indagare sulla causa radice completa. Forniamo un aggiornamento di mercoledì, 2026-08-19 00:30 PDT con i dettagli attuali. # Simptoms # I clienti interessati in Australia e Nuova Zelanda possono sperimentare lentezza o errori durante l'utilizzo di Google Drive. Alcuni clienti possono anche osservare 502 errori con Drive inaccessibile per un breve periodo. # Workaround # Nessuno in questo momento.

3. 19 agosto 2026 alle ore 06:49 UTCresolved

   # Sommario # Più clienti in Australia e Nuova Zelanda possono sperimentare lentezza o errori durante l'accesso a Google Drive. #Descrizione # Stiamo vivendo un problema con Google Drive a partire da martedì, 2026-08-18 16:58 PDT. Il nostro team di ingegneria ha identificato la causa principale del problema e sta lavorando attivamente su una strategia di mitigazione. Non esiste un ETA per una risoluzione completa. Forniamo un aggiornamento di mercoledì, 2026-08-19 01:30 PDT con i dettagli attuali. # Simptoms # I clienti interessati in Australia e Nuova Zelanda possono sperimentare lentezza o 502 errori, con alcuni utenti brevemente in grado di accedere a Drive. # Workaround # Nessuno in questo momento.

4. 19 agosto 2026 alle ore 07:59 UTCresolved

   # Sommario # Più clienti in Australia e Nuova Zelanda possono sperimentare lentezza o errori durante l'accesso a Google Drive. #Descrizione # Stiamo vivendo un problema con Google Drive a partire da martedì, 2026-08-18 16:58 PDT. Il nostro team di ingegneria ha identificato la causa principale del problema e sta lavorando attivamente su una strategia di mitigazione. Non esiste un ETA per una risoluzione completa. Forniamo un aggiornamento di mercoledì, 2026-08-19 02:00 PDT con i dettagli attuali. # Simptoms # I clienti interessati in Australia e Nuova Zelanda possono sperimentare lentezza o 502 errori, con alcuni utenti brevemente in grado di accedere a Drive. # Workaround # Nessuno in questo momento.

5. 19 agosto 2026 alle ore 08:54 UTCresolved

   # Sommario # Più clienti in Australia e Nuova Zelanda possono sperimentare lentezza o errori durante l'accesso a Google Drive. #Descrizione # Stiamo vivendo un problema con Google Drive a partire da martedì, 2026-08-18 16:58 PDT. Il nostro team di ingegneri sta lavorando attivamente su una strategia di mitigazione. Non esiste un ETA per una risoluzione completa. Forniamo un aggiornamento di mercoledì, 2026-08-19 03:00 PDT con i dettagli attuali. # Simptoms # I clienti interessati in Australia e Nuova Zelanda possono sperimentare lentezza o 502 errori, con alcuni utenti brevemente in grado di accedere a Drive. # Workaround # Nessuno in questo momento.

6. 19 agosto 2026 alle ore 09:54 UTCresolved

   # Sommario # Più clienti in Australia e Nuova Zelanda possono sperimentare lentezza o errori durante l'accesso a Google Drive. #Descrizione # Stiamo vivendo un problema con Google Drive a partire da martedì, 2026-08-18 16:58 PDT. Il nostro team di ingegneri sta lavorando attivamente su una strategia di mitigazione. Non esiste un ETA per una risoluzione completa. Forniamo un aggiornamento di mercoledì, 2026-08-19 04:30 PDT con i dettagli attuali. # Simptoms # I clienti interessati in Australia e Nuova Zelanda possono sperimentare lentezza o 502 errori, con alcuni utenti brevemente in grado di accedere a Drive. # Workaround # Nessuno in questo momento.

7. 19 agosto 2026 alle ore 11:26 UTCresolved

   # Sommario # Più clienti in Australia e Nuova Zelanda possono sperimentare lentezza o errori durante l'accesso a Google Drive. #Descrizione # Stiamo vivendo un problema con Google Drive a partire da martedì, 2026-08-18 16:58 PDT. Il nostro team di ingegneri sta lavorando attivamente su una strategia di mitigazione. Non esiste un ETA per una risoluzione completa. Forniamo un aggiornamento di mercoledì, 2026-08-19 06:00 PDT con i dettagli attuali. # Simptoms # I clienti interessati in Australia e Nuova Zelanda possono sperimentare lentezza o 502 errori, con alcuni utenti brevemente in grado di accedere a Drive. # Workaround # Nessuno in questo momento.

8. 19 agosto 2026 alle ore 13:05 UTCresolved

   # Sommario # I clienti multipli in Australia e Nuova Zelanda possono avere provato lentezza o errori durante l'accesso a Google Drive. #Descrizione # Il problema con Google Drive è stato risolto per tutti i clienti interessati a partire da mercoledì, 2026-08-19 05:40 PDT. I nostri team di ingegneria hanno determinato la lentezza è stato il risultato di un problema localizzato di capacità e routing all'interno della nostra infrastruttura regionale. Per ripristinare il servizio, abbiamo implementato una soluzione per alleviare la congestione della rete e accelerato un aggiornamento dell'infrastruttura pianificato nella regione interessata per garantire livelli di prestazioni normali. Vi ringraziamo per la vostra pazienza mentre abbiamo lavorato per risolvere il problema. # Simptoms # I clienti interessati in Australia e Nuova Zelanda possono avere avuto una lentezza o 502 errori, con alcuni utenti brevemente in grado di accedere a Drive. # Workaround # Il problema è ora mitigato

9. 20 agosto 2026 alle ore 20:00 UTCresolved

   Relazione preliminare sugli incidenti Ci scusiamo sinceramente per la disgregazione che questo incidente ha causato alla vostra attività. Sappiamo quanto fai affidamento su Google Workspace, e ci dispiace per l'impatto sulla tua produttività. Stiamo lavorando per affrontare la causa principale e impedire che questo accada in futuro. Si prega di notare che queste informazioni si basano sulle nostre migliori conoscenze al momento della pubblicazione e sono soggette a modifiche mentre la nostra indagine continua. Una relazione finale sugli incidenti con azioni preventive sarà pubblicata una volta completata la nostra indagine. Se hai avuto un impatto al di fuori di quello che è elencato di seguito, ti preghiamo di contattare Google Workspace Support utilizzando l'articolo di aiuto [**https://support.google.com/a/answer/1047213**](https://support.google.com/a/answer/1047213). ## Data/ora del problema (Tutte le volte US/Pacifico) Inizio incidente: 18 agosto 2026 16:58 Fine incidente: 19 agosto 2026 05:40 Durata: 12 ore, 42 minuti # Il 18 agosto 2026 dalle 16:58 fino al 19 agosto 2026 05:40 US/Pacific, i clienti di Drive in Australia, Filippine e Nuova Zelanda hanno sperimentato prestazioni e lentezza degradate. Durante questo periodo gli utenti hanno anche sperimentato 502 errori. Altri servizi di Google Workspace non sono stati interessati. ## Causa di radice preliminare Google utilizza un multi-tiered globale bilanciamento del carico e la rete routing architettura per servire il traffico in modo efficiente. Per garantire un uso equo e prevenire la congestione, l'allocazione della larghezza di banda è gestita attribuendo il traffico a specifici servizi a valle. Una cattiva configurazione nell'attribuzione del traffico ha causato l'uso della larghezza di banda da attribuire in modo errato al frontend network load bilanciamento tier stesso, piuttosto che al servizio Drive. La sequenza di eventi che portano all'impatto del cliente è stata la seguente: * Il traffico dal livello di bilanciamento del carico regionale è stato erroneamente attribuito all'infrastruttura di bilanciamento del carico piuttosto che al servizio Drive. * Il traffico non correlato ha causato l'utilizzo della larghezza di banda di rete attribuito all'infrastruttura di bilanciamento del carico in questa regione per superare la sua quota. * I sistemi di gestione della larghezza di banda di rete hanno applicato la limitazione a questo traffico per far rispettare le quote, causando una grave congestione della rete che interessa il traffico di Drive in questa regione. * Questa congestione ha portato ad aumentare la latenza, la lentezza e i tassi di errore per gli utenti che accedono a Drive nelle regioni colpite. ## Remediation Gli ingegneri di Google sono stati avvisati del problema tramite monitoraggio automatizzato e un afflusso di casi di assistenza clienti, con i primi team di risposta incidente impegnati da 17:21 US/Pacific il 18 agosto 2026\. Gli ingegneri inizialmente tentarono di alleviare la congestione, drenando il traffico di frontend regionale ad una posizione geografica alternativa, ma questo si rivelò inefficace e fu ritorto. Il team ha quindi mitigato il problema migrando il traffico regionale ad un'architettura di routing di rete interna aggiornata, che ha correttamente impostato l'attribuzione del traffico per Drive. Le operazioni normali sono state completamente restaurate una volta che il 100% del traffico regionale è stato migrato all'architettura di rete aggiornata. ## Descrizione dell'impatto Tra il 18 agosto 2026, alle 16:58 US/Pacific e il 19 agosto 2026, alle 05:40 US/Pacific, gli utenti di Google Drive in Australia, Filippine e Nuova Zelanda hanno sperimentato latenza grave, le prestazioni degradate e 502 errori. Durante questa finestra di circa 12 ore e 42 minuti, i clienti interessati possono aver osservato una lentezza significativa o errori durante il tentativo di accedere a Google Drive o di elencare i file tramite Editor (ad esempio [docs.google.com](http://docs.google.com)), con tempi di carico iniziali significativamente ritardati. Il problema è stato completamente mitigato a partire dal 19 agosto 2026, alle 05:40 US/Pacifico, e il servizio normale è stato ripristinato.

10. 24 agosto 2026 alle ore 16:31 UTCresolved

    # Rapporto incidente # # Martedì 18 agosto 2026 alle 16:58 US/Pacific, un incidente che interessa Google Drive si è verificato per una durata di 12 ore e 42 minuti. I clienti situati in Australia, Filippine e Nuova Zelanda hanno sperimentato gravi latenza, errori di carico sporadici e errori quando si accede a Google Drive. Ai nostri stimati clienti di Google Workspace, siamo profondamente dispiaciuti per l'interruzione di servizio che avete sperimentato. Stiamo facendo un'azione immediata e decisiva per affrontare il problema e rafforzare i nostri sistemi contro gli incidenti futuri. Altri servizi di Google Workspace non sono stati interessati. # Causa radice # Google utilizza un multi-tiered globale bilanciamento del carico e la rete routing architettura per servire il traffico in modo efficiente. Per garantire un uso equo e prevenire la congestione, l'allocazione della larghezza di banda è gestita attribuendo il traffico a specifici servizi a valle. Una cattiva configurazione nell'attribuzione del traffico ha causato l'uso della larghezza di banda da attribuire in modo errato al frontend network load bilanciamento tier stesso, piuttosto che al servizio Drive. La sequenza di eventi che portano all'impatto del cliente è stata la seguente: * Il traffico dal livello di bilanciamento del carico regionale è stato erroneamente attribuito all'infrastruttura di bilanciamento del carico piuttosto che al servizio Drive. * Il traffico non correlato ha causato l'utilizzo della larghezza di banda di rete attribuito all'infrastruttura di bilanciamento del carico in questa regione per superare la sua quota. * I sistemi di gestione della larghezza di banda di rete hanno applicato la limitazione a questo traffico per far rispettare le quote, causando una grave congestione della rete che interessa il traffico di Drive in questa regione. * Questa congestione ha portato ad aumentare la latenza, la lentezza e i tassi di errore per gli utenti che accedono a Drive nelle regioni colpite. ## Rimediazione e prevenzione Gli ingegneri di Google sono stati avvisati del problema tramite monitoraggio automatizzato e un afflusso di casi di assistenza clienti, con i team di risposta incidente iniziali impegnati da 17:21 US/Pacific il 18 agosto, 2026\. Gli ingegneri inizialmente tentarono di alleviare la congestione, drenando il traffico di frontend regionale ad una posizione geografica alternativa, ma questo si rivelò inefficace e fu ritorto. Il team ha quindi mitigato il problema migrando il traffico regionale ad un'architettura di routing di rete interna aggiornata, che ha correttamente impostato l'attribuzione del traffico per Drive. Le operazioni normali sono state completamente restaurate alle 05:40 una volta che il 100% del traffico regionale è stato migrato all'architettura di rete aggiornata. Per evitare il ripetersi di questo problema, i nostri team di ingegneri stanno intraprendendo le seguenti azioni di prevenzione strutturale: # Resilient Network Protocol Migration # Stiamo accelerando la migrazione completa di tutto il traffico di frontend regionale al protocollo di routing di rete più recente e resiliente per garantire l'attribuzione accurata della larghezza di banda in tutti gli scenari di congestione. Traduzione: Stiamo affrontando il meccanismo sottostante che ha causato la delegazione errata e analizzando casi simili in tutta la flotta per assicurarsi che non si rioccupa. ## Descrizione dettagliata dell'impatto Dal 18 agosto 2026, 16:58 al 19 agosto 2026, 05:40 US/Pacifico per una durata di 12 ore, 42 minuti, gli utenti di Google Drive in Australia, Filippine e Nuova Zelanda hanno sperimentato un grave degrado delle prestazioni, tra cui elevata latenza e errori di accesso a Drive o file di elenco tramite Editor. Il servizio è stato completamente restaurato a partire dal 19 agosto, 05:40 US/Pacifico. **Google Drive:** * Latency elevata: Gli utenti hanno sperimentato estrema lentezza quando si carica l'interfaccia di Drive o l'accesso ai file, con i tempi di recupero dei dati iniziali fortemente ritardati. * Caricamento Fallimenti e errori: Molte richieste degli utenti hanno aggiornato o restituito gli errori HTTP 502 a causa dell'aggressiva limitazione della rete che elimina le connessioni. Esclusione: * I clienti che accedono a Google Drive dall'esterno delle regioni Australia, Filippine e Nuova Zelanda non sono stati in gran parte influenzati da questo evento di limitazione localizzato. * Altre applicazioni di Google Workspace che non si basano su questo percorso di routing specifico sono rimasti stabili durante la finestra incidente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 18 agosto 2026 alle ore 19:35 UTCresolved

   ♪ Sommario ♪ Investigare i problemi di accesso con la nuova homepage di Classroom. **Descrizione: Stiamo indagando sui rapporti di accesso con la nuova homepage di Classroom a partire da giovedì 2026-08-13. Il nostro team di ingegneri sta attualmente lavorando a una soluzione potenziale, continuando a indagare sulla causa radice completa. Forniamo un aggiornamento di martedì, 2026-08-18 13:00 PDT con i dettagli attuali. Ci scusiamo con tutti coloro che sono colpiti dalla rottura. **Sintomi: Gli amministratori e alcuni insegnanti possono sperimentare errori di autorizzazione quando si accede alla nuova homepage di Classroom. # Workaround # Gli utenti dovrebbero ancora essere in grado di navigare in altre viste dal pannello sinistro dell'interfaccia.

2. 18 agosto 2026 alle ore 20:00 UTCresolved

   ♪ Sommario ♪ Mitigando i problemi di accesso con la nuova homepage di Classroom. **Descrizione: Il lavoro di mitigazione è attualmente in corso dal nostro team di ingegneria. La mitigazione è prevista per completare entro martedì 2026-08-18 14:00 PDT. Forniamo ulteriori informazioni entro martedì, 2026-08-18 14:15 PDT. **Sintomi: Gli amministratori e alcuni insegnanti possono sperimentare errori di autorizzazione quando si accede alla nuova homepage di Classroom. # Workaround # Gli utenti dovrebbero ancora essere in grado di navigare in altre viste dal pannello sinistro dell'interfaccia.

3. 18 agosto 2026 alle ore 20:27 UTCresolved

   ♪ Sommario ♪ Problemi di accesso Mitigating per Workspace Admins con homepage di Classroom. **Descrizione: La nostra ingegneria ha identificato il lavoro di causa e mitigazione è attualmente in corso. Il rollout di mitigazione dovrebbe richiedere diverse ore. Forniamo ulteriori informazioni entro mercoledì, 2026-08-19 8:00 PDT. **Sintomi: Gli amministratori dello spazio di lavoro possono sperimentare errori di autorizzazione quando si accede alla homepage di Classroom. Rimanere la funzionalità Classroom rimane inalterata. Le Classroom Mobile App e le Classroom API non sono influenzate dal problema. # Workaround # Tutte le altre pagine non sono interessate e gli amministratori possono navigare in altre pagine utilizzando il riquadro della mano sinistra sull'interfaccia. Gli amministratori dello spazio di lavoro possono ancora creare classi senza alcun problema. Gli amministratori dello spazio di lavoro possono anche visualizzare i corsi che sono in corso per https://classroom.google.com/h/tv

4. 18 agosto 2026 alle ore 23:02 UTCresolved

   # Sommario # [Mitigati] Problemi di accesso per gli amministratori dello spazio di lavoro con la homepage di Classroom. #Descrizione # Il problema con Classroom è stato risolto per tutti gli utenti interessati a partire da martedì, 2026-08-18 15:30 PDT. Dall'analisi preliminare, il problema è stato innescato a causa di un recente cambiamento che ha causato il malfunzionamento del permesso, il nostro team di Ingegneria ha implementato la correzione per mitigare l'impatto. Vi ringraziamo per la vostra pazienza mentre abbiamo lavorato per risolvere il problema. # Simptoms # Gli amministratori dello spazio di lavoro possono avere errori di autorizzazione sperimentati quando si accede alla homepage di Classroom. Rimanere funzionalità Classroom non è rimasto colpito. Le Classroom Mobile App e le Classroom API non sono state influenzate dal problema. # Workaround # Nessuno come il problema è risolto

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 30 giugno 2026 alle ore 11:56 UTCresolved

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

2. 30 giugno 2026 alle ore 12:17 UTCresolved

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

3. 30 giugno 2026 alle ore 12:28 UTCresolved

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

4. 30 giugno 2026 alle ore 13:28 UTCresolved

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

5. 30 giugno 2026 alle ore 14:06 UTCresolved

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

6. 30 giugno 2026 alle ore 14:51 UTCresolved

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

7. 30 giugno 2026 alle ore 15:48 UTCresolved

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

8. 30 giugno 2026 alle ore 16:36 UTCresolved

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

9. 30 giugno 2026 alle ore 17:53 UTCresolved

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

10. 30 giugno 2026 alle ore 19:03 UTCresolved

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

11. 1 luglio 2026 alle ore 00:44 UTCresolved

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

12. 1 luglio 2026 alle ore 04:58 UTCresolved

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

1. 22 giugno 2026 alle ore 22:28 UTCresolved

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

2. 23 giugno 2026 alle ore 00:29 UTCresolved

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

3. 23 giugno 2026 alle ore 01:08 UTCresolved

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

1. 10 giugno 2026 alle ore 12:40 UTCresolved

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

2. 10 giugno 2026 alle ore 13:21 UTCresolved

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

3. 10 giugno 2026 alle ore 15:10 UTCresolved

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

4. 10 giugno 2026 alle ore 16:24 UTCresolved

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

5. 10 giugno 2026 alle ore 18:37 UTCresolved

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

6. 10 giugno 2026 alle ore 20:19 UTCresolved

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

7. 11 giugno 2026 alle ore 01:07 UTCresolved

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

8. 12 giugno 2026 alle ore 11:14 UTCresolved

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

9. 16 giugno 2026 alle ore 17:41 UTCresolved

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

1. 31 maggio 2026 alle ore 04:59 UTCresolved

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

2. 31 maggio 2026 alle ore 05:11 UTCresolved

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

3. 2 giugno 2026 alle ore 03:50 UTCresolved

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

4. 4 giugno 2026 alle ore 20:11 UTCresolved

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

1. 21 maggio 2026 alle ore 15:37 UTCresolved

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

2. 21 maggio 2026 alle ore 16:09 UTCresolved

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

1. 20 maggio 2026 alle ore 01:07 UTCresolved

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

2. 20 maggio 2026 alle ore 03:20 UTCresolved

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

3. 20 maggio 2026 alle ore 04:38 UTCresolved

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

1. 13 maggio 2026 alle ore 17:55 UTCresolved

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

1. 16 maggio 2026 alle ore 02:05 UTCresolved

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

2. 18 maggio 2026 alle ore 21:45 UTCresolved

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

3. 19 maggio 2026 alle ore 21:55 UTCresolved

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

4. 22 maggio 2026 alle ore 00:04 UTCresolved

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

5. 22 maggio 2026 alle ore 18:57 UTCresolved

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

1. 5 maggio 2026 alle ore 23:35 UTCresolved

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

2. 6 maggio 2026 alle ore 03:22 UTCresolved

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

3. 6 maggio 2026 alle ore 19:11 UTCresolved

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

4. 7 maggio 2026 alle ore 23:52 UTCresolved

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

5. 8 maggio 2026 alle ore 01:00 UTCresolved

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

6. 8 maggio 2026 alle ore 05:16 UTCresolved

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

7. 8 maggio 2026 alle ore 07:29 UTCresolved

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

8. 8 maggio 2026 alle ore 10:23 UTCresolved

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

9. 8 maggio 2026 alle ore 15:53 UTCresolved

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

10. 8 maggio 2026 alle ore 18:58 UTCresolved

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

1. 29 aprile 2026 alle ore 19:17 UTCresolved

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

2. 29 aprile 2026 alle ore 19:53 UTCresolved

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

3. 29 aprile 2026 alle ore 20:13 UTCresolved

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

4. 29 aprile 2026 alle ore 21:07 UTCresolved

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

1. 28 aprile 2026 alle ore 15:20 UTCresolved

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

2. 28 aprile 2026 alle ore 16:00 UTCresolved

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

3. 28 aprile 2026 alle ore 16:50 UTCresolved

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

1. 10 aprile 2026 alle ore 10:07 UTCresolved

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

2. 10 aprile 2026 alle ore 10:55 UTCresolved

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

3. 10 aprile 2026 alle ore 11:27 UTCresolved

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

4. 10 aprile 2026 alle ore 15:06 UTCresolved

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

1. 8 aprile 2026 alle ore 22:22 UTCresolved

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

2. 8 aprile 2026 alle ore 23:27 UTCresolved

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

1. 8 aprile 2026 alle ore 18:22 UTCresolved

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

2. 8 aprile 2026 alle ore 19:02 UTCresolved

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

3. 8 aprile 2026 alle ore 20:03 UTCresolved

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

4. 8 aprile 2026 alle ore 21:49 UTCresolved

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

5. 8 aprile 2026 alle ore 22:54 UTCresolved

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

6. 10 aprile 2026 alle ore 02:32 UTCresolved

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

7. 17 aprile 2026 alle ore 09:10 UTCresolved

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

1. 21 marzo 2026 alle ore 03:19 UTCresolved

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

2. 21 marzo 2026 alle ore 03:46 UTCresolved

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

3. 21 marzo 2026 alle ore 05:33 UTCresolved

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

4. 21 marzo 2026 alle ore 07:17 UTCresolved

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

1. 13 marzo 2026 alle ore 13:58 UTCresolved

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

2. 13 marzo 2026 alle ore 14:34 UTCresolved

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

3. 13 marzo 2026 alle ore 14:56 UTCresolved

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

1. 23 febbraio 2026 alle ore 08:17 UTCresolved

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

2. 23 febbraio 2026 alle ore 08:34 UTCresolved

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

3. 23 febbraio 2026 alle ore 08:54 UTCresolved

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