Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects
Aug 19, 12:47 UTCAug 19, 15:56 UTC
Duration
3h 9m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
We have confirmed that the fix has been effective and are marking this incident as resolved.
Timeline
- Resolved · Aug 19, 15:56 UTC
We have confirmed that the fix has been effective and are marking this incident as resolved.
- Monitoring · Aug 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.
- Monitoring · Aug 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.
- Monitoring · Aug 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
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m