Intermittent 502 Bad Gateway from Supabase Auth /auth/v1/token

We are seeing repeated 502 Bad Gateway responses from Supabase Auth during password login. Endpoint: https://<project-ref>.supabase.co/auth/v1/token?grant_type=password Observed behavior: Login intermittently fails with HTTP 502 Same issue occurs on multiple clients/networks We also observed generic Failed to fetch / Network request failed Supabase Database Editor has also been intermittently unavailable Example response headers include: server: cloudflare sb-gateway-version: 2 sb-request-id: 01a085c8-680e-7c5e-8168-a1d93ac784b1 cf-ray: a3859eaccd591479-VIE timestamp: Wed, 09 Sep 2026 10:48:18 GMT The response is coming directly from the Supabase Auth endpoint, not from our application server. The Supabase status page currently reports API Gateway degradation, but Auth itself appears operational. In practice, authentication is unavailable during these 502 responses. Please confirm whether this is related to the current API Gateway incident and whether there is an ETA for mitigation.