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

What to do

• Check whether you use Neon in us, us-east-2. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-08-17 22:38 UTC and 2026-08-17 22:38 UTC may need a replay.

• Subscribe to Neon's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=neon works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Neon 1

1. resolvedAug 17, 2026, 10:38 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.