Central 1 Outage History

Started Oct 23, 2026, 07:35 PM UTC· resolved Oct 23, 2026, 07:35 PM UTC

1. resolved Oct 23, 2026, 07:35 PM UTC

   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

Read the full incident report →

Started Oct 22, 2026, 06:25 PM UTC· resolved Oct 22, 2026, 08:12 PM UTC

1. monitoring Oct 22, 2026, 06:25 PM UTC

   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)

Read the full incident report →

Started Oct 20, 2026, 12:19 PM UTC· resolved Oct 20, 2026, 12:19 PM UTC

1. resolved Oct 20, 2026, 12:19 PM UTC

   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)

Read the full incident report →

Started Oct 14, 2026, 11:39 PM UTC· resolved Oct 14, 2026, 11:39 PM UTC

1. resolved Oct 14, 2026, 11:39 PM UTC

   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

2. postmortem Oct 23, 2026, 10:02 PM UTC

   **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

Read the full incident report →

Started Oct 14, 2026, 10:04 PM UTC· resolved Oct 14, 2026, 10:04 PM UTC

1. resolved Oct 14, 2026, 10:04 PM UTC

   Application login using 2SS (2-Step-Security) may be failing Central 1 is aware that User Management (UM), EFM, AFT and Wires applications may have returned an error message between 2:10 to 2:15 p.m. PT (5:10 to 5:15 p.m. ET). Central 1’s technical teams are monitoring service for stability. If you are continuing to have sign-in errors please contact support. An update will be provided by 4:30 p.m. PT (7:30 p.m. ET). Central 1 - [email protected] - 1.888.889.7878, press 1

Read the full incident report →

Started Oct 14, 2026, 12:17 PM UTC· resolved Oct 14, 2026, 12:17 PM UTC

1. resolved Oct 14, 2026, 12:17 PM UTC

   Due to a technical issue, the EMCD (Detailed Transaction Listing) and EMC2 (Daily Detailed Transaction Report - Provincial Central) reports expected on October 14 were delayed and not included in this morning's MERG1014 file. We will include the delayed reports in tomorrow's MERG1015 file and FTP folders (ON). All reports, including EMC1, EMCC, EMCU, ECCX, EMCD, and EMC2, were processed successfully. Central 1 - [email protected] - 1.888.889.7878, press 1

Read the full incident report →

Started Oct 09, 2026, 05:07 PM UTC· resolved Oct 09, 2026, 05:50 PM UTC

1. identified Oct 09, 2026, 05:07 PM UTC

   Interac has informed Central 1 that they are currently investigating an issue impacting the Interac e-Transfer service. As a result, Participants may experience service disruptions or delays when using Interac e-Transfer services. Incident Start Time: 9:45 a.m. PT (12:45 p.m. ET) Interac has advised that their technical teams are actively investigating the issue and working toward resolution. This issue originates within the Interac e-Transfer service. Central 1 is monitoring the situation closely and will continue to provide updates as they are received from Interac. Central 1 will post updates approximately every hour, or sooner if Interac provides notification of service restoration or additional information. Central 1 - [email protected] - [email protected] - 1.888.889.7878

2. monitoring Oct 09, 2026, 05:13 PM UTC

   Central 1 has observed that Interac e-Transfer transaction activity appears to have recovered following a service disruption that affected the platform between approximately 9:21 a.m. PT and 9:45 a.m. PT (12:21 p.m. ET to 12:45 p.m. ET). At this time, Interac e-Transfer services appear to be processing normally; however, Central 1 is awaiting confirmation from Interac regarding service stability and formal incident resolution. Central 1 continues to monitor the situation closely and will provide further updates as information becomes available from Interac. Central 1 - [email protected] - [email protected] - 1.888.889.7878

3. resolved Oct 09, 2026, 05:50 PM UTC

   Interac has confirmed that the e-Transfer service disruption has been resolved and recovery activities are complete. During the recovery period, Central 1 observed a small number of transaction timeouts due to elevated service latency until approximately 10:28 a.m. PT. These issues have since recovered, and services are operating normally. We will continue to monitor the platform; however, this incident is now considered resolved.

4. postmortem Oct 23, 2026, 03:34 AM UTC

   Postmortem: INC229450 – Interac e-Transfer Service Outage On October 9, 2026, Interac experienced an e-Transfer service disruption between approximately 9:21 a.m. and 9:45 a.m. PT \(12:21 p.m. and 12:45 p.m. ET\). During this period, financial institutions using the Interac e-Transfer platform experienced transaction failures, service disruptions, and delays. Interac reported that approximately 147,920 transactions were affected across all financial institutions. Following the initial recovery, Central 1 continued to observe a small number of transaction timeouts due to elevated Interac service latency until approximately 10:28 a.m. PT \(1:28 p.m. ET\). These timeouts subsequently recovered, and services returned to normal. In its postmortem, Interac confirmed that the incident was caused by "an Oracle software defect impacting Dynamic Resource Mastering operations," which resulted in a prolonged database hang and disrupted transaction processing. In simpler terms, a defect within Interac's Oracle database environment temporarily prevented the e-Transfer platform from processing transactions normally. Interac restored service by restarting the affected services, restoring database connectivity, and redistributing processing across its database environment. Performance remained elevated during stabilization but returned to normal once processing workloads were rebalanced. Interac has since implemented Oracle's recommended fix across its production environments and updated its Severity 1 communication procedures. Interac continues to work with Oracle to obtain a detailed root cause analysis and review how critical software defects are communicated. Central 1 will continue to monitor Interac's remaining corrective actions through Interac Problem PRB0042951. Interac's Corrective Action Status Target/Completion Date \* Obtain a detailed root cause analysis from Oracle In progress October 2026 \* Implement Oracle's recommended fix in the production environment Completed October 15, 2026 \* Update and reinforce timely Severity 1 communication procedures Completed October 16, 2026 \* Review Oracle's notification process for critical software defects In progress To be determined

Read the full incident report →

Started Oct 06, 2026, 11:07 AM UTC· resolved Oct 06, 2026, 11:59 AM UTC

1. investigating Oct 06, 2026, 11:07 AM UTC

   Please be advised that members may have intermittent login failures on Retail and Small Business banking. We are actively investigating to identify the root cause and assess the impact. We are conducting a thorough analysis of the systems involved and working toward resolving the issue. We will provide an update by 5:00 a.m. PT (8:00 a.m. ET). [email protected] - 1.888.889.7878

2. resolved Oct 06, 2026, 11:59 AM UTC

   The incident has been resolved. We will complete a postmortem, and share these results when available. [email protected] - 1.888.889.7878, option 2

Read the full incident report →

Started Sep 29, 2026, 02:41 PM UTC· resolved Sep 29, 2026, 03:26 PM UTC

1. investigating Sep 29, 2026, 02:41 PM UTC

   Central 1 has identified an issue affecting multiple credit unions where the Online Return Processed Items (ORPI) and USD Cheque Return (ORUI) reports dated September 29, 2026, have not been received as expected this morning. Our technical team is actively investigating the issue. We will provide our next update by 12:00 p.m. PT (3:00 p.m. ET), or sooner if additional information becomes available. If you have any questions, please contact Central 1 Support at [email protected] or 1.888.889.7878 (press 1).

2. resolved Sep 29, 2026, 03:26 PM UTC

   Central 1 has resolved the issue affecting the ORPI and ORUI cheque return reports. The impacted ORPI and ORUI reports have been successfully regenerated. Please note that the affected cheque return records will be included in tomorrow's MERG file. For Ontario credit unions, the reports will be available in their SFTP folder. If you continue to experience issues accessing your ORPI\ORUI reports, or if you believe any records are missing after tomorrow's MERG file has been received, please contact Central 1 Support and provide examples for further investigation. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

Read the full incident report →

Started Sep 25, 2026, 08:10 PM UTC· resolved Sep 25, 2026, 11:16 PM UTC

1. investigating Sep 25, 2026, 08:10 PM UTC

   Central 1 has identified a discrepancy with the net activity and the ending balance for the daily AIBC banking reports for September 25, 2026. While this matter is being investigated, the correct balances are displayed in the CDJ and USDJ reports. Central 1 will provide an update by 2:30 p.m. PT (5:30 p.m. ET) or sooner if the incident is resolved. Central 1 - [email protected] - 1.888.889.7878, press 1

2. resolved Sep 25, 2026, 11:16 PM UTC

   Central 1 has resolved the issue and regenerated all the reports. Central 1 - [email protected] - 1.888.889.7878, press 1

Read the full incident report →

Started Sep 21, 2026, 03:57 PM UTC· resolved Sep 21, 2026, 06:26 PM UTC

1. investigating Sep 21, 2026, 03:57 PM UTC

   Globex 2000 has notified Central 1 they are experiencing system issues and users are receiving a “500 - Service error” message when trying to access the FX Notes application. Central 1 and Globex 2000 are investigating and we will provide an update by 11 a.m. PT (2 p.m. ET) or sooner if the incident is resolved. Central 1 - [email protected] - 1.888.889.7878, press 1

2. resolved Sep 21, 2026, 06:26 PM UTC

   The FX Notes application is now available. If you continue to experience log on issues, please contact Central 1 Support. Central 1 - [email protected] - 1.888.889.7878, press 1

Read the full incident report →

Started Sep 10, 2026, 11:23 PM UTC· resolved Sep 10, 2026, 11:33 PM UTC

1. resolved Sep 10, 2026, 11:23 PM UTC

   Please be advised, there was a service outage on Interac e-Transfer 3.4 from 3:56 to 4:06 pm PT (6:56 pm to 7:06 pm ET). Your customers may have seen a timeout or error during this time when trying to send or manually receive e-Transfers. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

2. postmortem Oct 13, 2026, 05:04 PM UTC

   **Postmortem: INC227360 – Interac e-Transfer 3.4 Service Outage** On September 10, after successfully implementing the RTR Settlement & Reconciliation solution, Central 1 initiated a planned activity to load historical data required for reporting. During this activity, an issue interrupted Interac e-Transfer 3.4 send and receive services between 3:56 p.m. and 4:06 p.m. PT \(6:56 p.m. and 7:06 p.m. ET\). **Point of Failure:** During the data load activity, an unexpected issue impacted production transaction processing, temporarily interrupting Interac e-Transfer 3.4 send and receive services. The disruption lasted approximately 10 minutes. Interac e-Transfer 3.5 services were not affected. The team restored service by stopping the data load activity and returning the environment to normal operation. Following recovery, the remaining historical data load work was reassessed and completed using a revised approach designed to minimize operational risk. Central 1 has reviewed the incident and implemented additional controls to strengthen the management and execution of future data migration activities and further reduce the risk of service disruption. **Corrective Actions \(PRB011767\)** **Completed** * Reviewed and enhanced the data replication process to ensure future activities are performed during approved maintenance windows. * Reviewed change management procedures to strengthen risk assessment and implementation oversight. * Updated review procedures to require Database Administration \(DBA\) involvement for large-scale data extraction, migration, and replication activities. * Redesigned the historical data replication process to reduce operational risk. **Planned \(Q4 2026\)** * Improve early engagement between Project and Technical teams to enhance planning, risk identification, and execution readiness for future initiatives. We sincerely apologize for the disruption and the impact this incident may have had on your operations. We appreciate your patience and understanding while we restored service, and we thank you for your continued partnership. Liz Ackroyd Manager, Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337

Read the full incident report →

Started Sep 01, 2026, 05:35 PM UTC· resolved Sep 01, 2026, 06:31 PM UTC

1. investigating Sep 01, 2026, 05:35 PM UTC

   Central 1 has identified that multiple credit unions are missing their ORPI cheque return reports this morning dated for 01/09/2026. Our technical team is currently investigating the issue. At this time, we have confirmed that the reports are not available via SFTP for affected clients. We will provide our next update by 12:00 p.m. PT (3:00 p.m. ET), or sooner if additional information becomes available. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

2. resolved Sep 01, 2026, 06:31 PM UTC

   Central 1 has resolved the issue affecting ORPI cheque return reports. The impacted ORPI files have been regenerated and successfully transferred for delivery. Clients should note that the affected cheque return records will be included in tomorrow's MERG file. If you continue to experience issues accessing your ORPI report or believe records are missing after tomorrow's MERG file is received, please contact Central 1 Support with examples for investigation. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

Read the full incident report →

Started Aug 28, 2026, 08:29 PM UTC· resolved Sep 21, 2026, 03:24 PM UTC

1. investigating Aug 28, 2026, 08:29 PM UTC

   Central 1 is aware of an Interac issue they are having with the Scheduled and Recurring e-Transfers. Currently some e-Transfers are not being processed on the due date. Customers requiring immediate fund transfers may send an immediate e-Transfer instead of a scheduled or recurring e-Transfer at this time. We have reached out to Interac support to investigate and will provide updates as we receive them. Central 1 - [email protected] - 1.888.889.7878 Option 1

2. investigating Sep 01, 2026, 09:36 PM UTC

   Central 1 continues to work with Interac to investigate an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R). Our review of historical processing volumes indicates that the number of impacted Scheduled and Recurring e-Transfers is relatively low, and the majority continue to be processed successfully. The issue may affect any customer using Scheduled or Recurring e-Transfers. Scheduled and Recurring e-Transfers are managed by Interac within a separate system, and Central 1 is unable to directly view or identify pending S&R transactions. We continue to engage Interac for updates and will provide our next status update on Thursday, September 3 at 12:00 p.m. PT (3:00 p.m. ET). Central 1 - [email protected] - 1.888.889.7878 Option 1

3. identified Sep 03, 2026, 11:21 PM UTC

   Central 1 continues to work with Interac to investigate an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R). Interac has identified a potential fix and is currently conducting testing and validation activities to confirm the root cause and effectiveness of the solution. Subject to successful testing and approval, Interac is currently targeting deployment of the fix as part of its September 20 production release. The issue remains intermittent and may affect some customers using Scheduled or Recurring e-Transfers. Customers requiring immediate fund transfers should send an immediate e-Transfer instead of a Scheduled or Recurring e-Transfer until this issue has been resolved. We continue to work closely with Interac and will provide our next update, including any changes to the expected release timeline, on Wednesday, September 9. Central 1 - [email protected] - 1.888.889.7878 Option 1

4. identified Sep 09, 2026, 10:31 PM UTC

   Central 1 continues to work with Interac on an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R). Interac's fix remains targeted for September 20, 2026, and testing is currently underway. The majority of Scheduled and Recurring e-Transfers continue to process successfully. Customers requiring immediate fund transfers should use a standard e-Transfer until the issue is resolved. Our next update will be provided by Wednesday, September 16 or sooner if new information becomes available. Central 1 - [email protected] - 1.888.889.7878 Option 1

5. resolved Sep 21, 2026, 03:24 PM UTC

   Interac has confirmed that the fix for this incident was released on Sunday, September 20, 2026. If you have any questions related to this incident, please contact Central 1 Support. Central 1 - [email protected] - 1.888.889.7878 Option 1

Read the full incident report →

Started Aug 13, 2026, 06:51 PM UTC· resolved Aug 17, 2026, 11:30 PM UTC

1. identified Aug 13, 2026, 06:51 PM UTC

   Central 1 is aware of an issue that has temporarily caused User Management Security Officers and Business User Admins to lose their access privileges today. Our team has identified the root cause and is actively working to restore the affected permissions. At this time, regular users are not affected and can continue using the system as usual. If you require any urgent user access changes while Security Officer privileges are unavailable, please get in touch with our Support team, and we will work with you to address those requests. We will provide our next update by 10:00 a.m. PT (1 p.m. ET) on August 14, 2026, or sooner if the issue is resolved. We apologize for any inconvenience and appreciate your patience as we work to resolve this issue. Central 1 - [email protected] - 1.888.889.7878 Option 1

2. identified Aug 14, 2026, 03:45 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Aug 14, 2026, 03:47 PM UTC

   As a follow-up to our previous notification, we would like to provide additional clarification regarding this incident. The issue is related to a delay in a background synchronization process. While Security Officers and MemberDirect Business User Administrators can continue to grant application permissions through User Management (UM) or MDB User Admin (BUA), and those changes appear to complete successfully, the corresponding permission updates are not currently being synchronized as expected. This delay does not affect: * Password changes, which take effect immediately. * Changes to a user's Active/Inactive status, which also take effect immediately. We anticipate the synchronization process will catch up by the end of the weekend. Once synchronization has been fully restored, any permissions granted yesterday, today, or over the weekend will be applied and reflected in users' accounts. We will provide our next update by 10:00 a.m. PT (1 p.m. ET) on August 17, 2026, or sooner if the issue is resolved. We apologize for any inconvenience this may cause and appreciate your patience.

4. identified Aug 17, 2026, 04:45 PM UTC

   We are actively working to finalize the planned synching updates for the User Manager (UM) and Business User Administrator (BUA) tool. While progress is being made, the implementation is taking longer than expected. We sincerely apologize for any inconvenience this may cause and appreciate your understanding. If you have an urgent request, please reach out to Support for immediate assistance. We will provide our next update by 10:00 a.m. PT (1 p.m. ET) on August 18, 2026, or sooner if the issue is resolved. Central 1 - [email protected] - 1.888.889.7878 Option 1

5. resolved Aug 17, 2026, 11:30 PM UTC

   After thorough investigation and remediation efforts, this incident has been resolved. User Management (UM) Security Officer and Business User Administrator (BUA) permissions have been fully restored, and the synchronization process is now operating as expected. Any pending permission updates have been successfully processed and reflected in user accounts. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience and understanding while we worked to restore service.

Read the full incident report →

Started Aug 11, 2026, 04:56 PM UTC· resolved Aug 11, 2026, 05:22 PM UTC

1. investigating Aug 11, 2026, 04:56 PM UTC

   We are currently investigating a potential issue impacting Central 1’s Remote Deposit Capture (RDC) error or mobile deposits. At approximately 9:30 a.m. PT (12:30 p.m. ET) we observed an increase in RDC errors. At this time, we are working to validate scope and confirm whether customer impact is present. We will provide an update within 1 hour or sooner as more information becomes available. Central 1 - [email protected] - 1.888.889.7878 Option 1

2. resolved Aug 11, 2026, 05:22 PM UTC

   Central 1 has confirmed that a service interruption impacted Remote Deposit Capture (RDC) between 2:05 a.m. PT and 10:13 a.m. PT (5:05 a.m. ET and 1:13 p.m. ET) on August 11, 2026. The disruption lasted approximately 8 hours and 8 minutes. During this period, members may have experienced errors when attempting to submit mobile cheque deposits through participating financial institution applications utilizing Central 1's RDC service. Service was fully restored at 10:13 a.m. PT (1:13 p.m. ET), and we continue to monitor the platform to ensure ongoing stability. A root cause analysis is being prioritized and will be completed as part of our standard incident management process.

3. postmortem Aug 24, 2026, 02:21 PM UTC

   **Postmortem: INC226099 – Mobile Remote Deposit Capture \(mRDC\) Service Interruption** On August 11, 2026, between 2:05 a.m. and 10:13 a.m. PT \(5:05 a.m. and 1:13 p.m. ET\), the Mobile Remote Deposit Capture \(mRDC\) service experienced an interruption, preventing members from successfully submitting mobile cheque deposits. During this period, deposit requests could not be processed due to a loss of connectivity between the mRDC application and supporting data services. **Point of Failure** As part of a database governance and standardization initiative, database service account permissions were updated to align with enterprise standards. This change exposed an undocumented user privilege dependency within the mRDC environment where the application access relied upon a legacy access permission for a service account. **Resolution** The team restored service by re-establishing the required database permissions and restarting the affected application, restoring connectivity and allowing deposit processing to resume. Once service was recovered, queued transactions were processed, and normal member activity resumed. While these actions resolved the immediate service interruption, the incident highlighted opportunities to strengthen platform resiliency and change validation processes. Central 1 has initiated a series of corrective measures to reduce dependency on legacy configurations, improve monitoring and alerting capabilities, strengthen change controls, and enable faster operational recovery should a similar event occur in the future. **Corrective Actions \(PRB011762\)** * Document and enhance the database user governance change process, including validation and testing requirements. – In Progress * Review remaining databases for legacy access dependencies and remediate where required. – In Progress * Implement post-change reviews of SQL Server logs to identify access and authentication issues immediately following user governance changes. – Complete * Enhance monitoring and alerting for RDC transaction failures and abnormal transaction patterns. – In Progress * Require all database user governance changes to be executed through the formal Change Management process. – Complete * Implement monitoring for RDC deposit confirmation transactions. – In Progress We sincerely apologize for the disruption and the impact this incident had on your members and operations. We appreciate your patience and understanding while services were restored and thank you for your continued partnership Liz Ackroyd Manager, Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337

Read the full incident report →

Started Aug 10, 2026, 10:38 PM UTC· resolved Aug 13, 2026, 07:29 PM UTC

1. identified Aug 10, 2026, 10:38 PM UTC

   *** This notice is for credit unions who have Everlink as their switch provider. *** Please be advised that Everlink has suspended processing of new INT network POS and SCD traces. This includes trace follow-up requests for the INT network, due to a technical issue within the Everlink processing stream. The issue has been escalated with Everlink and their settlement agent, PPJV, and we are actively working with them toward resolution. There is no impact to POS and SCD trace processing for other networks, including ME2, ME3, and CI3. Further updates will be provided as more information becomes available. Central 1 - [email protected] - 1.888.889.7878 Option 1

2. resolved Aug 13, 2026, 07:29 PM UTC

   *** This notice is for credit unions who have Everlink as their switch provider. *** Everlink has resolved the issue affecting INT network POS and SCD trace processing, and credit unions may now resume submitting new INT network POS and SCD trace requests. Follow-up requests for previously submitted INT network traces will be completed after September 10, once PPJV has cleared the backlog of new trace requests. Thank you for your patience while this issue was being addressed. Central 1 - [email protected] - 1.888.889.7878 Option 1

Read the full incident report →

Started Jul 31, 2026, 04:11 PM UTC· resolved Jul 31, 2026, 05:44 PM UTC

1. investigating Jul 31, 2026, 04:11 PM UTC

   The Foreign Exchange (FX Trader) via the Treasury Connect application is currently unavailable. Our technical team is investigating. Should you require an urgent trade, please contact our Treasury Department at [email protected] or by calling 1-800-661-6813 x 8487. An update will be sent out by 10:30 a.m. PT (1:30 p.m. ET). Central 1 - [email protected] - 1.888.889.7878, press 1

2. resolved Jul 31, 2026, 05:44 PM UTC

   The Foreign Exchange (FX Trader) application is now available. Central 1 - [email protected] - 1.888.889.7878, press 1

Read the full incident report →

Started Jul 31, 2026, 01:00 PM UTC· resolved Jul 31, 2026, 03:08 PM UTC

1. investigating Jul 31, 2026, 01:00 PM UTC

   Please note that we are currently experiencing delays in processing outgoing wire transfers. Once a wire has been approved, its status may remain in a pending state in the outgoing queue. We are actively working with all relevant teams to identify and resolve the issue as quickly as possible. An update will be provided by 9:30 a.m. PT (12:30 p.m. ET) or sooner if additional information becomes available. Support 888 889 7878 Option 1 [email protected]

2. resolved Jul 31, 2026, 03:08 PM UTC

   Central 1 performed an emergency reset of the wire processing queue, which resolved the incident. Outgoing wire transactions are now processing successfully, and any incoming wires that were delayed as a result of this issue are now appearing correctly in the appropriate queues. The issue has been mitigated, and wire processing has returned to normal operation and we will continue to monitor the services. Support 888 889 7878 Option 1 [email protected]

3. postmortem Aug 11, 2026, 07:32 PM UTC

   **Postmortem: INC225671 – Delayed Incoming and Outgoing Wire Transfers** On July 31, 2026, between 4:41 a.m. and 7:58 a.m. PT \(7:41 a.m. and 10:58 a.m. ET\), Central 1 experienced a disruption that delayed the processing of both incoming and outgoing wire transfers. During this period, outgoing wires were unable to progress through processing, and incoming wires were not delivered to downstream systems as expected. Following an investigation across the wire-processing environment, the issue was traced to an application responsible for facilitating communication between core processing systems. After a network connectivity interruption, the application was unable to resume processing messages, resulting in a backlog and delayed transaction flow. **Point of Failure** On July 31, 2026, a network connectivity interruption impacted communication between components supporting wire processing. While the affected systems remained available, one of the applications failed to re-establish communication after the interruption, preventing transactions from progressing through the normal processing flow. **Resolution** Service was restored by restarting the affected application, which successfully re-established connectivity and resumed normal transaction processing. Once connectivity was restored, queued transactions were processed, and wire services returned to normal operation. While the restart resolved the immediate processing interruption, the underlying cause of the connectivity loss remains under investigation. As a result, Central 1 has initiated a series of corrective actions focused on improving application resiliency, enhancing transaction-flow and queue monitoring, strengthening alerting and escalation processes, and enabling faster operational recovery should a similar condition occur in the future. **Corrective Actions \(PRB011760\)** * Implement application resiliency improvements to automatically recover from connectivity interruptions and reduce the risk of similar delays. **In Progress** * Validate PagerDuty routing, team assignments, and escalation processes to ensure rapid engagement and clear ownership during major incidents. **In Progress** * Provide an operational recovery script and training to the PS Software team and Computer Operators to ensure approved recovery procedures are executed consistently when known wire-processing issues occur. **Complete** * Work with Fiserv to implement queue-depth monitoring to improve visibility into processing delays. **In Progress** * Enhance PSD/MTS transaction-flow monitoring to enable earlier detection of processing interruptions. **In Progress** * Assess and implement potential message-queue reconnection enhancements to improve system resilience. **In Progress** 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 and understanding while services were restored and thank you for your continued partnership. **Liz Ackroyd** Manager, Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337

Read the full incident report →

Started Jul 22, 2026, 04:23 PM UTC· resolved Jul 22, 2026, 04:23 PM UTC

1. resolved Jul 22, 2026, 04:23 PM UTC

   Please be advised that the deployment of Digital Banking Core Release 774 (CHG172867), previously scheduled for Wednesday July 22, 2026 at 1 a.m. PT (4 a.m. ET), did not occur as planned and has been delayed. The release is currently being rescheduled. We will provide an update with the new deployment date and time as soon as it has been confirmed. We apologize for any inconvenience this may cause and appreciate your patience and understanding. If you have any questions, please contact: Central 1 - [email protected] - 1.888.889.7878, option 2

Read the full incident report →

Started Jul 15, 2026, 09:20 PM UTC· resolved Jul 21, 2026, 10:20 PM UTC

1. monitoring Jul 15, 2026, 09:20 PM UTC

   Due to a file transmission issue, EDI bill payments for July 10 to American Express (AMEX) have been delayed. We are actively working with AMEX and will advise once the payments have been processed. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at [email protected].

2. monitoring Jul 16, 2026, 10:19 PM UTC

   Central 1 continues to actively work with AMEX to resolve the issue as quickly as possible. We will provide another update once we have additional information. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at [email protected].

3. resolved Jul 21, 2026, 10:20 PM UTC

   Central 1 has resolved the issue with AMEX. All payments will be 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].

Read the full incident report →

Started Jul 14, 2026, 07:18 PM UTC· resolved Jul 15, 2026, 11:07 PM UTC

1. monitoring Jul 14, 2026, 07:18 PM UTC

   Due to a file transmission issue, EDI bill payments for July 11 to billers using TD Canada Trust (TD Bank) have been delayed. We are actively working with TD Bank and will advise once the payments have been processed. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at [email protected].

2. monitoring Jul 15, 2026, 09:17 PM UTC

   Central 1 continues to actively work with TD Bank to resolve the issue as quickly as possible. We will provide another update once we have additional information. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at [email protected].

3. resolved Jul 15, 2026, 11:07 PM UTC

   Central 1 has resolved the issue with TD Bank. All payments will be 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].

Read the full incident report →

Started Jul 14, 2026, 04:16 PM UTC· resolved Jul 14, 2026, 04:16 PM UTC

1. resolved Jul 14, 2026, 04:16 PM UTC

   Please be advised that the deployment of MDB, Forge Commercial, and CAS Online Release 527+528 (CHG170133), previously scheduled for Tuesday July 14, 2026 at 1 a.m. PT (4 a.m. ET), did not occur as planned and has been delayed. The release is currently being rescheduled. We will provide an update with the new deployment date and time as soon as it has been confirmed. We apologize for any inconvenience this may cause and appreciate your patience and understanding. If you have any questions, please contact: Central 1 - [email protected] - 1.888.889.7878, option 2

Read the full incident report →

Started Jul 08, 2026, 02:00 PM UTC· resolved Jul 08, 2026, 02:53 PM UTC

1. investigating Jul 08, 2026, 02:00 PM UTC

   Central 1 is aware that the OREC0707 file is delayed and not in the FTP directories. We are working on having the file available as soon as possible. An update will be provided by 9 am PT (12 pm ET). Central 1 - [email protected] - 1.888.889.7878, press 1

2. resolved Jul 08, 2026, 02:53 PM UTC

   The OREC0707 file is now available on the FTP server.

Read the full incident report →

Started Jul 06, 2026, 07:31 PM UTC· resolved Jul 07, 2026, 11:29 AM UTC

1. monitoring Jul 06, 2026, 07:31 PM UTC

   Central 1 has been advised by Payments Canada that TD Bank is experiencing system issues that are impacting their ability to post AFT credits to their client's accounts. No ETA has been provided at this time. We will provide another update at 2 pm PT (5 pm ET) or sooner if information is made available to us. Central 1 – [email protected] – 1.888.889.7878 (press 1)

2. monitoring Jul 06, 2026, 09:08 PM UTC

   Central 1 has received an update from Payments Canada that TD Bank is making progress with their internal system issues. The estimated time of resolution is 6:30 pm PT (9:30 pm ET). They expect to have all the transactions posted at that time. We will provide another update by 7 am PT (10 am ET) tomorrow, July 7, or sooner if we receive further information before then.

3. resolved Jul 07, 2026, 11:29 AM UTC

   Payments Canada has confirmed that TD has resolved its internal issue and that all impacted AFT payments have been successfully posted to the recipient accounts. Central 1 – [email protected] – 1.888.889.7878 (press 1)

Read the full incident report →