Supabase incident
Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects
Resolved after 3 h 9 min.
- Started
- Ended
- Worst state
- Degraded
- On Supabase’s status page
- Source
Timeline
- Supabase status page · Reported Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects
- Supabase status page · 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
- Supabase status page · 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.
- Supabase status page · 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.
- Supabase status page · Resolved We have confirmed that the fix has been effective and are marking this incident as resolved.
Cite this incident
Site Qwality, “Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects,” Aug 19, 2026, https://siteqwality.com/is-supabase-down/incidents/supabase-202608191247/
Free to quote with a link to this page.