**Resolution Summary:** This issue has been resolved. All systems are operational, and performance has returned to normal levels. **Final Impact:** Service has been fully restored. **Next Update:** A post-incident review will be conducted and communicated as appropriate.
**Action Taken:** A fix has been implemented. **Current Status:** We are actively monitoring system performance metrics. **Impact Status:** User-facing impact should be subsiding. **Next Update:** Within 30 minutes or sooner upon confirmation of full resolution.
**Additional Details:** fix is deployed, watching metrics
Posted Feb 12, 2026 - 09:00 EST
Identified
**Summary:** The cause of this issue has been identified. **Planned Actions:** Our team is implementing a fix. **Next Update:** Within 30 minutes or sooner once the fix is implemented.
**Additional Details:** DB connection pool issue
Posted Feb 12, 2026 - 09:00 EST
Update
**Status Update:** Our team continues to investigate and work on this issue. **Next Update:** We will provide another update within 30 minutes or sooner as new information becomes available.
**Additional Details:** still investigating, restarting tomcats
Posted Feb 12, 2026 - 08:59 EST
Investigating
**What we know:** We are aware of an issue affecting Labs and are actively investigating the matter. **Impact:** Some users may experience service interruptions. **Current Actions:** Our team is working to identify the root cause and restore full functionality. **Next Update:** We will provide updates every 30 minutes or as new information becomes available until this issue has been resolved.
**Additional Details:** customers can't process orders
Posted Feb 12, 2026 - 08:53 EST
This incident affected: EMA Cluster 48 (sbpod05) (Labs).