Neon had 9 outages in the last 2 years totaling 19h 53m of downtime — averaging 0.4 incidents per month.
There were 9 Neon outages since April 19, 2026 totaling 19h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 19:28 UTC and 20:35 UTC June 17, 2026, customers in the Germany West Central (Azure) region may have experienced failures while creating or deleting branches, or projects. The issue has been mitigated. We will continue to monitor the platform and confirm resolution.
Starting at approximately at 10:30 UTC June 01, 2026, customers in eu-central-1 region may experience failures while creating or deleting branches, or projects, connections to new database created might be affected. Existing database connectivity remains unaffected. We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant.
Starting at approximately at 10:30 UTC June 01, 2026, customers in eu-central-1 region may experience failures while creating or deleting branches, or projects, connections to new database created might be affected. Existing database connectivity remains unaffected. We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant.
Between 10:30 UTC and 11:10 UTC June 01, 2026, customers in eu-central-1 region may have experienced failures while creating or deleting branches, or projects, connections to new database created might have been affected. Existing database connectivity remained unaffected. The issue has been mitigated. We will continue to monitor the platform and confirm resolution. Further updates will be provided within the next hour, or as events warrant.
We are actively investigating an issue with a Neon service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately at 10:22 UTC June 01, 2026, customers in us-east-1 region may experience failures while creating or deleting branches, or projects, connections to new database created might be affected. Existing database connectivity remains unaffected. We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant.
Between 10:22 UTC and 11:32 UTC, June 01, 2026, customers may have experienced failures while creating new projects or branches. The issue has been mitigated. We will continue to monitor the platform and confirm resolution. Further updates will be provided within the next hour, or as events warrant.
Starting at approximately 12:30 UTC May 25, 2026, customers may experience failures or delays in compute operations or database connectivity. We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant.
Starting at approximately 12:30 UTC May 25, 2026, customers may experience failures or delays in compute operations or database connectivity. We identified the issue and are applying the remediation. Further updates will be provided within the next hour, or as events warrant.
Between 12:30 UTC and 14:15 UTC May 25, 2026, customers may have experienced failures or delays in compute operations or database connectivity. The issue has been mitigated. We will continue to monitor the platform and confirm resolution. Further updates will be provided within the next hour, or as events warrant.
We are actively investigating an issue with a Neon service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary Starting at 19:50 UTC May 10 2026, a subset of customers may experience degraded performance on Neon. Current Status We identified the issue and are applying the remediation. Recommendations No customer action is required at this time. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary Starting at 19:50 UTC May 9 2026, a subset of customers may experienced connectivity issues and elevated error rates for database and console operations. Current Status We have applied mitigations and have observed recovery. We are monitoring to confirm full resolution. Recommendations No customer action is required at this time. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 00:20 May 8, 2026, customers may experience connectivity issues with databases in US-East-1 Cell 6 We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant.
Between 00:20 UTC and 02:21 UTC May 8, 2026, approximately 1,000 projects in US-East-1 Cell 6 experienced slow or stuck compute start events. The issue has been mitigated. We will continue to monitor the platform and confirm resolution. Further updates will be provided within the next hour, or as events warrant.
Starting at 20:03 UTC on May 7, 2026, a subset of customers using Neon databases in AWS us-east-1 may have experienced issues with compute endpoints not scaling down to zero after periods of inactivity. Mitigation has been applied, and affected endpoints are recovering. We are monitoring to confirm full resolution. Customers may have observed: - Issues starting recently with suspended compute's - Database compute endpoints not suspending during periods of inactivity - Unexpected active compute usage for idle databases No customer action is required at this time. We will provide a further update within 1 hour, or sooner if there is a material change in status.
Starting at approximately 12:13 UTC April 30, 2026, customers may experience failures while creating or deleting branches, or projects. Existing database connectivity remains unaffected. We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant.
Between 12:07 UTC and 12:40 UTC April 30, 2026, customers may have experienced failures while creating or deleting branches, or projects. Existing database connectivity remained unaffected. The issue has been mitigated. We will continue to monitor the platform and confirm resolution. Further updates will be provided within the next hour, or as events warrant.