Shared Pooler (Supavisor) connections graph is empty (always showing 0)

Hi,

We are serving a SvelteKit app on Netlify Functions that's (just recently) using Prisma ORM, and connecting to Supabase via the

Transaction Pooler Connection string – postgresql://postgres.[your-project-ref]:password@aws-0-[region].pooler.supabase.com:6543/postgres

Transaction Pooler Connection string – postgresql://postgres.[your-project-ref]:password@aws-0-[region].pooler.supabase.com:6543/postgres

Transaction Pooler Connection string – postgresql://postgres.[your-project-ref]:password@aws-0-[region].pooler.supabase.com:6543/postgres

Transaction Pooler Connection string – postgresql://postgres.[your-project-ref]:password@aws-0-[region].pooler.supabase.com:6543/postgres

As described here: https://www.prisma.io/docs/orm/overview/databases/supabase

Our app is live in prod and running, but the Database Reports page graphs look like this (view attached screenshot)

We've had a couple of

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)

errors happen in prod and are currently trying to debug, and those empty graphs are puzzling. Why would the Shared Pooler (Supavisor) chart show nothing?

IIsitfato Hi, We are serving a SvelteKit app on Netlify Functions that's (just recently) ...

ibrahim•9/26/25, 6:05 AM

I'm wondering if maybe you are using the correct uri for the shared pooler? I would have imagine that you are using the dedicated pooler hence why you have one client connection for that as apposed to the shared pooler which uses

DIRECT_URL="postgresql://postgres.[project-ref]:[YOUR-PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:5432/postgres"

DIRECT_URL="postgresql://postgres.[project-ref]:[YOUR-PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:5432/postgres"

ibrahim•9/26/25, 6:07 AM

Note that supabase mentions Dedicated Pooler is not IPv4 compatibleDedicated Pooler is not IPv4 compatible which may be causing issues for you related to timeouts

IsitfatoOP•9/26/25, 6:27 AM

We were using the Dedicated pooler connection string, and then switched (because of confusing/outdated docs) to the Session pooler (Shared Pooler) connection string, with port 65436543 instead of 54325432

IsitfatoOP•9/26/25, 6:28 AM

We are now reverting back to the Dedicated pooler, though we had some downtime and it just sucks to have no graph to look at to see when we actually bust the limit

IsitfatoOP•9/26/25, 6:28 AM

There are logs in the Shared PoolerShared Pooler log section

inder•9/26/25, 6:33 AM

For standard queries use transaction pooler: connection string with port 6543
For running migrations, either use session pooler connection string or the direct connection string.

IIsitfato We are now reverting back to the Dedicated pooler, though we had some downtime a...

ibrahim•9/26/25, 6:34 AM

perhaps this might be something to leave in feedback in the top right of the dashboard

Shared Pooler (Supavisor) connections graph is empty (always showing 0)

Similar Threads

Similar Threads

Similar Threads