Neon

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-21 18:22 UTC

   We are investigating an issue with the Console Monitoring Page starting around 17:20 UTC. Monitoring data may be delayed. Data from before 17:20 UTC should still be available.

2. monitoring 2026-10-21 19:40 UTC

   Between 17:20 UTC and 18:42 UTC October 21 2026, an issue with Console Monitoring may have led to delayed or missing monitoring data. A fix has been applied as of 18:42 UTC.

3. resolved 2026-10-21 19:56 UTC

   Between 17:20 UTC and 18:42 UTC October 21 2026, an issue with Console Monitoring may have led to delayed or missing monitoring data. This issue is now resolved.

Excerpts are shortened. Read the full incident on Neon's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. resolved 2026-08-17 22:38 UTC

   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...

Excerpts are shortened. Read the full incident on Neon's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. investigating 2026-08-10 14:53 UTC

   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...

2. resolved 2026-08-10 15:02 UTC

   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...

Excerpts are shortened. Read the full incident on Neon's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-07-31 10:40 UTC

   Starting at 14:47 UTC on July 30, 2026, customers might experience an error during account creation. The issue only impacts new account registrations. Customers may observe: New account registrations are failing. Next Update We will provide another update within 1 hour, or...

2. identified 2026-07-31 11:54 UTC

   Starting at 14:47 UTC on July 30, 2026, customers might experience an error during account creation. The issue only impacts new account registrations. Customers may observe: New account registrations are failing. We identified the issue and are applying the remediation. Further...

3. resolved 2026-07-31 12:30 UTC

   Between 14:47 UTC, July 30, 2026, and 12:26 UTC, July 31, 2026, a subset of customers may have experienced errors during account creation. The issue only impacted new account registrations. The issue has been fully resolved, and all services are operating normally. We apologize...

Excerpts are shortened. Read the full incident on Neon's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-15 23:18 UTC

   Between 21:59 UTC and 22:33 UTC July 15 2026, customers in EU-Central-1 may have encountered failures waking up databases due to certain compute and suspend operations being stuck. This issue is Resolved.

Excerpts are shortened. Read the full incident on Neon's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-07-11 09:51 UTC

   Starting at 4:50 UTC on July 11, 2026 , customers might experience elevated API latency on compute operations. Customers may observe: Databases failing to start Project operations failing to complete. Next Update We will provide another update within 1 hour, or sooner if there...

2. resolved 2026-07-11 10:24 UTC

   Further investigation has confirmed that this issue did not impact Database or project operations on the platform. We apologize for the inconvenience. Next Update No further updates are planned unless there is a material change in service status.

Excerpts are shortened. Read the full incident on Neon's status page.