Ctrl+Z Therapy
CasesQuick answersGuides10-minute checklistHow we testCartoonSend it in

Neon database slow on the first request? It scales to zero after 5 minutes

Ship ItChecked against the official source

Source checked 10 Oct 2026 · Published 23 Oct 2026 · Last reviewed 23 Oct 2026 · By Ctrl+Z Therapy (how we test)

The short answer

If your Postgres database is on Neon, a slow first request after a quiet period can mean it was asleep. Neon's docs say that when your database is inactive, it automatically scales to zero after 5 minutes, and the next query reactivates it automatically within a few hundred milliseconds (Neon calls this a cold start). For Neon Free plan users this setting is fixed; paid plan users can disable scale to zero for an always-active compute.

What to do

  1. Put your app and your database in the same region.
  2. Configure a longer connection timeout, so your app has time to accommodate cold starts.
  3. Need the database always on? On a paid plan, you can disable scale to zero.
  4. Ask your AI tool: "This app uses Neon. Check that the app and database are in the same region and set a longer database connection timeout so the first request after idle doesn't fail."

Good to know

  • The wake-up itself takes a few hundred milliseconds. A longer first load can have other causes too.
  • Separate from this: on the Free plan, if you run out of compute hours, your compute is suspended until the next billing period or until you upgrade. Neon says none of these limits delete your data.

Source

Checked on 10 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.

Related