Skip to main content

Is Neon Down?

No — Neon is up

Reachable from all 8 checked regions

Average response time: 833ms

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
845ms
Avg response, 30 days

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

30-day history

11-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: 100.00% uptime, 16 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 24 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 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.

gru
522ms
DNS 0ms TCP 3ms TLS 9ms TTFB 519ms
iad
149ms
DNS 1ms TCP 1ms TLS 6ms TTFB 146ms
jnb
1387ms
DNS 0ms TCP 0ms TLS 7ms TTFB 1383ms
lax
669ms
DNS 0ms TCP 1ms TLS 8ms TTFB 666ms
lhr
950ms
DNS 0ms TCP 2ms TLS 10ms TTFB 945ms
nrt
1186ms
DNS 0ms TCP 1ms TLS 7ms TTFB 1183ms
ord
268ms
DNS 0ms TCP 1ms TLS 13ms TTFB 265ms
sin
1770ms
DNS 0ms TCP 1ms TLS 7ms TTFB 1767ms
sjc
286ms
DNS 0ms TCP 1ms TLS 8ms TTFB 283ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

Supabase
Supabase
MongoDB Atlas
MongoDB Atlas
R
Railway
R
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 — 8 of them answered the most recent check.
  • 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required