Supabase incident: SSO login failures in us-east-1

Affected components

• Auth

1. resolvedJul 28, 2026, 22:07 UTC

   The issue has been resolved. SSO login functionality in the us-east-1 region has returned to normal, and all services are operating as expected.

2. monitoringJul 28, 2026, 21:53 UTC

   We have rolled out a fix for the SSO login failures affecting the us-east-1 region. We are monitoring the results and will continue to observe the service to ensure stability before resolving the incident.

3. identifiedJul 28, 2026, 21:33 UTC

   We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made.

4. investigatingJul 28, 2026, 21:24 UTC

   We are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• RevenueCat: Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"Minor · Jul 27, 2026, 10:14 UTC

How often does Supabase have incidents?

Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history