Skip to content

Incident detail

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

Resolved incidentMinor

Timeline window

to

Get alerted the next time Supabase breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Monitoring

    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

    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

    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

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

Keep exploring

More from Supabase

Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.