Resolved
**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.
Posted Feb 12, 2026 - 12:30 EST
Update
**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:** We continue to monitor improvements in AI-Scribe performance and the status of the third-party service provider.
Posted Feb 12, 2026 - 12:01 EST
Monitoring
**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:** Third-party has applied a fix. We are monitoring improvements in performance.
Posted Feb 12, 2026 - 11:26 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:** A third-party outage is impacting AI-Scribe functionality. We are monitoring for updates.
Posted Feb 12, 2026 - 10:56 EST
Investigating
**What we know:** We are aware of degraded performance affecting Clinical and are actively investigating the matter.
**Impact:** Most services are available and operational, but users may experience degraded performance. We will provide updates as new information becomes available.
**Current Actions:** Our team is actively investigating the root cause.
**Next Update:** We will provide updates every 30 minutes or as new information becomes available until this issue has been resolved.
**Additional Details:** Customers may experience issues using AI-Scribe.
Posted Feb 12, 2026 - 10:23 EST
This incident affected: EMA Cluster 03 (pod03) (Clinical), EMA Cluster 04 (pod04) (Clinical), EMA Cluster 05 (pod05) (Clinical), EMA Cluster 06 (pod06) (Clinical), EMA Cluster 07 (pod07) (Clinical), EMA Cluster 08 (pod08) (Clinical), EMA Cluster 09 (pod09) (Clinical), EMA Cluster 10 (pod10) (Clinical), EMA Cluster 11 (pod11) (Clinical), EMA Cluster 12 (pod12) (Clinical), EMA Cluster 13 (pod13) (Clinical), EMA Cluster 14 (pod14) (Clinical), EMA Cluster 15 (pod15) (Clinical), EMA Cluster 16 (pod16) (Clinical), EMA Cluster 17 (pod17) (Clinical), EMA Cluster 18 (pod18) (Clinical), EMA Cluster 19 (pod19) (Clinical), EMA Cluster 20 (pod20) (Clinical), EMA Cluster 21 (pod21) (Clinical), EMA Cluster 22 (pod22) (Clinical), EMA Cluster 23 (pod23) (Clinical), EMA Cluster 24 (pod25) (Clinical), EMA Cluster 25 (pod27) (Clinical), EMA Cluster 26 (pod29) (Clinical), EMA Cluster 27 (pod31) (Clinical), EMA Cluster 28 (pod33) (Clinical), EMA Cluster 29 (pod35) (Clinical), EMA Cluster 30 (pod37) (Clinical), EMA Cluster 31 (pod39) (Clinical), EMA Cluster 32 (pod41) (Clinical), EMA Cluster 33 (pod43) (Clinical), EMA Cluster 34 (pod45) (Clinical), EMA Cluster 35 (pod47) (Clinical), EMA Cluster 36 (pod49) (Clinical), EMA Cluster 37 (pod51) (Clinical), EMA Cluster 38 (adpod01) (Clinical), EMA Cluster 39 (eapod01) (Clinical), EMA Cluster 40 (eapod02) (Clinical), EMA Cluster 41 (eapod03) (Clinical), EMA Cluster 42 (efpod01) (Clinical), EMA Cluster 43 (efpod02) (Clinical), EMA Cluster 44 (efpod03) (Clinical), EMA Cluster 45 (mepod01) (Clinical), EMA Cluster 01 (pod01) (Clinical), EMA Cluster 02 (pod02) (Clinical), EMA Cluster 46 (sbpod01) (Clinical), EMA Cluster 47 (sbpod03) (Clinical), EMA Cluster 48 (sbpod05) (Clinical), and EMA Cluster 49 (vwpod01) (Clinical).