Skip to main content
Neon logo

Is Neon Down?

No — Neon is up

Reachable from all 8 checked regions

Average response time: 1081ms

Last checked · checks run every 6 hours

Official status page: https://neonstatus.com

Neon uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
855ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 62 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

62-day clean streak
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 28 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb
1502ms
DNS 0ms TCP 0ms TLS 6ms TTFB 1501ms
lax
373ms
DNS 0ms TCP 1ms TLS 7ms TTFB 369ms
lhr
1052ms
DNS 0ms TCP 2ms TLS 14ms TTFB 1052ms
nrt
1126ms
DNS 0ms TCP 1ms TLS 8ms TTFB 1126ms
ord
295ms
DNS 0ms TCP 2ms TLS 8ms TTFB 293ms
sin
2210ms
DNS 0ms TCP 1ms TLS 8ms TTFB 2204ms
sjc
586ms
DNS 0ms TCP 11ms TLS 15ms TTFB 583ms
syd
1505ms
DNS 0ms TCP 0ms TLS 6ms TTFB 1490ms

What Neon does

Neon runs managed Postgres with storage separated from compute, so databases can scale to zero and projects can be branched like code for testing. Applications connect to it as an ordinary Postgres endpoint, which makes it a hard dependency for anything it backs. Neon publishes status per region across AWS and Azure rather than as one global figure.

What an outage looks like

Applications fail to connect and log Postgres connection errors or timeouts, and requests touching the database return 500s while static pages still serve. Creating or deleting branches fails from the console and the API, breaking preview environments in CI. The Neon console will not load or sign-in fails, sometimes while existing database connections keep working normally.

What to do about it

Check neonstatus.com and find your project's region: Neon reports Database Connectivity, Project and Branch Operations, the Console API and Console Login separately for each AWS and Azure region, so a us-east-1 incident does not mean your eu-west-2 project is affected. Console problems and connectivity problems are distinct rows, and an application can keep serving while the dashboard does not.

Is it down for everyone, or just you?

If this page says Neon is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Supabase
Supabase
MongoDB Atlas
MongoDB Atlas
Railway
Railway
Render
Render

Neon outage FAQ

Is Neon down or is it just my database?
Check neonstatus.com for your specific region rather than the overall banner, since Neon reports each AWS and Azure region separately. If your region reads operational, look at your own connection limits and at whether the compute has been suspended and is cold-starting. The measurement above probes the Neon console from several regions at once, which separates a local fault from a platform one.
Does a Neon outage mean I lose data?
No. Neon separates storage from compute, so a compute or connectivity incident stops you reaching the data rather than affecting the data itself. Writes in flight when connections dropped follow Postgres transaction semantics, meaning an uncommitted transaction rolls back. What to verify afterwards is that your application reported or retried those failed writes rather than silently dropping them.
Why can I reach my database but not the console?
Neon lists Console Frontend, Console Login and Console API as separate components from Database Connectivity. The console is a management surface, so it can fail while the Postgres endpoint your application uses keeps serving traffic. That is a real distinction during an incident: your users may be entirely fine while you cannot see or change anything.
Do preview environments break during a Neon outage?
They can, specifically when Project and Branch Operations is the affected component. Branch creation is what CI uses to give each pull request its own database, so that component failing blocks new preview environments while existing branches keep serving. Check that row rather than Database Connectivity if your pipeline is what is failing.
Should my application retry Neon connection failures?
Yes, with backoff, and set sensible connection timeouts. Neon computes can suspend when idle and take a moment to resume, so the first connection after a quiet period is slower rather than broken. Distinguishing that cold start from an outage in your own logging saves a lot of confusion, and a connection pooler in front reduces how often you pay it.

How we measure this

  • We request Neon's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Neon publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Neon goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required