Resolved - INC216206 - Universal Connectivity Proxy (UCP) outage

Update timeline

1. investigating Feb 01, 2026, 11:10 AM UTC

   Central 1 is currently experiencing an issue with our Universal Connectivity Proxy (UCP), which connects to third-party applications and certain internal applications. As a result, multiple services across PaymentStream, Interac (e-Transfers), MemberDirect, Forge, and Originations are not available. An update will be posted by 4 a.m. PT (7 a.m. ET). Central 1 - [email protected] - 1.888.889.7878

2. monitoring Feb 01, 2026, 12:12 PM UTC

   Central 1 has rolled back a change to the UCP that affected all 3rd-party connections. Connections are recovering, and Central 1 is monitoring the connections. An update will be posted by 5 a.m. PT (8 a.m. ET). Central 1 - [email protected] - 1.888.889.7878

3. resolved Feb 01, 2026, 12:27 PM UTC

   The UCP change was successfully rolled back, and all 3rd-party connections were restored. If you are experiencing any connection issues after this incident, please contact Central 1. Central 1 - [email protected] - 1.888.889.7878

4. postmortem Feb 20, 2026, 10:32 PM UTC

   **Postmortem: INC216206 -** **Universal Connectivity Proxy \(UCP\) Outage – February 1, 2026** On Sunday, February 1, beginning at approximately 1:38 a.m. PT \(4:38 a.m. ET\), Central 1 experienced a critical outage impacting the Universal Connectivity Proxy \(UCP\) following the deployment of a minor release \(CHG161055\). The UCP is a shared infrastructure component supporting multiple external integrations and payment applications. As a result of this failure, all traffic flowing through UCP was disrupted. Primary impacts included e-Transfer services, Forge and MD Login authentication, Deposit Anywhere, ISO20022 banking host connections, and various third-party connections. Services were fully restored at 4:02 a.m. PT \(7:02 a.m. ET\) following a rollback to the previous stable version. **Point of Failure:** The outage was caused by a misconfiguration within the deployment automation \(Chef Cookbook\) associated with UCP version. Required startup and logging configurations were not included in the release package. This resulted in application logging failure at startup, which cascaded into broader application-level failures, preventing UCP from successfully processing incoming traffic. Existing health checks validated service availability at a technical level but did not confirm functional transaction processing, causing a delay in triage. Central 1 has made enhancements to the UCP monitoring along with a review of the deployment tools improvements to help mitigate a reoccurrence. **Corrective Actions \(PRB011669\)** * PTASK0010487 - Make required Chef Cookbook changes for PROD – COMPLETED * PTASK0010488 - Document improved release process for UCP - COMPLETED We sincerely apologize for the disruption this incident caused. We recognize the critical nature of UCP as a shared service and the broad impact when it becomes unavailable. [[email protected]](mailto:[email protected]) | 1.888.889.7878