Neon Outage History

Neon experienced a database connectivity issue that caused degraded performance for a subset of customers starting at 19:50 UTC on May 10, 2026. The incident lasted 4.8 hours and was classified as minor severity. The issue was identified and remediation was applied to resolve the service degradation.

Neon experienced database connectivity issues in US-East-1 Cell 6 starting at 00:20 UTC on May 8, 2026, affecting approximately 1,000 projects with slow or stuck compute start events. The incident lasted 2.6 hours and was mitigated by 02:21 UTC the same day.

Neon experienced a 16-minute service disruption in the us-west-2 region starting at 12:07 UTC on April 30, 2026, where customers encountered failures when creating or deleting branches and projects. Existing database connectivity remained operational throughout the incident. The issue was resolved by 12:23 UTC with normal project and branch operations restored.

Some Neon database endpoints in Azure Germany West Central became temporarily unavailable due to failures when starting new instances after scaling to zero. The incident affected database connectivity for 4 minutes before the engineering team identified the cause and applied remediation.

Neon experienced performance degradation in the SA-East-1 (Sao Paolo) region affecting Console API, Project/Branch Operations, and Database Connectivity. The engineering team identified the cause and worked on mitigation. The incident was resolved after 36 minutes.

Starting at approximately 15:52 UTC on March 10, 2026, Neon customers experienced failures when attempting to create new Datadog and OTel collector monitoring integrations through the Console Frontend. Existing integrations continued to function normally throughout the incident. The issue lasted 1.1 hours and has been resolved.

Neon experienced compute operation failures and database connectivity issues in the us-east-1-cell-4 region starting at 16:05 UTC on March 6, 2026. Customers encountered delays and failures when attempting database operations during the 12-minute incident. The service was restored after active investigation by the engineering team.

Between 00:05 UTC and 00:40 UTC on March 3, 2026, some Neon databases in the us-east-2 region experienced increased cold-start times, affecting database connectivity. The issue was mitigated after 1.1 hours and the platform continues to be monitored.