Skip to main content
Supabase

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

Degraded Lasted 3h 9m · started · Supabase's page

Level
confirmed
Worst impact
Degraded
Down Index
20of 100

What to do

  • Check whether your product depends on Supabase. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3h 9m it lasted.

    Anything that failed between 2026-08-19 12:47 UTC and 2026-08-19 15:56 UTC may need a replay.
  • Subscribe to Supabase's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=supabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Supabase 4

  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

    provider

  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.

    provider

  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.

    provider

  4. resolved

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-4f8e5a2d22

Is Supabase still down?

No, this incident was resolved 2026-08-19 15:56 UTC. For Supabase's live state, see https://down.guide/supabase.

How long did it last?

3h 9m, from 2026-08-19 12:47 UTC to 2026-08-19 15:56 UTC, by the times Supabase posted.

What caused it?

Supabase hasn't published a root cause. If it does, it shows here.

Where does this come from?

Supabase's official status page, https://status.supabase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.