Companies / Supabase / incidents

Supabase: Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects

Timeline of updates

1. monitoring2026-08-19 12:47 UTC

   We've identified an issue causing sign-in failures for signInWithIdToken (OIDC) logins on free-tier projects. Users authenticating with non-Google/Apple/Firebase OIDC providers may see failed login attempts. We've identified the root cause and fix has been rolled out. Impacted timeframe was 18th August 4pm UTC - 19th Aug 10:30am UTC

2. monitoring2026-08-19 12:48 UTC

   We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects.  Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts. We've identified the root cause and fix has been rolled out.

3. monitoring2026-08-19 13:01 UTC

   We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects. Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts. We've identified the root cause and fix has been rolled out. We are monitoring for continued stability.

4. resolved2026-08-19 15:56 UTC

   We have confirmed that the fix has been effective and are marking this incident as resolved.

Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab). Supabase profile · Recent Supabase incidents · Markdown · JSON