Platform Google SSO failure

Update timeline

1. identified Feb 09, 2026, 11:36 PM UTC

   The app.fluidattacks.com platform is experiencing access issues affecting users attempting to log in via Google SSO.

2. resolved Feb 09, 2026, 11:37 PM UTC

   The incident has been resolved and access to the platform via Google SSO has been restored.

3. postmortem Feb 10, 2026, 02:08 PM UTC

   **Impact** At least one internal user experienced failed login attempts while using Google SSO on the platform. The issue started on UTC-5 26-02-09 17:55 and was proactively discovered 14.4 minutes \(TTD\) later by a staff member who reported through our internal channels that users trying to sign in could not access their accounts, although no external customers reported problems. The problem was resolved in 5.7 minutes \(TTF\), resulting in a total window of exposure of 20.1 minutes \(WOE\) [\[1\]](https://gitlab.com/fluidattacks/universe/-/issues/20397). **Cause** During a deployment, the old Google OAuth token was removed before a critical post-deployment job finished. This caused the platform to temporarily reject Google SSO logins [\[2\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/94377). **Solution** Wait for the post-deployment job to complete. Once the job finished, the Google SSO login was restored [\[3\]](https://gitlab.com/fluidattacks/universe/-/jobs/13048056424). **Conclusion** To prevent this from happening again, the OAuth token should not be removed, invalidated, or deactivated until the related post-deployment processes have fully completed. **COMMUNICATION\_FAILURE < INFRASTRUCTURE\_ERROR < INCOMPLETE\_PERSPECTIVE**