Google Workspace Status : Admin Console - AVAILABLE - 2026-01-21 12:39:29 UTC

[back...@gmail.com]

Product: Admin Console
Status: AVAILABLE
Published: 2026-01-21 12:39:29 UTC

## 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.
Date/Time of the Issue (All time US/Pacific)
Incident Start: 19 January 2026, 10:10
Incident End: 20 January 2026 11:49
Duration: 1 day, 1 hour 39 minutes
## Summary
Starting 19 January at 10:10, Google Workspace customers may have
experienced missing account metadata, including primary email address
and account creation time in the Admin Console for a duration of 1
day, 1 hour and 39 minutes. To our Workspace customers whose services
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
This incident was identified to be caused by corrupted user account
metadata in a secondary data store, triggered by a faulty code change.
In Google's infrastructure, user account information is maintained in
a primary backend system of record. This data is periodically
synchronized to secondary data stores, which applications such as the
Admin Console use to retrieve and display user profile information.
The trigger for this incident was a faulty code change deployed to a
synchronization job. This change caused the job to malfunction and
write invalid or empty information into the secondary data store for a
subset of user accounts. Although the correct user data remained
intact in the primary backend system of record, the corrupted copy in
the secondary data store was served to dependent services.
Google will complete a full Incident report in the following days that
will provide a full root cause.
## Remediation
Google engineers were alerted to the issue via support case on 20
January at 03:32. Engineering quickly identified a faulty code change
that was deployed to a synchronization job as the source of the issue.
A rollback of the application service was performed in parallel with
synchronizing the data for affected users from the primary backend
account system. A script was run to accomplish this, correcting the
data for affected accounts. The script was deployed in batches, which
led to the mitigation of the affected accounts and restored services
on 20 January at 11:49.
## Description of Impact
Between 19 January, 10:10 and 20 January, 11:49,
Admin Console: Administrators searching for or viewing users may have
seen empty fields for primary email addresses and an incorrect account
creation date of "January 1, 1970". The issue may have also affected
the display of user information where a user's email address would
normally be present (such as in Reporting or Activity events).
Directory API: Applications accessing the Directory API, such as
Google Cloud Directory Sync (GCDS), may have received responses with
missing fields including email and account creation metadata.
Single Sign-On (SSO): Some customers experienced SSO failures for
external services that rely on Google Workspace as an identity
provider.

Link to official detail of this status:
https://www.google.com/appsstatus/dashboard/incidents/9q5n4sfDnxYzHj8FxEua