read timeout
I'm experiencing Supabase read timeouts in my Spring application using JDBC connections. The server has been running smoothly since last year without any connectivity issues. Has anyone else encountered this same problem recently?
6 Replies
The connection string is like this,
jdbc:postgresql://aws-0-ap-northeast-2.pooler.supabase.com:5432/postgres?user=XXX&password=XXXX
I curious it is ap-northeast-2 issue
me too
Same region?
Yes. i'm using prisma orm
Can't reach database server at aws-0-ap-northeast-2.pooler.supabase.com:6543Resolved
Connection is established now
If you are Pro you should consider using your dedicated pgbouncer instead of Supavisor.