Supabase incident

Login issues for SSO and Email accounts on Supabase Dashboard

Minor Resolved View vendor source →

Supabase experienced a minor incident on May 21, 2026 affecting Dashboard, lasting 2h 20m. The incident has been resolved; the full update timeline is below.

Started
May 21, 2026, 08:30 AM UTC
Resolved
May 21, 2026, 10:51 AM UTC
Duration
2h 20m
Detected by Pingoru
May 21, 2026, 08:30 AM UTC

Affected components

Dashboard

Update timeline

  1. investigating May 21, 2026, 08:30 AM UTC

    Users that are already logged in are not affected.

  2. investigating May 21, 2026, 08:33 AM UTC

    We are currently investigating an issue causing login failures for some users attempting to authenticate to the Supabase dashboard via SSO or email/password login flows. Affected users may see an error similar to: “captcha protection: request disallowed (sitekey-secret-mismatch)” Currently logged-in users are not affected, and GitHub authentication continues to operate normally. We will continue to provide updates as more information becomes available.

  3. identified May 21, 2026, 08:49 AM UTC

    We have identified the issue as being related to a recent key rotation and are currently working on a fix.

  4. identified May 21, 2026, 09:26 AM UTC

    A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.

  5. monitoring May 21, 2026, 09:43 AM UTC

    We have applied a fix and are seeing login services return to normal. We will continue to monitor authentication success rates over the next 60 minutes to ensure stability.

  6. resolved May 21, 2026, 10:51 AM UTC

    The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue.