Neon Connection Timeout After Scale to Zero (Cold Start)

How to fix it

Try these in order — the most common fix is first.

1. 1. Raise the client connection timeout

   Copy steps
   1. Node.js pg: set connectionTimeoutMillis: 10000
   2. Python psycopg2: connect_timeout=10
   3. Prisma: append connect_timeout=15&pool_timeout=15 to the connection string
   Did this fix it? Yes No

2. 2. Retry with exponential backoff

   Copy steps
   1. Wrap the first connection in a retry (Neon docs example: 5 retries, 4 second minimum timeout, randomized jitter)
   2. Retry fast for brief blips, then back off
   Did this fix it? Yes No

3. 3. Keep the compute awake on a paid plan

   Copy steps
   1. Open the project in the Neon Console, then Branches, select the compute and Edit
   2. Turn off scale to zero, or extend the suspend timeout (Scale plan: 1 minute up to 7 days)
   3. If scale to zero is disabled, restart the compute about weekly to pick up compute image updates
   Did this fix it? Yes No

4. 4. Cut connection setup time

   Copy steps
   1. With a PostgreSQL 17 client add sslnegotiation=direct to the connection string
   2. Place your app in the same region as the Neon project
   Did this fix it? Yes No

Symptoms

First query after a quiet period hangs or fails with 'Couldn't connect to compute node', Prisma P1001 'Can't reach database server', or a client timeout. Later queries are fast.

Why it happens

• Compute auto-suspends after 5 minutes idle (not changeable on the Free plan) and takes a few hundred milliseconds or more to wake
• Client connect timeout shorter than the wake-up time (Prisma gives up early)
• Network distance between app region and Neon region adds latency

This guide also covers

• neon connection timeout
• neon cold start
• neon can't reach database server
• neon scale to zero slow first query

The same problem in other apps

All not loading, error messages & connection guides →

• Supabase Max Client Connections Reached (Supabase)
• PlanetScale Prisma Connection Errors (PlanetScale)
• Railway SSL Certificate Stuck or Not Working (526, 525, Too Many Redirects) (Railway)

Other Neon errors

• Neon "Remaining Connection Slots Are Reserved" (Too Many Connections)
• Neon Compute Time Quota Exceeded (Free Plan Limit Reached)
• Neon Free Plan Storage Limit Reached (Writes Blocked)
• Neon Cannot Create Branch: Branch Limit Reached
• Neon Prisma or Drizzle Migration Fails (Pooled Connection)
• Neon SSL Required Error (Connection Is Insecure)
• Neon "The Endpoint ID Is Not Specified" / Password Authentication Failed
• Neon "Active Endpoints Limit Exceeded" / Compute Suspended