Quick answer
Neon documents pooled concurrent clients as Up to 10,000. Pooler clients are not the same as backend PostgreSQL sessions.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| pooled concurrent clientsPooler clients are not the same as backend PostgreSQL sessions. | Up to 10,000 | Neon connection pooler | NeonAug 22, 2026 |
Why does this limit matter?
A transaction pooler can absorb many client sockets while keeping backend connections bounded.
This value is scoped to Neon connection pooler; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm the pooled connection string and audit application assumptions about session state.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Session-dependent PostgreSQL features can be incompatible with transaction pooling.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related