Shared Pooler Connection Issues
We've been seeing inconsistent DB latency issues in our app since about 8am EST yesterday morning.
Some queries are taking way longer than expected but our DB Health looks fine when viewing our Supabase Grafana Dashboard.
My hunch is that this is another issue with the shared Pooler we're using since we're using vercel which only supports IPv4 Connections.
The issue is manifesting in almost the exact same way as this issue that I reported 2 months ago:
help-and-questionsSupabase Shared Connection Pooler Issues
Interestingly, the exact same instance_id that was causing the issues last time i-0f130f02967960cb6 is the same instance that our Shared Pooler Logs are reporting being problematic this time.
We've already opened up a support ticket with Supabase but haven't heard back yet.
Is anyone else experiencing similar issues?
Some queries are taking way longer than expected but our DB Health looks fine when viewing our Supabase Grafana Dashboard.
My hunch is that this is another issue with the shared Pooler we're using since we're using vercel which only supports IPv4 Connections.
The issue is manifesting in almost the exact same way as this issue that I reported 2 months ago:
help-and-questionsSupabase Shared Connection Pooler Issues
Interestingly, the exact same instance_id that was causing the issues last time i-0f130f02967960cb6 is the same instance that our Shared Pooler Logs are reporting being problematic this time.
We've already opened up a support ticket with Supabase but haven't heard back yet.
Is anyone else experiencing similar issues?
