Neon

Neon reimagined what a PostgreSQL hosting service could look like in a serverless world. Rather than provisioning a database server that runs continuously — billing for idle time and requiring manual scaling operations — Neon separates compute from storage, autoscales compute capacity to zero when no connections are active, and charges for actual usage. The architecture allows database branches, a concept borrowed from version control, where developers can create a copy-on-write snapshot of their database for testing, staging, or feature development without duplicating the full data volume. These capabilities made Neon popular with frontend frameworks like Next.js and Vercel, where serverless compute and serverless databases pair naturally.

The technical foundation that enables these features also creates distinctive failure modes. Neon's storage layer — which handles the actual durable persistence of data — is separated from the compute layer that runs PostgreSQL query processing. A healthy compute node cannot serve queries if the storage layer is degraded, and the connection pooler that manages database connections from serverless functions must coordinate with both layers. Cold-start latency — the brief pause while a compute node scales up from zero — is a normal Neon behaviour, but infrastructure problems can cause cold-starts to fail entirely rather than taking longer than usual, resulting in connection timeout errors rather than slow initial response.

Developers hitting Neon incidents typically see PostgreSQL connection errors from their application runtime. Serverless functions that use Neon via the Neon serverless driver or standard PostgreSQL drivers receive connection refused or connection timeout errors when compute autoscale events fail. The Neon console — where developers manage branches, monitor query activity, and configure connection strings — may be unavailable independently from the database service itself. Database branch creation operations, which rely on Neon's branching infrastructure, can fail while existing branch connections remain usable, or vice versa.

Outage.gg aggregates real-time community reports from Neon users and developers. If database connections are failing, the console is inaccessible, or branch operations are timing out, the live status page shows current incident data from the Neon user community.