Is Neon down?
No, Neon is not down.
Neon’s status page reports no incidents, console.neon.tech responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsneonstatus.com
- Reachable6 of 6 regionsNeon API · console.neon.tech
- Reports in the last hour0Normal
Neon’s status page
From neonstatus.com. Read at
- Database ConnectivityOperational
- Project/Branch OperationsOperational
- Console APIOperational
- Console FrontendOperational
- Account CreationOperational
- Console LoginOperational
- WebsiteOperational
- Object StorageOperational
Show all 12 components
- FunctionsOperational
- AI GatewayOperational
- Managed Better AuthOperational
- Data APIOperational
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 299 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (console.neon.tech)
By region
| Region | Neon API console.neon.tech |
|---|---|
| N. Virginia us-east-1 | 401 · 42 ms |
| Oregon us-west-2 | 401 · 206 ms |
| Frankfurt eu-central-1 | 401 · 129 ms |
| Singapore ap-southeast-1 | 401 · 663 ms |
| Tokyo ap-northeast-1 | 401 · 438 ms |
| São Paulo sa-east-1 | 401 · 452 ms |
Two regions check Neon every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Neon ourselves since Oct 28, 2026. Earlier days come from its status page.
0 days with problems in the last 90 days.
Recent incidents
Incidents: 0 in the last 30 days and 0 in the last 90.
No incidents recorded.
If Neon isn’t working for you
Neon is a serverless Postgres service, owned by Databricks, that separates storage and compute and supports branching and scale to zero.
Common Neon errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Couldn't connect to compute node | Neon's proxy could not connect to your compute, sometimes during repeated attempts while it restarts after being idle. | An outage | Check neonstatus.com, then retry with a short delay. Source |
terminating connection due to administrator command | The connection sat idle long enough for the compute to suspend (after 5 minutes of inactivity by default). | Your side | Reconnect before querying, or disable scale to zero on a paid plan. Source |
remaining connection slots are reserved for roles with the SUPERUSER attribute | The database reached its max_connections limit. | Your side | Close idle connections or use the pooled connection string. Source |
You have exceeded the limit of concurrently active endpoints | Your project has more active computes than its limit, so extra computes stay suspended. | Your side | Suspend unused computes or raise the limit. Source |
Is it just you?
- Check neonstatus.com for your region.
- A first query after idle can be slow while the compute wakes up; that is scale to zero, not an outage.
- Use the pooled connection string to avoid running out of connections.
- Try connecting with psql from another network to rule out your app or firewall.
Alternatives to Neon
Questions
Common causes are a compute waking from scale to zero, too many connections, an active-compute limit, or an incident. Neon's connection errors page explains each message.
Neon posts incidents per region at neonstatus.com. This page shows that alongside our own reachability checks.
Sources: neon.com, neonstatus.com
Get alerted when Neon breaks your app.
If your product or your team depends on Neon, its outage is your outage, and your users will blame you, not Neon. Point a Site Qwality monitor at the Neon endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.