Central 1 Status Page

Jun 5, 2026

All impacted payments have now been returned to members through the standard payments return process. We have made significant progress in our investigation and have successfully validated a fix in our test environments. The issue was related to a recent system update that caused a compatibility problem, resulting in transfers not being completed as expected. A change has been prepared to address this issue and is tentatively scheduled for tomorrow morning. Once the change is complete, Agility will re-enable the production connection to restore service. We will continue to provide updates as we move toward resolution. [email protected] - 1.888.889.7878 (option 2)

Jun 3, 2026 · resolved Jun 3

Central 1 has resolved the issue with BMO. Payments for BC Hydro and Capital One Mastercard were processed today, June 3. All payments have been posted to the applicable biller accounts effective the original payment date. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at [email protected].

Jun 1, 2026 · resolved Jun 1

**Postmortem: INC222639 – Outgoing and Incoming Wire Transfers Delayed** On June 1, 2026, between 7:25 and 10:55 a.m. PT \(10:25 and 1:55 a.m. ET\), a Central 1 third-party tool used for wire reviews intermittently displayed an error to Central 1 users. Despite the error messages, wire transfers continued to process in the background. Some transactions had to be manually restarted, causing a brief delay. The issue was traced to a problem with our external vendor, Fiserv’s Enterprise Payments Platform \(EPP\), which supports wire processing. Service was fully restored after the vendor made the necessary fixes, and normal operations resumed. To resolve the issue, Fiserv completed a system configuration update at 9:24 a.m. PT \(12:34 p.m. ET\), addressing a compatibility problem that was causing the errors. **Point of Failure:** Fiserv has performed a preliminary root cause analysis and determined that this incident was caused by a Fiserv vendor-managed component \(Ingress Controllers\) that was upgraded across several environments. This triggered the outage due to incompatibility with a Fiserv monitoring component used within the affected configuration \(Ingress Controller setup\). **Corrective Actions:** Fiserv is working with Microsoft to reduce the likelihood of recurrence by enhancing validation and testing procedures for configuration changes and ensuring that all server dependencies are identified and addressed before deployment. Additional monitoring will also be implemented to detect and address EPP UI proxy errors in real time. At Central 1, we improved our monitoring to catch issues with third-party systems earlier. We are also reviewing vendor support and escalation processes to help resolve issues faster. In addition, we’ve evaluated our internal incident response procedures to improve coordination and response during vendor-related outages. * Central 1 has implemented an automated daily test at 4:00 a.m. PT \(7:00 a.m. ET\) to confirm outgoing wire transfers are working properly and to detect issues earlier. We sincerely apologize for the disruption and the impact this incident had on your operations, particularly for time-sensitive wire transactions. We appreciate your patience while services were restored. Liz Ackroyd, Manager of Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337

May 22, 2026 · resolved May 28

The OIDC fix has been successfully deployed, addressing the “Remember Me” expiry issue for desktop and manual login within the mobile app. The system will now refresh the “Remember Me” cookie at login, ensuring saved login information is maintained with ongoing use. A fix for Biometric and QuickView persistence is being delivered via native Mobile App updates. These updates are being coordinated directly through Client Delivery for each client. Please reach out to your Delivery Consultant through the v18 app upgrade ticket to address timeline. The Native App hot fix does not require client testing. Once the new apps are in production end users will receive the update through the App Store (iOS) and Google Play Store (Android) (automatic for most users, depending on device settings). Once the users app has been updated, then the system will refresh the Biometric and Quickview settings when a user logs in via Biometric, ensuring saved login information is maintained with ongoing use. [email protected] - 1.888.889.7878 (option 2)

May 22, 2026 · resolved May 22

**Postmortem: INC221480 – Client Centre Intermittent Login Failures**  Between May 4 and May 22, 2026, clients experienced intermittent access issues when attempting to log in to Client Centre \([clients.central1.com](http://clients.central1.com)\). Full service was restored on May 22, 2026, at approximately 2:10 p.m. PT \(5:10 p.m. ET\).  The disruption was caused by instability within an external hosting environment supporting Client Centre at the time, which resulted in intermittent degradation of authentication services. During this period, some users experienced login failures or inconsistent access. No data loss or security concerns were identified. Central 1 restored stability by transitioning Client Centre to a Central 1-managed Azure-hosted environment, significantly improving reliability, and reducing dependency on the previous hosting platform.  For a more detailed root cause review, please refer to the Client Centre news item: [https://clients.central1.com/news\_updates/client-centre-service-disruption-update/](https://clients.central1.com/news_updates/client-centre-service-disruption-update/)  **Corrective Actions – PRB011734** * **PTASK – Transition to Central 1-managed hosting – COMPLETED** • Migrated Client Centre to an Azure-hosted environment to improve stability and control. * **PTASK – Enhance monitoring and alerting – IN PROGRESS** • Improving detection capabilities to identify degradation conditions earlier. * **PTASK – Strengthen resiliency controls – IN PROGRESS** • Implementing additional safeguards to reduce the likelihood and impact of similar disruptions. * **PTASK – Improve incident communication and escalation – IN PROGRESS** • Enhancing coordination and communication processes during service disruptions.  We apologize for the disruption experienced during this incident. Central 1 is taking these steps to strengthen platform stability, improve monitoring, and ensure a more consistent experience for clients.  Jason Seale | Director of Client Support Services [[email protected]](mailto:[email protected]) | 778.558.5627