Databases & data infrastructure
Is Neon down?
Live Neon status, measured independently. We probe 5 Neon endpoints from monitoring regions on every continent and record every outage we detect.
Neon is up
Our probes are reaching Neon normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website99.99% uptime, 30 days5 regions, 86 to 166 msCheckingp50116 msMedian responsep95254 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- Console API99.96% uptime, 30 days6 regions, 101 to 571 msCheckingp50325 msMedian responsep95530 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Console99.83% uptime, 30 days6 regions, 374 to 1852 msCheckingp501118 msMedian responsep951528 msSlowest 5% of checks2000 ms1000024 h ago12 h agonow
- Documentation99.98% uptime, 30 days5 regions, 140 to 292 msCheckingp50194 msMedian responsep95324 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Console DNS100% uptime, 30 days6 regions, 0 to 0 msCheckingp500 msMedian responsep9535 msSlowest 5% of checks1 ms0.5024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Neon goes down
Follow these 5 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Neon goes down. They don't count against your monitor quota. Free plan, no card required.
About Neon outages
Neon provides serverless Postgres that scales to zero and branches like Git. It is a common database choice for Vercel-hosted apps, so a Neon incident shows up as API routes failing on database connections while the frontend renders fine.
Neon's control plane and its per-region compute are separate. We probe the website, the console and its API, and the documentation; probe your own connection string through your app for the compute side.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website neon.com is unreachable. | httpneon.com | HTTP 200 | 1 min |
Console API The Neon API is not answering. Branch creation, the CLI, and integrations fail. | httpconsole.neon.tech/api/v2/projects | HTTP 401 | 2 min |
Console The Neon console is unreachable (it normally redirects to sign-in). | httpconsole.neon.tech | HTTP 200 | 2 min |
Documentation Neon's documentation is unreachable. | httpneon.com/docs | HTTP 200 | 5 min |
Console DNS The console and API hostname is not resolving. | dnsconsole.neon.tech | A record resolves | 1 min |
For component-level detail and incident write-ups from the vendor, see Neon's official status page.
Embed a live Neon badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/neon?utm_source=badge)HTML
<a href="https://www.upti.my/status/neon?utm_source=badge"><img src="https://www.upti.my/status/neon/badge.svg" alt="Neon status"></a>Recent Neon outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Neon is up. Is your Neon integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Neon and fail quietly. Here is what teams that rely on Neon monitor on their side.
Cold starts and connection errors
Scale-to-zero means the first query after idle takes longer, and connection limits are easy to hit. Probe an API route that runs a real query and validate the body.
HTTP monitoring with body validationNeon status: frequently asked questions
Check the official page for your region first. If Neon is healthy, look at compute cold starts, connection pooling, and whether your project hit its compute or connection limits. A probe through your own API route separates the two.
Look at the per-region results above. If our probes fail from every region, Neon has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Neon may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Neon" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Neon: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other databases & data infrastructure
Uptimy is not affiliated with Neon. Neon and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.