401 JWT rejections on new project — authenticated requests failing (findseeazzmsdzpxobgt)

[lelekovigilante]

Our production app became unusable today. I believe we're affected by the
open incident "401 errors due to JWT rejections" (status page, open
since Aug 14, 2026), which describes a subset of new projects failing
on some JWT renewals. The status page currently also shows
API Gateway: Degraded Performance.

Project ref: findseeazzmsdzpxobgt
Project created: ~Aug 15, 2026 (new project — matches the affected group)
Plan: Free
Stack: Next.js on Vercel, @supabase/ssr + @supabase/supabase-js
App: https://riscomais.com.br

Symptom

Users sign in successfully — the auth endpoint responds normally — but
every authenticated page then hangs and never finishes loading. The
browser ends up bouncing between /login and the destination page.

Reproduced on desktop, on mobile, and in a clean incognito window, so it
is not client-side cache.

What I verified on our side

• Requests using the secret / service_role key work normally (HTTP 200)
• Requests carrying a user JWT fail
• Database is healthy: 23 of 60 connections in use, no queries running
  longer than 3s, small tables (~9k rows in the largest)
• SELECT grants for the authenticated role are present on all 38
  public tables
• Auth health endpoint responds in ~200ms
• No application errors in our server logs — requests simply never complete

Question

A support ticket is already filed. Is there anything I can do on my side
while the fix rolls out — rotating keys, forcing new sessions, migrating
to the new publishable key — or does the fix have to be applied to the
project by your team?

Also: is anyone else seeing this today? I noticed a couple of recent
posts here about unreachable projects that may be related.

Thanks.

[GaryAustin1]

Unreachable would not be related to the JWT issue.

Only support could say if they can fix it individually or waiting for the fix is required.