Auth service UNHEALTHY — GoTrue down, 503 on all auth endpoints (paid plan, us-east-1)
authOur auth service has been down for nearly a day on project ref ftgsojwbvvqkqxjffrxi (Pro plan, us-east-1). REST and DB are healthy — only auth is affected. This is our Dev database and is preventing us from moving forward with any development or testing.
Symptoms:
/auth/v1/health returns 503: upstream connect error or disconnect/reset before headers... delayed connect error: 111
/v1/projects/{ref}/health via Management API confirms: auth: UNHEALTHY
All auth flows broken (OAuth, email/password)
Our Netlify deployment edge functions timeout because middleware can't reach GoTrue
What we've tried:
Restarted the project from dashboard
Patched auth config via Management API to trigger GoTrue restart — no effect
Verified all config is correct (Google OAuth, email auth all properly set)
What we need: Someone at Supabase to manually restart the GoTrue container for this project.
We have an open support ticket but haven't heard back yet. Has anyone experienced this or know a workaround? Any Supabase team members who can help escalate?
Symptoms:
/auth/v1/health returns 503: upstream connect error or disconnect/reset before headers... delayed connect error: 111
/v1/projects/{ref}/health via Management API confirms: auth: UNHEALTHY
All auth flows broken (OAuth, email/password)
Our Netlify deployment edge functions timeout because middleware can't reach GoTrue
What we've tried:
Restarted the project from dashboard
Patched auth config via Management API to trigger GoTrue restart — no effect
Verified all config is correct (Google OAuth, email auth all properly set)
What we need: Someone at Supabase to manually restart the GoTrue container for this project.
We have an open support ticket but haven't heard back yet. Has anyone experienced this or know a workaround? Any Supabase team members who can help escalate?
