**CRITICAL: Supabase Auth Service Down**
Issue: Complete Auth service failure
- ❌ Users cannot log in ("Database error granting user")
- ❌ User creation failing
- ❌ User updates failing
- ❌ Session creation failing
Impact: Application completely unusable - 100% of users affected
Status:
- ✅ Database reads working
- ❌ All Auth writes failing
- ❌ Login completely broken
Did someone faced something similar? Could help me anyone?
14 Replies
Have you checked the Auth and Postgres logs for database error?
How is the status of your subsystems on the main project page upper right?
There is no outage as there are no other reports of auth problems.
Database error is usually your trigger function failing or an auth webhook you added not working.
Did you make a change before the errors started?
yes, but not in this part application.
in supabase UI
Failed to invite user: Failed to make POST request to "https://nsyfksvtkjmyhvdmxqsi.supabase.co/auth/v1/invite". Check your project's Auth logs for more information. Error message: Database error updating user
---
Postgress
"relation "profiles" does not exist" - but the table exists according the documentation
Auth:
"event_message": "{"component":"api","error":"ERROR: relation \"profiles\" does not exist (SQLSTATE 42P01)","level":"error","method":"POST","msg":"500: Database error updating user","path":"/invite","referer":"...","remote_addr":"34.244.40.143","request_id":"97fb08287632bdca-DUB","time":"2025-09-15T20:56:38Z"}",
Do you have an auth.users trigger function?
And what do you mean it exists according to documentation? You should be able to see in the table UI.
Normally you don't use statement triggers. Is there some case for that?
I'm seeing the table. According this documentation https://supabase.com/docs/guides/auth/managing-user-data#advanced-techniques
User Management | Supabase Docs
View, delete, and export user information.
You have 3 functions that will run for each new user and some multiple times (updates).
That doc is optional. So you would have had to create the table.
But you have 3 triggers one is likely calling profile without using public.profile for your first error.
The statement trigger is a bit scary as there will be no NEW variable in the function for that.
but this trigger was not created by me. At least I do not remember that I would created something like this
Had to be you or your AI if you are using one.
Supabase does not have any triggers by default. Same as it does not have the profile table by default.
Default instance. And there are no extensions that add triggers there.
hmm, interesting. That was really root of my issue.
Did you mean to add a trigger to some other table?
Or was the Statement part the issue?
I removed the statement trigger and it unblock my issue with login
or sending invitations
thank you
After update will be called on almost all auth operations except refresh token.