Google Workspace driftsforstyrrelser

1. 28. august 2026 kl. 19.25 UTCresolved

   * * Oversigt: * * Google Chat-brugere oplever et problem, hvor de modtager meddelelser om nye meddelelser, men de faktiske meddelelser ikke vises i deres chat-program, medmindre brugeren genopfrisker deres visning. * * Beskrivelse: * * Vi oplever et intermitterende problem med Google Chat fredag, 2026-08- 28 10: 25 PDT. Vores ingeniørhold har undersøgt sagen og arbejder i øjeblikket på at mildne problemet. Vi vil give mere information på fredag, 2026-08- 28 14: 15 PDT med aktuelle oplysninger. Vi undskylder over for alle, der er berørt af afbrydelsen. * * Kundesymptomer: * * Brugere oplever et problem, hvor de modtager meddelelser om nye meddelelser, men de faktiske meddelelser ikke vises i deres chat-program, medmindre brugeren genopfrisker deres visning * * Arbejde omkring: * * Brugere kan opdatere for at se nye beskeder

2. 28. august 2026 kl. 20.55 UTCresolved

   * * Oversigt * * Google Chat-brugere oplevede et problem, hvor de modtog meddelelser om nye meddelelser, men de faktiske meddelelser kunne ikke vises i deres chat-program, medmindre brugeren genopfrisket deres visning. * * Beskrivelse * * Problemet med Google Chat er blevet løst for alle berørte brugere som fredag, 2026-08- 28 13: 45 PDT. Fra indledende analyse blev problemet udløst på grund af en nylig ændring, som blev rullet tilbage for at afbøde virkningen. Vi takker Dem for Deres tålmodighed, mens vi arbejdede på at løse problemet. * * Kundesymptomer * * Brugerne oplevede et problem, hvor de modtog meddelelser om nye meddelelser, men de faktiske meddelelser ikke kunne vises i deres chat ansøgning, medmindre brugeren genopfrisket deres visning. * * Arbejde omkring * * Ingen som problemet er løst.

3. 4. september 2026 kl. 03.43 UTCresolved

   # # Incident Report # # Summary Fredag den 28. august 2026, mellem 10: 50 US / Pacific og 13: 34 US / Pacific i en varighed af 2 timer og 44 minutter, Google Chat brugere oplevede forsinkelser i at modtage real- time indgående meddelelser inden for aktiv samtale strømme på tværs af web, desktop, og mobile applikationer. Mens brugerne fortsatte med at modtage meddelelser om nye meddelelser, meddelelsen indhold ikke automatisk gengive i aktive samtale strømme, indtil brugeren manuelt genopfrisket programmet eller sendt en svarmeddelelse. Til vores værdsatte Google Workspace-kunder, er vi dybt kede af den service afbrydelse, du oplevede. Vi træffer omgående og beslutsomme foranstaltninger for at løse problemet og styrke vores systemer mod fremtidige hændelser. # Root Cause Hændelsen blev udløst under en global database skema udrulning. En inkompatibel database skema ændring forårsaget database skriver kræves for meddelelse levering til at begynde at svigte. Specifikt, en mekanisme for schema synkronisering - designet til at sikre høj overensstemmelse mellem primær opbevaring og live message levering - stødte på en sjælden race tilstand fejl. Dette forårsagede backend besked afsendere til at forsøge skriver mod en uklar skema stat, der fører til at skrive fejl. Fordi live message levering havde en aktiv afhængighed af disse skriver udfylde succes, før du skubber begivenheder til brugerskærme, fiasko forårsaget indgående meddelelser til at opleve synkronisering forsinkelser. Separat push notification services og core message storage fungerede uafhængigt og var upåvirket, hvilket er grunden til, at brugerne stadig modtog advarsler for nye meddelelser, mens aktive samtale strømme oplevede forsinkelser. # Rengøring og forebyggelse Problemet blev opdaget ved automatiseret backend advarsel på afsendelse fejlrater, sammen med tilsvarende kunderapporter. Google Engineering startede parallelle arbejdsstrømme for at genoprette tjenesten. * På 12: 44 US / Pacific, Google Engineering direkte afbødet kilden til problemet ved at fjerne den afhængighed, live message levering havde på den svigtende database skrive. Dette gjorde det muligt for nye indkommende meddelelser at omgå den mislykkede skrive og straks genoptage normal real- time levering til brugerskærme. * Ved 13: 00 US / Pacific, Engineering stoppet og vendt databasen skema ændring til sin tidligere verificerede stabile version, genoprette fuld database kompatibilitet. * Ved 13: 34 US / Pacific, som i kø meddelelser blev behandlet, real-time besked synkronisering forsinkelser returneres til 0% på tværs af alle kundedomæner. Engineering bekræftet, at fuld service sundhed blev genoprettet med nul meddelelse tab. For at forhindre dette i at ske igen, vi udfører følgende forebyggende handlinger: * * * Hårdere intern detektion: * * Styrke automatiseret validering og verifikation til at dække dette specifikke fejlscenarie på tværs af præ-produktion og interne udrulningsfaser. Dette har til formål at fange og afbøde schema uforeneligheder og synkronisering kant sager internt, før nogen kundetrafik kan blive påvirket i fremtiden. * * * Resistens over for raceforhold: * * Implementere arkitektoniske forbedringer for at gøre skema synkronisering og meddelelse levering arkitektur modstandsdygtig over for race betingelser. Dette har til formål at sikre, at baggrund skema og config synkronisering uoverensstemmelser ikke kan forstyrre real- time meddelelse levering. # Detaljeret beskrivelse af virkning Hændelsen indslag vindue opstod mellem 10: 50 US / Pacific og 13: 34 US / Pacific på fredag, 28 August 2026\. Dette spørgsmål gjaldt globalt for alle Google Chat-miljøer. * * Google Chat: * * * * * Forsinket meddelelse rendering: * * Nye meddelelser vises ikke i aktive samtale strømme automatisk. Brugerne var forpligtet til manuelt at opdatere deres klient eller sende en ny besked / reagere for at tvinge strømmen til at synkronisere. * * * Standset læse tilstande og indbakke sortering: * * Baggrundshandlinger, såsom opdatering af ulæste badges og flytte aktive rum til toppen af indbakken, oplevede store interne fejlrater og blev betydeligt forsinket for brugerne. * * * Søgning indeksering forsinkelser: * * Nye meddelelser sendt under udbrudsvinduet fastlåst i indeksering rørledningen, oplever forsinkelser i at blive søgbar. * * Anvendelsesområde Eksklusioner: * * * * * Ingen tab af data: * * På intet tidspunkt var kundedata tabt eller kompromitteret. Alle meddelelser, der blev sendt under hændelsesvinduet, blev sikkert fanget i primær lagring og leveret til samtalestrømme, når backlog ryddet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. august 2026 kl. 03.57 UTCresolved

   * * Oversigt * * Nogle kunder kan opleve langsommelighed, når de bruger Google Drive. * * Beskrivelse * * Vi oplever et problem med Google Drive begynder tirsdag, 2026-08- 18 16: 58 PDT. Vores ingeniørhold arbejder i øjeblikket på en potentiel rettelse, mens vi fortsætter med at undersøge den fulde rod årsag. Vi vil levere en opdatering inden tirsdag, 2026-08- 18 22: 00 PDT med aktuelle oplysninger. Vi undskylder over for alle, der er berørt af afbrydelsen. * * symptomer * * Berørte kunder kan opleve langsommelighed, når de bruger Google Drive. * * Arbejde omkring * * Ingen på nuværende tidspunkt.

2. 19. august 2026 kl. 04.59 UTCresolved

   * * Oversigt * * Flere kunder i Australien og New Zealand kan opleve langsommelighed eller fejl, mens du bruger Google Drive. * * Beskrivelse * * Vi oplever et problem med Google Drive begynder tirsdag, 2026-08- 18 16: 58 PDT. Vores ingeniørhold arbejder i øjeblikket på en potentiel rettelse, mens vi fortsætter med at undersøge den fulde rod årsag. Vi vil levere en opdatering inden onsdag, 2026-08- 19 00: 30 PDT med aktuelle oplysninger. * * symptomer * * Berørte kunder i Australien og New Zealand kan opleve langsommelighed eller fejl, mens du bruger Google Drive. Nogle kunder kan også observere 502 fejl med Drev utilgængelige for en kort periode. * * Arbejde omkring * * Ingen på nuværende tidspunkt.

3. 19. august 2026 kl. 06.49 UTCresolved

   * * Oversigt * * Flere kunder i Australien og New Zealand kan opleve langsommelighed eller fejl, mens adgang til Google Drive. * * Beskrivelse * * Vi oplever et problem med Google Drive begynder tirsdag, 2026-08- 18 16: 58 PDT. Vores ingeniørhold har identificeret årsagen til problemet og arbejder aktivt på en afbødningsstrategi. Der er ingen ETA for fuld løsning. Vi vil levere en opdatering inden onsdag, 2026-08- 19 01: 30 PDT med aktuelle oplysninger. * * symptomer * * Berørte kunder i Australien og New Zealand kan opleve langsommelighed eller 502 fejl, med nogle brugere kort ude af stand til at få adgang til Drive. * * Arbejde omkring * * Ingen på nuværende tidspunkt.

4. 19. august 2026 kl. 07.59 UTCresolved

   * * Oversigt * * Flere kunder i Australien og New Zealand kan opleve langsommelighed eller fejl, mens adgang til Google Drive. * * Beskrivelse * * Vi oplever et problem med Google Drive begynder tirsdag, 2026-08- 18 16: 58 PDT. Vores ingeniørhold har identificeret årsagen til problemet og arbejder aktivt på en afbødningsstrategi. Der er ingen ETA for fuld løsning. Vi vil levere en opdatering inden onsdag, 2026- 08- 19 02: 00 PDT med aktuelle oplysninger. * * symptomer * * Berørte kunder i Australien og New Zealand kan opleve langsommelighed eller 502 fejl, med nogle brugere kort ude af stand til at få adgang til Drive. * * Arbejde omkring * * Ingen på nuværende tidspunkt.

5. 19. august 2026 kl. 08.54 UTCresolved

   * * Oversigt * * Flere kunder i Australien og New Zealand kan opleve langsommelighed eller fejl, mens adgang til Google Drive. * * Beskrivelse * * Vi oplever et problem med Google Drive begynder tirsdag, 2026-08- 18 16: 58 PDT. Vores ingeniørhold arbejder aktivt på en afbødende strategi. Der er ingen ETA for fuld løsning. Vi vil levere en opdatering inden onsdag, 2026-08- 19 03: 00 PDT med aktuelle oplysninger. * * symptomer * * Berørte kunder i Australien og New Zealand kan opleve langsommelighed eller 502 fejl, med nogle brugere kort ude af stand til at få adgang til Drive. * * Arbejde omkring * * Ingen på nuværende tidspunkt.

6. 19. august 2026 kl. 09.54 UTCresolved

   * * Oversigt * * Flere kunder i Australien og New Zealand kan opleve langsommelighed eller fejl, mens adgang til Google Drive. * * Beskrivelse * * Vi oplever et problem med Google Drive begynder tirsdag, 2026-08- 18 16: 58 PDT. Vores ingeniørhold arbejder aktivt på en afbødende strategi. Der er ingen ETA for fuld løsning. Vi vil levere en opdatering inden onsdag, 2026- 08- 19 04: 30 PDT med aktuelle oplysninger. * * symptomer * * Berørte kunder i Australien og New Zealand kan opleve langsommelighed eller 502 fejl, med nogle brugere kort ude af stand til at få adgang til Drive. * * Arbejde omkring * * Ingen på nuværende tidspunkt.

7. 19. august 2026 kl. 11.26 UTCresolved

   * * Oversigt * * Flere kunder i Australien og New Zealand kan opleve langsommelighed eller fejl, mens adgang til Google Drive. * * Beskrivelse * * Vi oplever et problem med Google Drive begynder tirsdag, 2026-08- 18 16: 58 PDT. Vores ingeniørhold arbejder aktivt på en afbødende strategi. Der er ingen ETA for fuld løsning. Vi vil give en opdatering inden onsdag, 2026- 08- 19 06: 00 PDT med aktuelle oplysninger. * * symptomer * * Berørte kunder i Australien og New Zealand kan opleve langsommelighed eller 502 fejl, med nogle brugere kort ude af stand til at få adgang til Drive. * * Arbejde omkring * * Ingen på nuværende tidspunkt.

8. 19. august 2026 kl. 13.05 UTCresolved

   * * Oversigt * * Flere kunder i Australien og New Zealand kan have oplevet langsommelighed eller fejl, mens adgang til Google Drive. * * Beskrivelse * * Problemet med Google Drev er blevet løst for alle berørte kunder fra onsdag, 2026-08- 19 05: 40 PDT. Vores ingeniørhold fastslog, at trægheden var resultatet af en lokal kapacitet og routing problem inden for vores regionale infrastruktur. For at genoprette tjenesten, implementerede vi et fix til at lindre netværkets trængsel og accelererede en planlagt opgradering af infrastrukturen i den berørte region for at sikre normale præstationsniveauer. Vi takker Dem for Deres tålmodighed, mens vi arbejdede på at løse problemet. * * symptomer * * Berørte kunder i Australien og New Zealand kan have oplevet langsommelighed eller 502 fejl, med nogle brugere kort ude af stand til at få adgang til Drive. * * Arbejde omkring * * Spørgsmålet er nu løst

9. 20. august 2026 kl. 20.00 UTCresolved

   # Foreløbig hændelsesrapport Vi undskylder for forstyrrelsen af din forretning. Vi ved, hvor meget du stoler på Google Workspace, og vi beklager virkningen på din produktivitet. Vi arbejder på at tage fat på den grundlæggende årsag og forhindre, at dette sker i fremtiden. Bemærk venligst, at disse oplysninger er baseret på vores bedste viden på udstationeringstidspunktet og kan ændres, efterhånden som vores undersøgelse fortsætter. En endelig hændelsesrapport med forebyggende handlinger vil blive offentliggjort, når vores undersøgelse er færdig. Hvis du har oplevet en effekt uden for det, der er anført nedenfor, bedes du kontakte Google Workspace Support ved hjælp af hjælpeartiklen [*] https: / / support.google.com / a / weak / 1047213 * *] (https: / / support.google.com / a / week / 1047213). # # Tidspunkt for udstedelsen (All time US / Pacific) Hændelse Start: 18 August 2026 16: 58 Hændelse slut: 19 August 2026 05: 40 Varighed: 12 timer, 42 minutter # # Summary Den 18. august 2026 fra 16: 58 til 19 august 2026 05: 40 US / Pacific, Drive kunder i Australien, Filippinerne og New Zealand oplevede forringet ydeevne og langsommelighed. I denne periode oplevede brugerne også 502 fejl. Andre Google Workspace-tjenester blev ikke påvirket. # Foreløbig rodårsag Google bruger en alsidig global lastbalancering og netværksrouting arkitektur til at tjene trafikken effektivt. For at sikre en retfærdig anvendelse og forhindre overbelastning forvaltes båndbreddefordelingen ved at tildele trafik til specifikke downstream-tjenester. En forkert konfiguration i tildelingen af trafik forårsaget af båndbredde brug at være forkert tilskrives frontend netværk load balancering tier selv, snarere end Drev-tjenesten. Sekvensen af begivenheder, der førte til kundernes indflydelse var som følger: * Trafikken fra det regionale balanceringsniveau blev fejlagtigt tilskrevet lastbalanceringsinfrastrukturen snarere end Drive-tjenesten. * Urelateret trafik forårsaget netbåndbredde brug tilskrives lastbalanceringsinfrastrukturen i denne region til at overstige sin kvote. * Network båndbredde management systemer anvendes væltning til denne trafik til at håndhæve kvoter, forårsager alvorlige netoverbelastning påvirker Drive trafik i denne region. * Denne trængsel førte til øget latency, langsommelighed, og fejlrater for brugere adgang Drive i de berørte regioner. # Respiration Google ingeniører blev advaret om problemet via automatiseret overvågning og en tilstrømning af kundesupport sager, med indledende hændelsesrespons hold engageret af 17: 21 US / Pacific den 18 august 2026\. Ingeniørerne forsøgte oprindeligt at mindske overbelastningen ved at tømme den regionale trafik til en alternativ geografisk placering, men dette viste sig at være ineffektivt og blev vendt tilbage. Holdet afbødede derefter problemet ved at migrere regional trafik til en opgraderet intern netværk routing arkitektur, som korrekt indstille trafik tildeling til Drive. Den normale drift blev fuldstændig genoprettet, da 100% af den regionale trafik blev migreret til den opgraderede netarkitektur. # Beskrivelse af virkning Mellem 18. august 2026, kl. 16: 58 US / Pacific og 19. august 2026, kl. 05: 40 US / Pacific, oplevede Google Drive-brugere i Australien, Filippinerne og New Zealand alvorlig latency, forringet ydeevne og 502 fejl. I løbet af dette omkring 12- time og 42- minut vindue, kan berørte kunder har observeret betydelig langsommelighed eller fejl, når du forsøger at få adgang til Google Drev eller liste filer gennem Editors (fx [docs.google.com] (http: / / docs.google.com), med indledende belastningstider betydeligt forsinket. Spørgsmålet blev fuldt afbødet fra august 19, 2026, på 05: 40 US / Pacific, og normal service er blevet genoprettet.

10. 24. august 2026 kl. 16.31 UTCresolved

    # Incident Report # # Summary Tirsdag den 18. august 2026 kl. 16: 58 OS / Pacific opstod en hændelse, der påvirkede Google Drive i en periode på 12 timer og 42 minutter. Kunder beliggende i Australien, Filippinerne og New Zealand oplevede alvorlig latency, sporadisk loading fejl og fejl, når de får adgang til Google Drive. Til vores værdsatte Google Workspace-kunder, er vi dybt kede af den service afbrydelse, du oplevede. Vi træffer omgående og beslutsomme foranstaltninger for at løse problemet og styrke vores systemer mod fremtidige hændelser. Andre Google Workspace-tjenester blev ikke påvirket. # Root Cause Google bruger en alsidig global lastbalancering og netværksrouting arkitektur til at tjene trafikken effektivt. For at sikre en retfærdig anvendelse og forhindre overbelastning forvaltes båndbreddefordelingen ved at tildele trafik til specifikke downstream-tjenester. En forkert konfiguration i tildelingen af trafik forårsaget af båndbredde brug at være forkert tilskrives frontend netværk load balancering tier selv, snarere end Drev-tjenesten. Sekvensen af begivenheder, der førte til kundernes indflydelse var som følger: * Trafikken fra det regionale balanceringsniveau blev fejlagtigt tilskrevet lastbalanceringsinfrastrukturen snarere end Drive-tjenesten. * Urelateret trafik forårsaget netbåndbredde brug tilskrives lastbalanceringsinfrastrukturen i denne region til at overstige sin kvote. * Network båndbredde management systemer anvendes væltning til denne trafik til at håndhæve kvoter, forårsager alvorlige netoverbelastning påvirker Drive trafik i denne region. * Denne trængsel førte til øget latency, langsommelighed, og fejlrater for brugere adgang Drive i de berørte regioner. # Rengøring og forebyggelse Google ingeniører blev advaret om problemet via automatiseret overvågning og en tilstrømning af kundesupport tilfælde, med indledende hændelsesrespons hold engageret af 17: 21 US / Pacific den 18 august, 2026\. Ingeniørerne forsøgte oprindeligt at mindske overbelastningen ved at tømme den regionale trafik til en alternativ geografisk placering, men dette viste sig at være ineffektivt og blev vendt tilbage. Holdet afbødede derefter problemet ved at migrere regional trafik til en opgraderet intern netværk routing arkitektur, som korrekt indstille trafik tildeling til Drive. Normal drift blev fuldt restaureret kl. 05: 40, da 100% af den regionale trafik blev migreret til den opgraderede netværk arkitektur. For at forhindre en gentagelse af dette problem, vores ingeniørhold er i gang med følgende strukturelle forebyggende foranstaltninger: * * * Resilient Network Protocol Migration: * * Vi fremskynder den fuldstændige migration af al regional frontend trafik til den nyere, robuste netværk routing protokol for at sikre præcis båndbredde tildeling under alle overbelastning scenarier. * * * Delegation Root Årsag Opbedring: * * Vi tager fat på den underliggende mekanisme, der forårsagede den forkerte uddelegering og analyse af lignende sager i hele flåden for at sikre, at den ikke gentager sig. # Detaljeret beskrivelse af virkning Fra 18 august 2026, 16: 58 til 19 august 2026, 05: 40 US / Pacific i en varighed af 12 timer, 42 minutter, Google Drive-brugere i Australien, Filippinerne og New Zealand oplevede alvorlig forringelse af ydeevnen, herunder høj latency og fejl adgang til Drev eller liste filer via redaktører. Service blev fuldt restaureret fra 19 August, 05: 40 US / Pacific. * * Google Drive: * * * Forhøjet latency: Brugere oplevede ekstrem langsommelighed, når du indlæser Drev interface eller adgang til filer, med indledende data hentning gange stærkt forsinket. * Indlæsning Fejl og fejl: Mange brugeranmodninger timet ud eller returneret HTTP 502 fejl på grund af den aggressive netværk throttling droppe forbindelserne. * * Anvendelsesområde Udelukkelse: * * * Kunder, der fik adgang til Google Drive fra uden for Australien, Filippinerne og New Zealand var stort set upåvirket af denne lokaliserede throttling begivenhed. * Andre Google Workspace-applikationer, der ikke er afhængige af denne specifikke routingsti, forblev stabile under hændelsesvinduet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. august 2026 kl. 19.35 UTCresolved

   * * Oversigt: * * Undersøgelse af adgangsproblemer med Classrooms nye hjemmeside. * * Beskrivelse: * * Vi undersøger rapporter om adgangsproblemer med Classrooms nye hjemmeside begynder torsdag, 2026-08-13. Vores ingeniørhold arbejder i øjeblikket på en potentiel rettelse, mens vi fortsætter med at undersøge den fulde rod årsag. Vi vil levere en opdatering inden tirsdag, 2026-08- 18 13: 00 PDT med aktuelle oplysninger. Vi undskylder over for alle, der er berørt af afbrydelsen. * * Symptomer: * * Administration og nogle lærere kan opleve tilladelsesfejl, når de får adgang til Classrooms nye hjemmeside. * * Arbejde omkring: * * Brugerne bør stadig være i stand til at navigere til andre visninger fra venstre side af grænsefladen.

2. 18. august 2026 kl. 20.00 UTCresolved

   * * Oversigt: * * Afbryder adgangsproblemer med Classrooms nye hjemmeside. * * Beskrivelse: * * Mitigation arbejde er i øjeblikket i gang af vores ingeniør team. Afbødningen forventes at være afsluttet inden tirsdag, 2026- 08- 18 14: 00 PDT. Vi vil give mere information på tirsdag, 2026-08- 18 14: 15 PDT. * * Symptomer: * * Administration og nogle lærere kan opleve tilladelsesfejl, når de får adgang til Classrooms nye hjemmeside. * * Arbejde omkring: * * Brugerne bør stadig være i stand til at navigere til andre visninger fra venstre side af grænsefladen.

3. 18. august 2026 kl. 20.27 UTCresolved

   * * Oversigt: * * Afbryder adgangsproblemer for Workspace Leveres med Classrooms hjemmeside. * * Beskrivelse: * * Vores ingeniør har identificeret årsagen og afbødende arbejde er i gang. Den afbødende udrulning forventes at tage flere timer. Vi vil give mere information inden onsdag, 2026-08- 19 8: 00 PDT. * * Symptomer: * * Workspace Administration kan opleve tilladelsesfejl, når adgang til Classrooms hjemmeside. Resterende Classroom funktionalitet forbliver upåvirket. Classroom Mobile App og Classroom API er upåvirket af problemet. * * Arbejde omkring: * * Alle andre sider er upåvirkede og administratorer kan navigere til andre sider ved hjælp af venstre rude på grænsefladen. Workspace Administration kan stadig oprette klasser uden problemer. Workspace Administratorer kan også se de kurser, de er i ved at gå til https: / / classroom.google.com / h / tv

4. 18. august 2026 kl. 23.02 UTCresolved

   * * Oversigt * * [Mislykket] Adgangsproblemer til Workspace Leveres med Classrooms hjemmeside. * * Beskrivelse * * Problemet med Classroom er blevet løst for alle berørte brugere fra tirsdag, 2026-08- 18 15: 30 PDT. Fra indledende analyse, problemet blev udløst på grund af en nylig ændring, som forårsagede tilladelse mismatch, vores Engineering team har rullet ud fix for at afbøde virkningen. Vi takker Dem for Deres tålmodighed, mens vi arbejdede på at løse problemet. * * symptomer * * Workspace Administration kan have oplevet tilladelsesfejl, når adgang til Classrooms hjemmeside. Resterende Classroom funktionalitet forblev upåvirket. The Classroom Mobile App og Classroom API var upåvirket af problemet. * * Arbejde omkring * * Ingen som problemet er løst

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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.