Supabase incident

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

Minor Resolved View vendor source →

Supabase experienced a minor incident on August 19, 2026, lasting 3h 9m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2026, 12:47 PM UTC
Resolved
Aug 19, 2026, 03:56 PM UTC
Duration
3h 9m
Detected by Pingoru
Aug 19, 2026, 12:47 PM UTC

Update timeline

  1. monitoring Aug 19, 2026, 12:47 PM 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. monitoring Aug 19, 2026, 12:48 PM 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. monitoring Aug 19, 2026, 01:01 PM 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. resolved Aug 19, 2026, 03:56 PM UTC

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