Issues with compute start on us-east-2-Major

Resolved

Started

Lasted 54m

View official incident ↗

Updates

  1. Resolved

    The incident has been successfully resolved, and normal operations have been restored to all affected systems and services. Our team conducted a thorough investigation, implemented necessary actions, and analyzed the underlying cause to prevent similar incidents in the future.

  2. Investigating

    Investigating: (10:10) Update: 🛠️ **Affected Component**: [Database Operations](https://app.incident.io/neondb/catalog/01HDK7B6RMJ2DA7AXN0MSHXQFC/01HDK7CGYXYMVBPH4EJ35W9X5B), [Console and API Requests](https://app.incident.io/neondb/catalog/01HDK7B6RMJ2DA7AXN0MSHXQFC/01HDK7C3W54S3AB18AS4GMDVP3), [Database Connectivity](https://app.incident.io/neondb/catalog/01HDK7B6RMJ2DA7AXN0MSHXQFC/01HDK7CYY3NEWAZPEBFVN4FVDW) 🚀 **Impact**: Investigating We are currently experiencing technical issues that may affect our services. Our team is diligently working to resolve these issues and restore normal operations. We understand the inconvenience this may cause and appreciate your patience. Stay tuned for further updates. Identified: (10:11) 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. Monitoring: (10:29) We identified high IO on a single node in us-east-2, which was impacting our ability to wake up endpoints. We cordoned the node, and have observed rates return to normal. We are continuing to monitor the situation to ensure there is no lasting impact.