CompaniesGoogle WorkspaceIncidents
Google Workspace: **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.
Affected components: Admin Console
Timeline of updates
- 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. - 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. - 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. - 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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
b85f211a9b3ae08d…
Impact, status and times are the vendor’s own, as last archived. View on www.google.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Google Workspace, started 2026-04-10 02:08 UTC, resolved after 13 h, 4 update(s).
- Title
- **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.
- Vendor
- Google Workspace
- Date
- URL
- https://rewindex.com/company/google-workspace/incidents/jtgxxctxtaw3aevzuufa
Google Workspace profileRecent Google Workspace incidentsAll outages on April 10, 2026Google Workspace in April 2026MarkdownJSON