Problems with ap-south-1 pooler connections

I'm having a 2 prod DB on supabase. Recen;t my servers are getting these errors at random.

Can't reach database server at aws-0-ap-south-1.pooler.supabase.com:5432

Can't reach database server at aws-0-ap-south-1.pooler.supabase.com:5432

Can't reach database server at aws-0-ap-south-1.pooler.supabase.com:5432

Can't reach database server at aws-0-ap-south-1.pooler.supabase.com:5432

Connection Error: Connection ended unexpectedly

Connection Error: Connection ended unexpectedly

Connection Error: Connection ended unexpectedly

Connection Error: Connection ended unexpectedly

Connection terminated unexpectedly

Connection terminated unexpectedly

Connection terminated unexpectedly

Connection terminated unexpectedly

are there any known issues with pooler connection? or my code is wrong?
Please help me figure this out, I'm loosing a lot of signups

garyaustin•7/23/25, 7:56 PM

No reports here or status page.
If you are Pro you should consider using the PGbouncer built in to your instance.
Contact support for now.

Did both start having issues at same time?

Isaac•7/23/25, 8:08 PM

I am also having the same issue over here. It started 1 hour ago

garyaustin•7/23/25, 8:09 PM

Same region and supavisor port?

Isaac•7/23/25, 8:13 PM

we are us-west-1 region and port 6543

garyaustin•7/23/25, 8:14 PM

So may or may not be related.

v0idpwn•7/23/25, 8:53 PM

I'm from the pooler team. Right now we don't see anything atypical. I encourage you to contact support.

Ggaryaustin No reports here or status page. If you are Pro you should consider using the PGb...

cxOP•7/24/25, 5:34 AM

Isn't pgBouncer deprecated?

cxOP•7/24/25, 5:35 AM

tho I am using supavisor
I use a session pooler url (the 5432 port)

Ccx Isn't pgBouncer deprecated?

silentworks•7/24/25, 10:03 AM

No, it's used for dedicated poolers which you get on a pro plan.

cxOP•7/24/25, 10:03 AM

ahh okay

cxOP•7/24/25, 10:04 AM

i'm on the free plan

garyaustin•7/24/25, 12:24 PM

Ahh, I assumed you would be Pro if in Production at least for backups and support.

cxOP•7/24/25, 4:08 PM

im ready to move to Pro it that fixes my issues

cxOP•7/24/25, 4:09 PM

im just trying to delay paying for Pro....

cxOP•7/24/25, 4:09 PM

hustlex_medusa_server-1  | http: POST /auth/customer/emailpass | (401) - 60 ms 
hustlex_medusa_server-1  | Connection Error: Connection ended unexpectedly

hustlex_medusa_server-1  | http: POST /auth/customer/emailpass | (401) - 60 ms 
hustlex_medusa_server-1  | Connection Error: Connection ended unexpectedly

cxOP•7/24/25, 4:10 PM

these are the logs from my server

garyaustin•7/24/25, 4:34 PM

That error could be lots of things. Check your logs for postgres timeout errors.

Your first messages had can't reach server which seems more in line with a network or supavisor issue. But with the dev coming in and saying no known issues with that supavisor port then it could be something more specific to your project. If your logs don't show anything then support would be the only way if this is ongoing.

The dedicated pooler isolates you from supavisor getting overloaded which has happened with the large growth in AI instances sometimes overwhelming things.

Problems with ap-south-1 pooler connections

Similar Threads

Similar Threads

Similar Threads