I am unable to run any queries in the SQL Editor, including SELECT 1;. I get 'Connection terminated due to connection timeout'. I have already restarted and paused/resumed the project. The supabase dashboard shows Database errors at 35.2%, but CPU and Memory are normal. I believe the connection pooler is completely unresponsive.
Are you running query in Supabase database? have you tried contacting their support?
Hi jim,
If SELECT 1; is timing out in the Supabase SQL Editor, I’d treat this as a Supabase database/project health issue first, not a Vercel deployment issue.
CPU and memory being normal is useful, but it does not completely rule out database-side problems like connection saturation, lock waits, disk I/O pressure, or the pooler path being unhealthy.
I’d try to separate the direct database connection from the pooler/dashboard path:
psql "DIRECT_CONNECTION_STRING" -c "select 1;"psql "POOLER_CONNECTION_STRING" -c "select 1;"
Don’t post either connection string publicly.
If the direct connection works but the pooler or SQL Editor fails, that points more toward the pooler/dashboard connection path. If both direct and pooler connections fail on select 1, then the database itself is likely unhealthy or overloaded even if the headline CPU/RAM numbers look fine.
I’d also check Database Reports for active connections, long-running queries, lock waits, disk I/O, and error logs around the timeout window. If restart or pause/resume only helps briefly, that usually suggests there is still an underlying query/connection issue to fix rather than a one-time dashboard glitch.
The most useful non-sensitive detail to share would be whether direct psql succeeds, whether the pooler connection succeeds, and the exact redacted error from each path.