Google Workspace 장애 기록

1. 2026년 8월 28일 PM 7:25 UTCresolved

   ** 일정:** Google Chat 사용자는 새로운 메시지에 대한 알림을받을 수있는 문제가 있습니다. 그러나 실제 메시지는 사용자가 자신의보기를 새로 고침하지 않고 채팅 응용 프로그램에 나타나지 못합니다. ** 설명:** 우리는 구글 채팅 금요일, 2026-08-28 10:25 PDT와 간헐적인 문제를 경험하고있다. 우리의 엔지니어링 팀은 문제를 조사하고 현재 문제를 완화하기 위해 노력하고 있습니다. 우리는 현재 세부사항을 가진 금요일, 2026-08-28 14:15 PDT에 의하여 정보를 더 제공할 것입니다. 우리는 혼란에 의해 영향을받는 모든 사람들에게 사과합니다. **고객 증상:** 사용자는 새로운 메시지에 대한 알림을 수신하는 문제가 발생하지만, 실제 메시지는 사용자가 자신의보기를 새로 고침하지 않는 한 채팅 응용 프로그램에 나타나지 못합니다. **지역:** 사용자는 새 메시지를 볼 수 있습니다

2. 2026년 8월 28일 PM 8:55 UTCresolved

   ** 일정 ** Google Chat 사용자는 새로운 메시지에 대한 알림을 수신 한 문제를 경험했지만 사용자가 자신의보기를 새로 고침 한 경우 실제 메시지가 채팅 응용 프로그램에 나타나지 못했습니다. ** 설명** Google Chat의 문제점은 금요일, 2026-08-28 13:45 PDT로 모든 영향을받는 사용자를 위해 해결되었습니다. 사전 분석에서 문제는 영향을 미칩니다. 우리는 문제를 해결하기 위해 일하면서 당신의 인내에 감사드립니다. **고객 증상 ** 사용자는 새로운 메시지에 대한 알림을 수신 한 문제가 발생했지만 사용자가 자신의보기를 새로 고침 한 경우 실제 메시지가 채팅 응용 프로그램에 나타나지 못했습니다. ** 주변 ** 문제는 해결되지 않습니다.

3. 2026년 9월 4일 AM 3:43 UTCresolved

   ## Incident 보고서 ## 요약 금요일, 8 월 28, 2026, 사이 10:50 미국 / 태평양과 13:34 미국 / 태평양 2 시간 및 44 분의 기간 동안, 구글 채팅 사용자는 웹, 데스크탑 및 모바일 응용 프로그램에 걸쳐 활성 대화 스트림 내에서 실시간 수신 메시지를 수신하는 데 지연을 경험. 사용자가 새로운 메시지에 대한 알림을 수신하는 동안, 메시지 내용은 사용자가 수동으로 응용 프로그램을 새로 고침하거나 응답 메시지를 보내 때까지 활성 대화 스트림을 자동으로 렌더링하지 않았다. 우리의 소중한 Google Workspace 고객에게, 우리는 경험있는 서비스 중단을 위해 심하게 미안합니다. 우리는 문제를 해결하고 미래 사건에 대한 우리의 시스템을 강화하기 위해 즉각적인 행동을 수행하고 있습니다. ## 뿌리 원인 사건은 글로벌 데이터베이스 스키마 롤아웃 중에 방아쇠를 겪었습니다. 잘못된 데이터베이스 schema 변경은 메시지 전달에 필요한 데이터베이스를 작성하여 실패를 시작합니다. 특히, 스키마 동기화 메커니즘 - 기본 저장과 라이브 메시지 배달 사이의 높은 일관성을 보장하기 위해 설계 - 드문 레이스 조건 버그를 수용. 읽지 않은 스키마 상태에 대한 쓰기를 시도하기 위해이 기인한 백엔드 메시지 파견사. 실시간 메시지 배송은 사용자가 화면에 이벤트를 밀어하기 전에이 글에 대한 활성 의존도를 가지고 있기 때문에 동기화 지연을 경험하기 위해 들어오는 메시지가 발생했습니다. 별도의 푸시 알림 서비스 및 핵심 메시지 저장은 독립적으로 운영되며 사용자가 여전히 새로운 메시지에 대한 경고를 받았고, 활성 대화가 숙련 된 지연이 발생했습니다. ## 치료 및 예방 이 문제는 전송 오류율에 대한 자동화 된 백업 경고를 통해 감지 된 고객 보고서와 함께. Google Engineering initiated Parallel workstreams는 서비스를 복원합니다. * 12:44 US/Pacific, Google Engineering은 직접 메시지 전달이 실패 데이터베이스 쓰기에 실패 한 의존도를 제거하여 문제의 소스를 마이그레이션. 이것은 실패한 쓰기를 우회하는 새로운 들어오는 메시지가 허용하고 즉시 사용자 스크린에 정상적인 순간 납품을 재개합니다. * 13:00 US/Pacific, Engineering halted and reverted the database schema change to its Previous Verified stable version, 전체 데이터베이스 호환성 복원. * 13:34 US/Pacific, 할당 된 메시지로 처리 된, 실시간 메시지 동기화 지연은 모든 고객 도메인에서 0%로 반환됩니다. 전체 서비스 건강이 0 메시지 손실로 복원 된 것을 확인했습니다. 이런 일이 다시 발생하면 다음과 같은 예방 조치를 시행하고 있습니다. * ** 내부 검출 : ** 자동화된 검증 및 검증을 통해 사전 제작 및 내부 롤아웃 단계에 걸쳐 이러한 특정 실패 시나리오를 커버합니다. 이것은 어떤 고객 교통이 미래에 영향을 미칠 수 있기 전에 내부적으로 잡기 및 mitigate schema incompatibilities 및 동기화 가장자리 케이스를 고려합니다. * ** 레이스 조건에 대한 탄력 : ** 건축 개선을 구현하는 스키마 동기화 및 메시지 전달 아키텍처는 레이스 조건에 탄력. 이것은 배경 스키마 및 구성 동기화 inconsistencies가 실시간 메시지 전달을 방해 할 수 있도록하는 것을 목표로합니다. ## 충격의 상세한 묘사 사건 충격 창은 10:50 US/Pacific와 13:34 미국/태평양 사이 발생, 28 8월 2026\. 이 문제는 모든 Google 채팅 환경에 적용됩니다. ** 구글 채팅:** ***Delayed 메시지 렌더링:** 새로운 메시지는 활성 대화 스트림에 자동으로 나타나지 않았습니다. 사용자는 수동으로 클라이언트를 새로 고침하거나 동기화 할 스트림을 강제하기 위해 새로운 메시지 / 사실을 보낼 필요가있다. ***Stalled read states와 inbox 정렬:** 읽지 않은 배지와 같은 배경 행동은 inbox의 상단에 활성 공간을 이동, 무거운 내부 오류율을 경험하고 사용자에게 크게 지연되었다. * **검색 색인 지연:** 아웃리지 창에서 전송된 새로운 메시지는 인덱스 라인에 배치되어 검색할 수 있는 지연을 경험합니다. ** 포함: ** * ** 데이터 손실 없음: ** 고객 데이터가 분실되거나 손상되지 않았습니다. 사건 창에서 전송된 모든 메시지는 1 차적인 저장에서 안전하게 붙잡고 backlog가 명확하게 한 대화 시내에 성공적으로 전달되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 19일 AM 3:57 UTCresolved

   ** 일정 ** 몇몇 고객은 Google 드라이브를 사용하는 동안 느린 경험을 경험할 수 있습니다. ** 설명** 우리는 구글 드라이브 시작 화요일, 2026-08-18 16:58 PDT와 문제가 있습니다. 우리의 엔지니어링 팀은 현재 전체 루트 원인을 조사하는 동안 잠재적 인 수정에 노력하고 있습니다. 우리는 화요일, 2026-08-18 22:00 PDT에 의해 업데이트를 제공합니다. 우리는 혼란에 의해 영향을받는 모든 사람들에게 사과합니다. **석** Affected 고객은 Google 드라이브를 사용하는 동안 느린 경험을 경험할 수 있습니다. ** 주변 ** 이 시간에 아무도.

2. 2026년 8월 19일 AM 4:59 UTCresolved

   ** 일정 ** 호주 및 뉴질랜드의 여러 고객은 Google 드라이브를 사용하여 느린 또는 오류를 경험할 수 있습니다. ** 설명** 우리는 구글 드라이브 시작 화요일, 2026-08-18 16:58 PDT와 문제가 있습니다. 우리의 엔지니어링 팀은 현재 전체 루트 원인을 조사하는 동안 잠재적 인 수정에 노력하고 있습니다. 우리는 수요일, 2026-08-19 00:30 PDT에 의해 업데이트를 제공합니다. **석** 호주 및 뉴질랜드의 고객 만족은 Google 드라이브를 사용하는 동안 느린 또는 오류를 경험할 수 있습니다. 일부 고객은 짧은 기간 동안 드라이브에 액세스 할 수있는 502 오류를 관찰 할 수 있습니다. ** 주변 ** 이 시간에 아무도.

3. 2026년 8월 19일 AM 6:49 UTCresolved

   ** 일정 ** 호주 및 뉴질랜드의 여러 고객은 Google 드라이브에 액세스하면서 느린 또는 오류를 경험할 수 있습니다. ** 설명** 우리는 구글 드라이브 시작 화요일, 2026-08-18 16:58 PDT와 문제가 있습니다. 우리의 엔지니어링 팀은 문제의 뿌리 원인을 확인하고 완화 전략에 적극적으로 노력하고 있습니다. 풀 해상도의 ETA가 없습니다. 우리는 수요일, 2026-08-19 01:30 PDT에 의해 업데이트를 제공합니다. **석** 호주와 뉴질랜드의 고객 만족은 느린 또는 502 오류를 경험할 수 있으며, 일부 사용자는 드라이브에 액세스 할 수 없습니다. ** 주변 ** 이 시간에 아무도.

4. 2026년 8월 19일 AM 7:59 UTCresolved

   ** 일정 ** 호주 및 뉴질랜드의 여러 고객은 Google 드라이브에 액세스하면서 느린 또는 오류를 경험할 수 있습니다. ** 설명** 우리는 구글 드라이브 시작 화요일, 2026-08-18 16:58 PDT와 문제가 있습니다. 우리의 엔지니어링 팀은 문제의 뿌리 원인을 확인하고 완화 전략에 적극적으로 노력하고 있습니다. 풀 해상도의 ETA가 없습니다. 우리는 수요일에 의해 업데이트를 제공 할 것입니다, 2026-08-19 02:00 PDT 현재 세부 사항. **석** 호주와 뉴질랜드의 고객 만족은 느린 또는 502 오류를 경험할 수 있으며, 일부 사용자는 드라이브에 액세스 할 수 없습니다. ** 주변 ** 이 시간에 아무도.

5. 2026년 8월 19일 AM 8:54 UTCresolved

   ** 일정 ** 호주 및 뉴질랜드의 여러 고객은 Google 드라이브에 액세스하면서 느린 또는 오류를 경험할 수 있습니다. ** 설명** 우리는 구글 드라이브 시작 화요일, 2026-08-18 16:58 PDT와 문제가 있습니다. 우리의 엔지니어링 팀은 완화 전략에 적극적으로 노력하고 있습니다. 풀 해상도의 ETA가 없습니다. 우리는 현재 세부사항을 가진 수요일, 2026-08-19 03:00 PDT에 의하여 갱신을 제공할 것입니다. **석** 호주와 뉴질랜드의 고객 만족은 느린 또는 502 오류를 경험할 수 있으며, 일부 사용자는 드라이브에 액세스 할 수 없습니다. ** 주변 ** 이 시간에 아무도.

6. 2026년 8월 19일 AM 9:54 UTCresolved

   ** 일정 ** 호주 및 뉴질랜드의 여러 고객은 Google 드라이브에 액세스하면서 느린 또는 오류를 경험할 수 있습니다. ** 설명** 우리는 구글 드라이브 시작 화요일, 2026-08-18 16:58 PDT와 문제가 있습니다. 우리의 엔지니어링 팀은 완화 전략에 적극적으로 노력하고 있습니다. 풀 해상도의 ETA가 없습니다. 우리는 수요일, 2026-08-19 04 : 30 PDT 현재의 세부 정보를 제공합니다. **석** 호주와 뉴질랜드의 고객 만족은 느린 또는 502 오류를 경험할 수 있으며, 일부 사용자는 드라이브에 액세스 할 수 없습니다. ** 주변 ** 이 시간에 아무도.

7. 2026년 8월 19일 AM 11:26 UTCresolved

   ** 일정 ** 호주 및 뉴질랜드의 여러 고객은 Google 드라이브에 액세스하면서 느린 또는 오류를 경험할 수 있습니다. ** 설명** 우리는 구글 드라이브 시작 화요일, 2026-08-18 16:58 PDT와 문제가 있습니다. 우리의 엔지니어링 팀은 완화 전략에 적극적으로 노력하고 있습니다. 풀 해상도의 ETA가 없습니다. 우리는 현재 세부사항을 가진 수요일, 2026-08-19 06:00 PDT에 의하여 갱신을 제공할 것입니다. **석** 호주와 뉴질랜드의 고객 만족은 느린 또는 502 오류를 경험할 수 있으며, 일부 사용자는 드라이브에 액세스 할 수 없습니다. ** 주변 ** 이 시간에 아무도.

8. 2026년 8월 19일 PM 1:05 UTCresolved

   ** 일정 ** 호주 및 뉴질랜드의 여러 고객은 Google 드라이브에 액세스하면서 느린 또는 오류를 경험할 수 있습니다. ** 설명** Google 드라이브의 문제는 수요일, 2026-08-19 05:40 PDT로 모든 영향을받는 고객을 위해 해결되었습니다. 우리의 엔지니어링 팀은 지역 인프라 내에서 현지화된 용량과 라우팅 문제의 결과로 결정되었습니다. 서비스를 복원하려면 네트워크 혼잡을 완화하고 영향을받는 지역에서 계획 된 인프라 업그레이드를 가속화하여 정상 성능 수준을 보장합니다. 우리는 문제를 해결하기 위해 일하면서 당신의 인내에 감사드립니다. **석** 호주와 뉴질랜드에서 고객 만족은 느린 또는 502 오류를 경험할 수 있으며 일부 사용자는 드라이브에 액세스 할 수 없습니다. ** 주변 ** 이 문제는 이제 mitigated

9. 2026년 8월 20일 PM 8:00 UTCresolved

   # Preliminary Incident 보고서 우리는 진심으로 당신의 사업에 기인한 이 사건에 대한 사과. Google Workspace에 얼마나 의존했는지 알고 있으며 생산성에 영향을 줄 수 있습니다. 우리는 뿌리 원인을 해결하고 미래에 발생하는 것을 방지하기 위해 노력하고 있습니다. 참고,이 정보는 우리의 가장 좋은 지식에 근거하여 게시물의 시간에 따라 계속 우리의 조사로 변경 될 수 있습니다. 우리의 조사가 완료되면 예방 조치와 최종 소득 보고서가 게시됩니다. 아래 나열된 내용 밖에도 경험이 풍부한 영향을 받으면 도움말 문서를 사용하여 Google Workspace Support에 도달하십시오 [**https://support.google.com/a/answer/1047213**](https://support.google.com/a/answer/1047213). ## 발행일/시간 (모든 시간 US/Pacific) 법인 시작: 18 8월 2026 16:58 법인 끝: 19 8월 2026 05:40 소요시간: 12시간, 42분 ## 요약 에 8월 18, 2026 에서 16:58 에 8월 19, 2026 05:40 미국/태평양, 호주, 필리핀 및 뉴질랜드에 있는 고객을 몰고 성능과 느림을 경험했습니다. 이 기간 동안 사용자는 또한 502 오류를 경험했습니다. 다른 Google Workspace 서비스는 영향을받지 않았습니다. ## 예비 뿌리 원인 Google은 멀티 계층 글로벌 로드 밸런싱 및 네트워크 라우팅 아키텍처를 활용하여 트래픽을 효율적으로 제공합니다. 공정한 사용을 보장하고 혼잡을 방지하기 위해, 대역폭 할당은 특정한 다운스트림 서비스에 attributing 교통에 의해 관리됩니다. 트래픽의 attribution에 있는 misconfiguration는 드라이브 서비스에 비해 프론트엔드 네트워크 로드 밸런싱 계층 자체에 잘못된 특성으로, 대역폭 사용량이 발생했습니다. 고객 영향에 대한 이벤트의 순서는 다음과 같습니다. * 지역 부하 밸런싱 계층의 트래픽은 드라이브 서비스보다 오히려 부하 밸런싱 인프라에 확실히 속성이었다. * 관련 트래픽이 발생하지 않는 네트워크 대역폭 사용은 이 지역의 로드 밸런싱 인프라에 따라 할당량을 초과합니다. * 네트워크 대역폭 관리 체계는 이 지역에 있는 드라이브 교통에 영향을 미치는 가혹한 네트워크 혼잡을 일으키는 원인이 되기 위하여 이 교통에 throttling를 적용했습니다. * 이 혼잡은 영향을받는 지역에서 드라이브에 액세스하는 사용자를위한 대기 시간, 느린 및 오류율을 증가시켰다. ## 구제 Google 엔지니어는 자동화 된 모니터링 및 고객 지원 사례의 영향력을 통해 문제로 경고했습니다. 초기 사건 응답 팀은 8 월 17 : 21 US / Pacific, 2026 \에 참여했습니다. 엔지니어는 처음에는 지역 프론트 엔드 트래픽을 대체 지리적 위치에 배수함으로써 혼잡을 완화하려고했지만, 이것은 효과적이고 역동적이었습니다. 이 팀은 지역 트래픽을 업그레이드 된 내부 네트워크 라우팅 아키텍처로 마이그레이션하여 문제를 mitigated. 이는 제대로 드라이브에 대한 트래픽 특성 설정. 일반 작업은 지역 트래픽의 100 %가 업그레이드 된 네트워크 아키텍처로 마이그레이션되었습니다. ## 충격의 묘사 사이 8월 18, 2026, 에 16:58 미국/태평양과 8월 19, 2026, 에 05:40 미국/태평양, 호주에 있는 구글 드라이브 사용자, 필리핀과 뉴질랜드는 심각한 대기권, degraded 성과 및 502 오류를 경험했습니다. 이 약 12 시간 및 42 분 창 동안 영향을받은 고객은 Google 드라이브에 액세스하거나 편집기를 통해 파일을 목록으로 만들기 위해 시도 할 때 상당한 느리거나 오류를 관찰 할 수 있습니다 (예 : [docs.google.com] (http://docs.google.com)), 초기 부하 시간 크게 지연. 이 문제는 8 월 19 일 2026 년 8 월 19 일, 05 : 40 US / Pacific에서 완전히 mitigated이며, 정상 서비스는 복원되었습니다.

10. 2026년 8월 24일 PM 4:31 UTCresolved

    # Incident 보고서 ## 요약 화요일, 18 8 월 2026 16 : 58 미국 / 태평양, Google 드라이브에 영향을 미치는 사건은 12 시간과 42 분의 기간 동안 발생했습니다. 호주, 필리핀 및 뉴질랜드에 위치한 고객은 Google Drive에 액세스 할 때 심각한 대기 시간, 특수 로드 실패 및 오류를 경험했습니다. 우리의 소중한 Google Workspace 고객에게, 우리는 경험있는 서비스 중단을 위해 심하게 미안합니다. 우리는 문제를 해결하고 미래 사건에 대한 우리의 시스템을 강화하기 위해 즉각적인 행동을 수행하고 있습니다. 다른 Google Workspace 서비스는 영향을받지 않았습니다. ## 뿌리 원인 Google은 멀티 계층 글로벌 로드 밸런싱 및 네트워크 라우팅 아키텍처를 활용하여 트래픽을 효율적으로 제공합니다. 공정한 사용을 보장하고 혼잡을 방지하기 위해, 대역폭 할당은 특정한 다운스트림 서비스에 attributing 교통에 의해 관리됩니다. 트래픽의 attribution에 있는 misconfiguration는 드라이브 서비스에 비해 프론트엔드 네트워크 로드 밸런싱 계층 자체에 잘못된 특성으로, 대역폭 사용량이 발생했습니다. 고객 영향에 대한 이벤트의 순서는 다음과 같습니다. * 지역 부하 밸런싱 계층의 트래픽은 드라이브 서비스보다 오히려 부하 밸런싱 인프라에 확실히 속성이었다. * 관련 트래픽이 발생하지 않는 네트워크 대역폭 사용은 이 지역의 로드 밸런싱 인프라에 따라 할당량을 초과합니다. * 네트워크 대역폭 관리 체계는 이 지역에 있는 드라이브 교통에 영향을 미치는 가혹한 네트워크 혼잡을 일으키는 원인이 되기 위하여 이 교통에 throttling를 적용했습니다. * 이 혼잡은 영향을받는 지역에서 드라이브에 액세스하는 사용자를위한 대기 시간, 느린 및 오류율을 증가시켰다. ## 치료 및 예방 Google 엔지니어는 자동화 된 모니터링 및 고객 지원 사례의 영향력을 통해 이슈에 경고했다. 17 : 21 8 월 18 일 미국 / 태평양, 2026 \에 참여한 초기 사건 응답 팀. 엔지니어는 처음에는 지역 프론트 엔드 트래픽을 대체 지리적 위치에 배수함으로써 혼잡을 완화하려고했지만, 이것은 효과적이고 역동적이었습니다. 이 팀은 지역 트래픽을 업그레이드 된 내부 네트워크 라우팅 아키텍처로 마이그레이션하여 문제를 mitigated. 이는 제대로 드라이브에 대한 트래픽 특성 설정. 일반 작업은 완전히 복원되었습니다 05:40 한 번에 지역 트래픽의 100 %가 업그레이드 된 네트워크 아키텍처로 마이그레이션되었습니다. 이 문제의 재발을 방지하기 위해, 우리의 엔지니어링 팀은 다음과 같은 구조적 예방 조치를 취합니다. ***Resilient 네트워크 프로토콜 마이그레이션:** 우리는 모든 지역 프론트 엔드 트래픽의 전체 마이그레이션을 새로운, 탄력성 네트워크 라우팅 프로토콜로 통합하여 모든 혼잡 시나리오에서 정확한 대역폭 특성에 대한 보장을 제공합니다. * **Delegation 뿌리 원인 구제 : ** 우리는 그것을 reoccur하지 않도록 함대에 대한 잘못된 위임과 유사한 사례를 분석하기 위해 부정확한 위임 메커니즘을 해결하고 있습니다. ## 충격의 상세한 묘사 18 8 월 2026, 16 : 58에서 19 8 월 2026, 05 : 40 미국 / 태평양 12 시간, 42 분, 호주의 Google 드라이브 사용자, 필리핀 및 뉴질랜드는 높은 대기 시간 및 오류 액세스 드라이브 또는 편집기를 통해 파일을 목록으로 만들 수있는 심각한 성능 평가를 경험했습니다. 서비스는 19 8 월, 05 : 40 미국 / 태평양으로 완전히 복원되었습니다. ** 구글 드라이브:** * Elevated Latency: 사용자는 드라이브 공용영역을 적재하거나 파일에 접근할 때 극단적으로 느리게 경험했습니다, 처음 자료 retrieval 시간과 더불어. * 로드 실패 및 오류 : 많은 사용자 요청은 공격적인 네트워크 throttling이 연결 떨어지기 때문에 HTTP 502 오류를 중단하거나 반환합니다. **스코프 제외: ** * 호주, 필리핀 및 뉴질랜드 지역에서 Google 드라이브에 액세스하는 고객은이 지역화 된 스로틀링 이벤트에 의해 크게 영향을 미쳤습니다. * 이 특정 여정 경로에 의존하지 않는 다른 Google Workspace 애플리케이션은 사건 창에서 안정적으로 유지됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 18일 PM 7:35 UTCresolved

   ** 일정:** Classroom의 새로운 웹 홈페이지를 통해 액세스 문제를 조사합니다. ** 설명:** Classroom의 새로운 웹 홈페이지가 목요일부터 2026-08-13까지 액세스 문제의 조사 보고서입니다. 우리의 엔지니어링 팀은 현재 전체 루트 원인을 조사하는 동안 잠재적 인 수정에 노력하고 있습니다. 우리는 화요일, 2026-08-18 13 : 00 PDT 현재의 세부 정보를 제공합니다. 우리는 혼란에 의해 영향을받는 모든 사람들에게 사과합니다. **석사:** 관리자 및 일부 교사는 Classroom의 새로운 웹 홈페이지에 액세스 할 때 권한 오류를 경험할 수 있습니다. **지역:** 사용자는 여전히 인터페이스의 왼쪽 손 팬에서 다른 레이아웃을 탐색 할 수 있어야합니다.

2. 2026년 8월 18일 PM 8:00 UTCresolved

   ** 일정:** Classroom의 새로운 웹 홈페이지와의 접근 문제. ** 설명:** Mitigation work는 현재 엔지니어링 팀에 의해 진행 중입니다. 부채는 화요일, 2026-08-18 14:00 PDT에 의해 완료 될 것으로 예상됩니다. 우리는 화요일, 2026-08-18 14:15 PDT에 의해 더 많은 정보를 제공 할 것입니다. **석사:** 관리자 및 일부 교사는 Classroom의 새로운 웹 홈페이지에 액세스 할 때 권한 오류를 경험할 수 있습니다. **지역:** 사용자는 여전히 인터페이스의 왼쪽 손 팬에서 다른 레이아웃을 탐색 할 수 있어야합니다.

3. 2026년 8월 18일 PM 8:27 UTCresolved

   ** 일정:** Classroom의 웹 홈페이지를 통해 Workspace Admins에 대한 접근 문제. ** 설명:** 우리의 공학은 원인과 완화 작업을 현재 진행 중입니다. 완화 롤아웃은 몇 시간 걸릴 것으로 예상됩니다. 우리는 수요일에 의해 더 많은 정보를 제공 할 것입니다, 2026-08-19 8:00 PDT. **석사:** Workspace Admins는 Classroom의 웹 홈페이지에 액세스할 때 권한 오류를 경험할 수 있습니다. Remaining Classroom 기능은 비범죄가 남아 있습니다. Classroom Mobile App과 Classroom API는 문제로 해결되지 않습니다. **지역:** 다른 모든 페이지는 unaffected and admins can explore to other pages using the left hand pane on the interface. Workspace Admins는 여전히 어떤 문제없이 클래스를 만들 수 있습니다. Workspace Admins는 https://classroom.google.com/h/tv로 가는 과정에 있을 수 있습니다

4. 2026년 8월 18일 PM 11:02 UTCresolved

   ** 일정 ** [관련] Classroom의 웹 홈페이지로 Workspace Admins에 대한 접근 문제. ** 설명** 교실의 문제점은 화요일, 2026-08-18 15:30 PDT로 모든 영향을받는 사용자를 위해 해결되었습니다. 예비 분석에서, 문제는 허가 잘못이 발생 한 최근의 변경으로 방아쇠되었다, 우리의 엔지니어링 팀은 충격을 완화하기 위해 수정을 압연했다. 우리는 문제를 해결하기 위해 일하면서 당신의 인내에 감사드립니다. **석** Workspace Admins는 Classroom의 웹 홈페이지에 액세스 할 때 권한 오류를 경험할 수 있습니다. Remaining Classroom 기능은 비정기적으로 유지됩니다. Classroom Mobile 앱과 Classroom API는 문제로 해결되지 않았습니다. ** 주변 ** 문제로 아무도 해결

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 30일 AM 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. 2026년 6월 30일 PM 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. 2026년 6월 30일 PM 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. 2026년 6월 30일 PM 1: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. 2026년 6월 30일 PM 2: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. 2026년 6월 30일 PM 2: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. 2026년 6월 30일 PM 3: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. 2026년 6월 30일 PM 4: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. 2026년 6월 30일 PM 5: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. 2026년 6월 30일 PM 7: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. 2026년 7월 1일 AM 12: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. 2026년 7월 1일 AM 4: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. 2026년 6월 22일 PM 10: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. 2026년 6월 23일 AM 12: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. 2026년 6월 23일 AM 1: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. 2026년 6월 10일 PM 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. 2026년 6월 10일 PM 1: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. 2026년 6월 10일 PM 3: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. 2026년 6월 10일 PM 4: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. 2026년 6월 10일 PM 6: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. 2026년 6월 10일 PM 8: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. 2026년 6월 11일 AM 1: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. 2026년 6월 12일 AM 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. 2026년 6월 16일 PM 5: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. 2026년 5월 31일 AM 4: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. 2026년 5월 31일 AM 5: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. 2026년 6월 2일 AM 3: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. 2026년 6월 4일 PM 8: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. 2026년 5월 21일 PM 3: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. 2026년 5월 21일 PM 4: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. 2026년 5월 20일 AM 1: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. 2026년 5월 20일 AM 3: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. 2026년 5월 20일 AM 4: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. 2026년 5월 13일 PM 5: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. 2026년 5월 16일 AM 2: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. 2026년 5월 18일 PM 9: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. 2026년 5월 19일 PM 9: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. 2026년 5월 22일 AM 12: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. 2026년 5월 22일 PM 6: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. 2026년 5월 5일 PM 11: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. 2026년 5월 6일 AM 3: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. 2026년 5월 6일 PM 7: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. 2026년 5월 7일 PM 11: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. 2026년 5월 8일 AM 1: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. 2026년 5월 8일 AM 5: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. 2026년 5월 8일 AM 7: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. 2026년 5월 8일 AM 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. 2026년 5월 8일 PM 3: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. 2026년 5월 8일 PM 6: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. 2026년 4월 29일 PM 7: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. 2026년 4월 29일 PM 7: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. 2026년 4월 29일 PM 8: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. 2026년 4월 29일 PM 9: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. 2026년 4월 28일 PM 3: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. 2026년 4월 28일 PM 4: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. 2026년 4월 28일 PM 4: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. 2026년 4월 10일 AM 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. 2026년 4월 10일 AM 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. 2026년 4월 10일 AM 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. 2026년 4월 10일 PM 3: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. 2026년 4월 8일 PM 10: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. 2026년 4월 8일 PM 11: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. 2026년 4월 8일 PM 6: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. 2026년 4월 8일 PM 7: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. 2026년 4월 8일 PM 8: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. 2026년 4월 8일 PM 9: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. 2026년 4월 8일 PM 10: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. 2026년 4월 10일 AM 2: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. 2026년 4월 17일 AM 9: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. 2026년 3월 21일 AM 3: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. 2026년 3월 21일 AM 3: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. 2026년 3월 21일 AM 5: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. 2026년 3월 21일 AM 7: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. 2026년 3월 13일 PM 1: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. 2026년 3월 13일 PM 2: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. 2026년 3월 13일 PM 2: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. 2026년 2월 23일 AM 8: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. 2026년 2월 23일 AM 8: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. 2026년 2월 23일 AM 8: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.