Where does this status come from?

From Neon's own status API at https://neonstatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Neon's words.

How can my agent or app check Neon status?

Fetch https://upbutler.com/status/neon/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"neon"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Neon's?

Add "neon" to the dependencies of your UpButler workspace. When one of your monitors fails while Neon has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Neon down?

Right now

No. Neon is operational.

No incidents reported.

Read from neonstatus.com 35 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/neon/status.agent.json

MCP: upstream_status {"service":"neon"}

Serverless Postgres per cloud region. Connection and control-plane incidents are reported separately.

What Neon reports

Operational

Taken as is from Neon's own status API. Incident titles and component names below are theirs.

Open neonstatus.com

UpButler's independent probe

There is no keyless endpoint of Neon that says anything useful, so UpButler does not probe it. To check your own Neon account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Neon components

12 operational

Database ConnectivityOperational
Project/Branch OperationsOperational
Console APIOperational
Console FrontendOperational
Account CreationOperational
Console LoginOperational
WebsiteOperational
Object StorageOperational
FunctionsOperational
AI GatewayOperational
Managed Better AuthOperational
Data APIOperational

Neon incidents, last 90 days

No finished incidents on record yet. UpButler keeps what Neon publishes for 90 days from the day it starts tracking a service.

Tell your outage from Neon's

Declare that your project depends on Neon. When one of your monitors fails while Neon has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - neon

Ask before you retry

curl -s https://upbutler.com/status/neon/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "neon",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Neon down right now?: No. As of 2026-10-10 05:13 UTC, Neon is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Neon's own status API at https://neonstatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Neon's words.
How can my agent or app check Neon status?: Fetch https://upbutler.com/status/neon/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"neon"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Neon's?: Add "neon" to the dependencies of your UpButler workspace. When one of your monitors fails while Neon has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in databases and data

UpButler is not affiliated with Neon. Status and incident text belong to Neon and are read from their public status source; the probe result is UpButler's own measurement.