Skip to main content
Vendor reliability

Vendor record

Neon

Vendor reports Operational

Checked

Front door check counts and Neon’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Neon endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,878 of 2,878 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    1 more check gave no clear answer and is not counted.

    Endpoint checked
    console.neon.tech
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Neon product, region or your app worked.

How we count front door checks

Neon says

Incident posts from Neon’s status page, with its titles, impact levels and times. They say what Neon chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

0

incidents Neon posted, last 180 days

All vendors’ incidents

Most recent records · all dates

  • Database Maintenance

    Minor

    Started, per Neon

    Closed in our record(8h 27m)

    Neon’s post
  • Internal databases maintenance

    Minor

    Started, per Neon

    Closed in our record(8h 51m)

    Neon’s post

Your code, your dependencies

See which of your code paths call Neon

Connect GitHub or GitLab to find where your public or private repository uses Neon. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Neon status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · NeonStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/neon?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Neon status badge"></iframe>

Frequently Asked Questions

Is Neon currently down?

Neon's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Neon last have an outage?

The most recent closed incident record began 184 days ago and spans 8h 51m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Neon?

No. CheckUpstream checks Neon’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Neon in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

What does Neon do?

Neon is a serverless PostgreSQL platform used by developers and engineering teams to create, manage, and scale databases. It provides a cloud-based database service with an API and web console for provisioning, branching, monitoring, and connecting to PostgreSQL instances. The service is commonly used for application backends, development environments, and database workflows that need automated scaling and lifecycle management.

How does CheckUpstream track Neon?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.