# Summary

- Provider: [Google Workspace](https://down.guide/google-workspace)
- Level: confirmed
- Impact: Partial outage
- lasted 12h 42m
- started 2026-04-10 02:08 UTC
- Admin Console
- id: DWN-3a8bf6595e
- Official page: https://www.google.com/appsstatus/dashboard/incidents/JTgxXCtXTaw3aEVzUUfa

## Updates from Google Workspace
### 2026-04-10 10:07 UTC: service\_disruption
\*\*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.

### 2026-04-10 10:55 UTC: service\_disruption
\*\*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.

### 2026-04-10 11:27 UTC: service\_disruption
\*\*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.

### 2026-04-10 15:06 UTC: resolved
\*\*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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).