Hello, since May 13 2026, we notice we get a few ConnectTimeoutError: Connect Timeout Error when calling supabase.auth.admin.getUserById(...) and supabase.auth.getUser(...). But today (May 25) it happens more often.
Our project is live since multiple months, we didn't change anything recently, traffic is the same. Why is it happenning suddenly? Is it related to this status update: https://status.supabase.com/incidents/gn3hypz38flc ? Or is it something that we can improve/fix on our side?
Thank you, Maureen
Maureen is experiencing frequent 'ConnectTimeoutError' issues when using 'supabase.auth.admin.getUserById' and 'supabase.auth.getUser'. The issue started on May 13, 2026, and has become more frequent by May 25. Maureen is questioning if this is related to a recent status update or if there is something they can fix on their side.
That status does seem to suggest a resolution. What do your auth logs say, any more details? What tech stack are you using, is your client side application in the same region as your Supabase instance server?
How are you creating supabase clients also?
Also check your usage charts, database reports (observability) and Gateway API reports to see if usage or queries are going up over time.