All Systems Operational

Updated a few seconds ago

Database Connectivity




Operational

Project/Branch Operations




Operational

Console API




Operational

Console Frontend




Operational

Account Creation




Operational

Console Login




Operational

Website




Operational

Status page for neon.com

History (Last 30 days)

Neon Branch Reset and Restore Failures — AWS us-east-2Operational

Incident Status

Operational


Components

Console API


Locations

AWS us-east-2



August 17, 2026 10:38PM UTC
RESOLVED

Between 20:00 UTC and 21:15 UTC on August 17, 2026, a subset of customers using Neon databases in AWS us-east-2 may have experienced delays or failures when performing branch reset and restore operations. A configuration rollout caused these requests to fail on the backend; the Neon Console automatically retried them, so affected requests appeared to hang. The change has been rolled back, and all services are operating normally. Customers may have observed:  - Branch reset and restore requests via the Neon Console or API are hanging or taking longer than usual to complete  - Requests that did not complete and had to be canceled manually The issue has been fully resolved, and all services are operating normally. We apologize for any inconvenience. If you require further details, please submit a support ticket.
Issue with starting computes in us-east-1Degraded Performance

Incident Status

Degraded Performance


Components

Project/Branch Operations


Locations

AWS us-east-1



August 10, 2026 2:53PM UTC
INVESTIGATING

Starting at approximately 14:30 UTC August 10, 2026, a subset of customers in us-east-1 region may experienced an unavailability and blocked compute suspension. Startup of new computes and scale from zero are not affected. We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant.

August 10, 2026 3:02PM UTC
RESOLVED

Between 14:30 UTC and 14:57 UTC on August 10, 2026, a subset of customers in us-east-1 region may have experienced an unavailability and blocked compute suspension. Startup of new computes and scale from zero was not affected. The issue has been fully resolved, and all services are operating normally. We apologize for any inconvenience.