Is Neon Database Down Right Now?
Neon is a serverless Postgres platform with branching and auto-scaling. Slow responses often indicate cold starts, not true outages.
Updated May 2026
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
How to Check If Neon Is Down Right Now
- 1. Visit neonstatus.com — official status page with regional breakdown
- 2. Check @neondatabase on X for real-time incident announcements
- 3. In Neon console at console.neon.tech — check if your compute shows "Running" or "Idle"
- 4. Run
psql "$DATABASE_URL" -c "SELECT 1;"to test connectivity directly
🧊 Cold Starts: The #1 Neon "Outage" That Isn't
Most reports of Neon being "down" are actually cold starts. When Neon's compute (the Postgres engine) has been idle for 5+ minutes, the next request triggers a 100-500ms wake-up delay. This can cause connection timeouts if your application's timeout is set too low.
Fix Cold Start Timeouts
- • Set connection timeout to at least 10 seconds (not 3s which often fails on cold starts)
- • Add retry logic: 3 retries with 500ms initial delay
- • Enable connection pooling via the Neon pooled connection URL
- • Increase autosuspend delay or disable it on paid plans
- • Use a "warming" cron job to ping the database every 4 minutes
Common Neon Error Messages
error: connection timeout expired
Cause: Cold start (compute waking up) or true connectivity issue
Fix: Increase timeout to 10s+ and add retry logic
connection refused: server closed connection unexpectedly
Cause: Compute was suspended mid-connection or SSL handshake failed
Fix: Reconnect — Neon requires SSL (sslmode=require)
too many connections
Cause: Exceeded Postgres connection limit (Neon free: 100 connections)
Fix: Enable Neon connection pooler (PgBouncer) for serverless apps
remaining connection slots are reserved
Cause: All Postgres connections in use — serverless functions leak connections
Fix: Use pooled connection URL from Neon dashboard + connection pooling in ORM
SSL SYSCALL error: EOF detected
Cause: Network interruption or Neon compute restart
Fix: Implement connection retry; Neon computes restart occasionally for maintenance
Monitor your Neon database health externally
Better Stack alerts you when your Neon-backed API goes down — catching issues the status page might miss for your specific region.
Try Better Stack Free →Neon Branches: When They Help During Outages
Neon's branching feature (create instant copies of your database from any point in time) is a powerful recovery tool. If your primary branch is experiencing issues, you can:
- ✓Create a branch from 1 hour ago and compare — useful for diagnosing data corruption from a bad migration
- ✓Switch your app to a different branch connection string as a failover (same region, separate compute)
- ✓Test schema migrations on a branch before applying to production
- ⚠Branches don't protect against regional outages — they run in the same region as your primary database
Troubleshooting Neon Connection Issues
Use the pooled connection URL for serverless
In the Neon dashboard, go to your project → Connection Details → toggle to "Pooled connection". This PgBouncer URL handles connection pooling automatically, preventing the "too many connections" error common in serverless environments where each function invocation opens a new connection.
Enable SSL explicitly
Neon requires SSL. Add ?sslmode=require to your connection string if you see SSL errors. For Node.js with pg: ssl: { rejectUnauthorized: true } in your connection config.
Check compute region matches your app region
Neon compute runs in one of four AWS regions. If your app runs in eu-west-1 (Ireland) but your Neon database is in us-east-1, every query adds 80-100ms of latency. Create databases in the same region as your app's primary deployment.
Monitor with external health checks
Build a /api/health endpoint in your app that runs SELECT 1 against Neon. Then use Better Stack or APIStatusCheck to hit that endpoint every 30 seconds — you'll catch outages independently of Neon's status page.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Neon Database goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Neon Database + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
Related Developer Guides
Frequently Asked Questions
Is Neon database down right now?
To check if Neon database is down, visit the official Neon status page at neonstatus.com. Neon also posts incident updates on their Twitter/X @neondatabase. For third-party monitoring, APIStatusCheck.com tracks Neon availability independently. Neon incidents are often regional — affecting specific AWS regions (us-east-1, us-east-2, eu-central-1, ap-southeast-1) rather than all databases globally.
Why is my Neon database connection slow or timing out?
Slow Neon connections are usually caused by cold starts, not outages. Neon suspends compute (the Postgres engine) after 5 minutes of inactivity on free plan (300 seconds configurable on paid plans). When your app makes the next query, Neon wakes the compute — this takes 100-500ms on average. Solutions: (1) Use Neon connection pooling (PgBouncer) via pool_mode=transaction, (2) Increase the autosuspend delay on paid plans, (3) Disable autosuspend entirely for latency-critical applications, (4) Implement connection retries in your ORM (Drizzle, Prisma both support this).
How do I use Neon with Vercel Edge Functions?
Use the @neondatabase/serverless package (not pg) for Vercel Edge Functions and Cloudflare Workers — it connects via HTTP/WebSockets instead of raw TCP, which Edge runtimes require. Install with: npm install @neondatabase/serverless. Import neon from @neondatabase/serverless and use it as a tagged template literal for queries. Set your DATABASE_URL environment variable in Vercel settings. For connection pooling in serverless, enable the Neon pooler (add ?pgbouncer=true to your connection string or use the pooled connection URL from Neon dashboard).
What is the Neon free plan database limit?
Neon free plan limits (as of 2026): 0.5 GB storage, 190 compute hours/month (roughly 6 hours/day of active compute), 1 project, unlimited databases per project, 5 minutes autosuspend (compute pauses after 5 min inactivity). Paid plans (Launch at $19/mo) offer 10 GB storage, 300 compute hours, configurable autosuspend (up to no autosuspend), and multiple projects. The 190 compute hours limit is the most common bottleneck for free tier users with active applications.
How is Neon different from Supabase and PlanetScale?
Neon is a serverless Postgres platform focused on developer experience and branching — it lets you create instant database branches (for feature dev, CI/CD, and testing) from any point in time. Supabase is a broader BaaS platform (Auth, Storage, Realtime, Edge Functions) built on Postgres. PlanetScale is MySQL-based with a schema change workflow focused on large-scale databases. If you want pure serverless Postgres with branching and a generous free tier, Neon is the strongest option. If you need a full backend platform, Supabase is better.