Is Central 1 down?

Please be advised that IOS users have login failures with mobile app. At this time the login for the Forge mobile app in iOS devices is not working. We are actively investigating to identify the root cause and assess the impact. Users using biometric login, Android app and desktop Online banking are not affected. We are conducting a thorough analysis of the systems involved and working toward resolving the issue.

Intellect Design continues to investigate an issue affecting a subset of users attempting to log in to the Forge mobile app on iOS devices using their password. This issue does not affect all Credit Unions or all iOS users. Android users and users logging in with biometrics continue to be unaffected. As a workaround, affected users can access Online Banking through their mobile device's web browser while we continue to investigate the iOS app login issue. All relevant teams are engaged and actively working to identify the cause and restore normal login functionality. Our next update will be provided within two hours. Central 1 - [email protected] - 1.888.889.7878, press 2

The issue affecting a subset of Forge mobile app users on iOS devices when using password login has been resolved. Investigation identified a Web Application Firewall (WAF) rule change that was impacting this specific login traffic. The rule has been adjusted and login functionality has been restored. Android users and biometric login were not affected, and the issue did not impact all Credit Unions or all iOS users. All relevant teams remain engaged and are monitoring the service. Further investigation will be completed with Intellect Design to understand why the WAF rule affected this traffic and to identify any appropriate preventative measures. Central 1 - [email protected] - 1.888.889.7878, press 2

Central 1 recommends that PaymentStream AFT users with the Data Entry service review AFT records with due dates from November onward to verify their accuracy. The fix implemented on October 21 at 1:00 a.m. PT (4:00 a.m. ET) resolved the issue that caused due dates to shift back by one day when AFT records were created or modified. Please review any records created or modified before the fix was implemented to ensure the correct due date is reflected. Central 1 - [email protected] - 1.888.889.7878, press 1

Central 1 recently completed an assessment of the newly disclosed zero-day vulnerabilities affecting PHP, a widely used technology that underpins many web-based platforms, including WordPress. We are aware that clients may have concerns regarding the potential impact to Forge online banking services. As part of our investigation, Central 1 reviewed the applicability of these vulnerabilities across our environment. The assessment determined that the identified PHP exposure was limited to a non-critical vanity URL redirect service used by a single client feature. As a precautionary measure, this service was taken offline. Additional housekeeping activities were also completed, including the removal of PHP from systems where it was not required and the removal of an obsolete service. As a result of these actions, the identified threat exposure has been contained, and no additional remediation activities are currently required. At this time, there is no evidence that Central 1 online banking services have been compromised or adversely affected by these vulnerabilities. We will continue to monitor the situation and follow our established security response processes should new information become available. [email protected] 1.888.889.7878 (option 2)

Central 1 has identified an issue where some organizations may not have received the CAD Online Return Processed Items (ORPI) and USD Cheque Return (ORUI) reports dated October 19, 2026, in this morning's MERG file. If your organization did not receive a report, or received a blank report, the missing report details will be included in tomorrow's MERG file. For Ontario credit unions, the reports will also be available in their SFTP folder. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

Central 1 has continued to monitor User Management (UM), EFM, AFT and Wires following the earlier sign-in issue. Services have remained stable and no further issues have been observed. This incident is now considered resolved. If you continue to experience sign-in issues, please contact Central 1 Support. Central 1 - [email protected] - 1.888.889.7878, press 1

**Postmortem: INC229690 – 2SS Applications Unavailable \(UM, Wires, AFT, EFM\)** On October 14, 2026, users experienced authentication and access failures across applications that rely on 2-Step Security \(2SS\), including User Management \(UM\), Wires, AFT, and EFM. Multiple clients reported being unable to access affected applications, including sign-in failures and HTTP 500 errors. The issue was resolved following a restart of the 2SS service, restoring access to the affected applications. **Point of Failure:** The outage was caused by an unintended application dependency on libraries contained within a backup folder located in the active 2SS webapps directory. Earlier in October, vulnerability remediation updates had been deployed to the 2SS environment, with a backup copy of the application retained in this directory as a rollback option. The backup was believed to be inactive and not part of the production application path. Following the deployment, a hard-token provisioning issue was investigated under a separate incident, INC229174. During troubleshooting, an older library within the backup folder was identified as potentially interfering with the newly deployed code. Because the folder was understood to be used solely for rollback purposes, its contents were removed to eliminate the possibility that the older libraries were contributing to the provisioning issue. However, the running application was actively referencing libraries contained within this location. Removal of those files therefore caused the 2SS service to fail, resulting in authentication and access failures across dependent applications. The vulnerability remediation deployment itself did not directly cause the outage. Rather, the incident exposed an unintended dependency within the application environment: files retained as a backup were being referenced by the running production application. The risk associated with removing the backup contents was therefore not known prior to the troubleshooting activity. During the outage, customers were unable to access applications dependent on 2SS, including User Management, Wires, AFT, and EFM. Reported symptoms included general sign-in failures, inability to access User Management and Wires, and HTTP 500 errors when accessing EFM. The 2SS service was restarted at 2:10 p.m. PT and service was restored at 2:11 p.m. PT. Affected customers subsequently confirmed successful access to their applications. **Corrective Actions:** Follow-up actions are focused on addressing the underlying application dependency and strengthening deployment and troubleshooting practices within the 2SS environment. * **Separate backup artifacts from active application paths:** Review the storage of application backups and rollback artifacts to ensure they are isolated from active production application directories and cannot inadvertently be referenced at runtime. * **Validate application dependencies:** Review the 2SS application configuration and dependencies to identify and eliminate unintended references to libraries or components outside the intended production application structure. * **Strengthen deployment and rollback procedures:** Update deployment and rollback practices to clearly distinguish active application components from backup copies and include validation following changes to application files. * **Improve hard-token provisioning validation:** Review opportunities to improve validation of hard-token provisioning following application changes, reducing reliance on post-deployment external validation. We sincerely apologize for the disruption caused by this incident and are taking these steps to strengthen our deployment and application management practices and reduce the likelihood of recurrence. **Enquiries:** Jason Seale | Director, Incident & Service Management | [[email protected]](mailto:[email protected]) | 778.558.5627