Changes / Neon / Stuck Start Compute Operations
Neon: Major incident: Stuck Start Compute Operations
Summary
Summary pending. The diff below shows exactly what changed.
What changed
Before: not present
After: Stuck Start Compute Operations
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-05-16 15:01 UTC
Before: not present
After: 2025-05-16 19:11 UTC
Before: not present
After: Project/Branch Operations
Before: not present
After: Identified: (13:34) We have identified the underlying cause of this incident and are actively working to implement a resolution. Our team is committed to resolving this issue as quickly as possible to minimize any further impact. Identified: (15:52) We continue to investigate the ongoing outage. The team is committed to resolving this as soon as possible and minimizing further impacts. Identified: (16:04) We have implemented fixes in order to resolve the issue and databases are returning to normal states. We continue to monitor the fix and determine root cause. Identified: (17:08) We hit one more issue with EKS ip address allocation due to size of Kubernetes cluster while addressing previous issue. Rolling out fix right now and seeing recovery of operations rate. Monitoring: (17:54) The issue is mitigated and we are continuing to monitor the situation.
Before: not present
After: The issue has been fully resolved. All affected components are operating normally again.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Stuck Start Compute Operations (this change) | Major incident |