is aws-1-us-east-2 pooler healthy?
we're a platform that builds for supabase dbs.
I know us-east-1 had a massive outage yesterday.
but we're observing timeouts when trying to talk to dbs that are on aws-1-us-east-2 via the pooler. is this pooler having issues atm? not seeing any mention of it on status.supabase.com and it hasn't gotten better since yesterday.
other regions don't seem to have this issue
7 Replies
They had to fix a couple of us-east-1 supavisor instances this morning. 6 to 8 reports of user issues here and github. Seen nothing on us-east-2.
File a support ticket. The other issue did not make status either as it was not known to be an issue to SB yet and they fixed it immediately.
okay thanks, will do
Are you Pro?
If so considering using the pgbouncer pooler and direct session port if possible.
we are using the transaction pooler. port 6543
or i should say, our end users (who all are supabase db users) are all using the transaction pooler. 6543 and we are trying to connect that way
Your link you show is to Supavisor pooling port, which works with IPv4 and is only option on FREE for pooling 6543. Pro users have another option with a built in pooler on the direct port (.co instead of .com) for doing pooling of 6543. That pooler is dedicated to your instance.
Oh I see thanks. Wasn’t aware of the dedicated pooler for pro.
I think many of our users are on the free tier so not sure we have that option.
You don't if they are Free.