© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
Connection limit being reached too soon - Neon
N
Neon
•
16mo ago
•
8 replies
dry-scarlet
Connection limit being reached too soon
I
'm having issues with connection limit
.
I
'm using 0
.25 CU and Paid Plan
. The
SHOW max_connections;
SHOW max_connections;
returns 112
.
I
'm using pgbouncer
, 3 services
, each service has its own username
.
Sometimes I get these connections spikes of 55 connections
(picture
)
, and when this happens
, no service can create more connections
.
I don
't get it
. The connection limit should be 112
, not 55
.
Also
, the connection limit for a misbehaving service should be 64
, preventing it from exhausting connections for others
.
During these high
-connections times the neon UI cannot connect to Postgres
, so I cannot run
select * from pg_stat_activity
select * from pg_stat_activity
to debug it or so
.
.
.
Neon
Join
The official Neon Database Discord
10,545
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Similar Threads
Was this page helpful?
Yes
No
Recent Announcements
Similar Threads
Limit reached
N
Neon / ❓|questions-and-answers
15mo ago
Compute Hours Limit Reached
N
Neon / ❓|questions-and-answers
11mo ago
Local testing - compute limit nearly reached
N
Neon / ❓|questions-and-answers
2y ago
Connection Pooling limit question
N
Neon / ❓|questions-and-answers
2y ago