---
number: 22457
slug: 22457-increased-supavisor-client-connection-limits-across-paid-plans
published: 2024-04-04
discussion: https://github.com/orgs/supabase/discussions/22457
labels:
  - infra
page: https://supabase.com/changelog/22457-increased-supavisor-client-connection-limits-across-paid-plans
---

# Increased Supavisor Client Connection Limits Across Paid Plans

Supavisor, Supabase's multi-tenant connection pooler deployed to regional clusters, became production ready back in December 2023. You can read the announcement [here](https://supabase.com/blog/supavisor-postgres-connection-pooler).

Since then, we've migrated Supabase projects from PgBouncer, single tenant connection pooler deployed to the project's instance, to Supavisor.

However, we kept the previous client connection limits from PgBouncer during the transition across all compute instances.

Today, we're happy to announce that we've increased this limit for compute instances `Small`, `Medium`, `Large`, and `XL` so your projects can take advantage of additional client connections while pricing remains unchanged. These new limits have already been applied to all existing projects and any new projects spun up.

Here's a quick breakdown:

| Compute Size | Previous Client Limits | New Client Limits |
| -------------- | ---------------------  | ----------------- |
| Small                | 200                               | 400                       |
| Medium           |  200                               |  600                      |
| Large               |  300                               |  800                      |
| XL                    |  700                               | 1,000                     |

For a more complete breakdown of your compute instance resources head over to the [Compute Add-ons](https://supabase.com/docs/guides/platform/compute-add-ons) page.