Lost access to existing project (ref: cyyhtlorqubjsfexzlkf) after JWT/401 incident — project confirmed alive via REST API, just no dashboard access

[entrelacospsiedu]

Hi community
I have a project in active use (with real students using it) that I can no longer see in
the dashboard. Project reference: cyyhtlorqubjsfexzlkf
Navigating directly to https://supabase.com/dashboard/project/cyyhtlorqubjsfexzlkf returns
"You do not have access to this project" — which tells me the project still exists, my
account/session just isn't recognized as a member of the organization that owns it anymore.
I confirmed the project itself is fully alive and unaffected: querying its REST API directly
(GET {project_url}/rest/v1/areas with the public anon key) returns a valid 200 response from
PostgREST, proving the schema and tables are intact. This is purely an access/identity issue,
not data loss.
This started around the time of the JWT/401 authentication incident reported on your status
page (began Aug 14, 02:23 UTC, "newly refreshed JWT tokens being rejected"). I log in via
GitHub. When I tried logging in again after the related GitHub incident was resolved, Supabase
prompted me to create a brand new organization from scratch, as if I had no prior organization
membership at all — I did, and it's empty, unrelated to my real project.
I'm on the Free plan, so I don't have access to a support ticket. I don't have a second
account/colleague with access to the original organization either. Is there anything the
community or a staff member reading this can help verify — specifically, whether my GitHub
identity's org membership got dropped during the JWT incident, and whether it can be restored?
Project ref: cyyhtlorqubjsfexzlkf
Login method: GitHub
Thanks in advance.

[GaryAustin1]

Not sure this is related to the JWT incident versus your Github email has changed (primary must match one in dashboard) or you logged in with email/password. Check your emails in past and confirm your Github primary matches. If not a new account was created.

Try another browser. Try chatGPT account login with the same email the account uses (which may not be your Github primary).

Otherwise support@supabase.com . You will not get help finding the correct email thru Github or Discord from staff.

[anatbil]

This sounds much more like an organization/membership issue than a project or database issue. The fact that the REST API is still responding normally is a pretty strong indication that the project itself and its data are intact.

Given the timing, I’d also be looking at the GitHub OAuth identity and the Supabase organization membership record rather than trying to recreate anything. If the original org still exists and the project is still attached to it, there may be a way for Supabase to restore the membership without affecting the project.

I’ve dealt with similar Supabase access/auth issues before, and I’d be happy to help investigate from the technical side if someone from the Supabase team can confirm what happened to the original membership for this project ref.