Central 1 Status

Resolved: 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

Resolved: 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.

Monitoring: 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

Identified: 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

Resolved: 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

Resolved: 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

Investigating: Our Development and Support teams continue to actively investigate reports of saved login credentials unexpectedly being cleared within the iOS Forge App. This remains a high-priority investigation, and we continue to devote resources toward identifying the underlying cause.

As part of our ongoing troubleshooting efforts, we may have identified an instance where the issue was reproduced by a staff member using a debug version of the production iOS application. While this is an encouraging development, the investigation is still in progress and additional analysis is required.

We continue to encourage users testing the debug version of the iOS application to report any occurrences of this issue and provide as much detail as possible to assist with our investigation.

We understand the impact this issue has on affected users and appreciate your continued patience and cooperation. Please be assured that the investigation remains active and ongoing, and we will provide further updates as soon as significant new information becomes available.

Thank you for your continued partnership as we work toward a resolution.

[email protected] 1.888.889.7878 (option 2)

Investigating: Please be assured that we continue to treat this as a priority investigation and remain actively engaged with our Development team. Over the past several weeks, we've dedicated significant effort to reproducing the behavior internally and identifying a reliable pattern that would help us isolate the root cause.

Unfortunately, despite extensive testing, we have not yet been able to replicate the issue in our own environments. We've also worked with a small number of affected clients by providing debug versions of the iOS application to capture additional diagnostic information during reproduction attempts; however, these efforts have not yet produced any conclusive findings. While we do not have a meaningful update on the root cause at this time, the investigation remains active and ongoing. We understand the impact this issue has on your users and appreciate your patience as we continue working to gather the information necessary to move the investigation forward.

In the meantime, we encourage affected staff members to continue testing with the debug iOS application where possible. For impacted clients who have not yet received the debug version and would like to assist with troubleshooting, please let us know and we would be happy to provide it.

Should the issue occur again, any details surrounding the event would be extremely helpful to our investigation. In particular, we would appreciate information regarding the actions performed leading up to the login being cleared, the timestamp, the device type and model, the operating system version (iOS), and any screenshots or screen recordings that may help us better understand the circumstances under which the issue occurred.

We remain committed to resolving this issue and will provide further updates as soon as we have any significant developments to share. Thank you for your continued patience and understanding.

[email protected] - 1.888.889.7878 (option 2)

Investigating: We continue to investigate an issue affecting some members using the Forge App on iOS devices, where saved login information may not be retained as expected.

Through our investigation, we have identified a valid workaround that allows saved login functionality to continue working as designed. Members should ensure that Biometric Login (Face ID or Touch ID) is enabled within the Forge App. We have observed that when Biometric Login is disabled, saved login information may be removed, either immediately or after a period of time.

While the workaround has proven effective, our team continues to investigate the underlying cause. We have experienced challenges consistently reproducing the issue within our internal testing environments, which has extended the time required to identify the root cause and implement a permanent fix.

Our team remains actively engaged in the investigation and will provide additional updates as more information becomes available.

[email protected] - 1.888.889.7878 (option 2)

Investigating: We are currently investigating an issue affecting some users on iOS devices where saved login information is not being retained as expected on the v18.1 Forge App.

Some members reported that the issue was resolved after upgrading their device to iOS 26.5 operating system. While we have not yet confirmed this as a universal solution, members experiencing this issue may wish to ensure their device is running the latest available version of iOS.

Members can continue to access the service by manually entering their card number and password if their saved login is unavailable.

Our team is actively investigating the issue and working to determine the root cause. Additional updates will be provided as more information becomes available.

We apologize for any inconvenience and appreciate your patience while we work toward a resolution.

[email protected] - 1.888.889.7878 (option 2)

Resolved: 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.

Monitoring: 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

Identified: 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

Resolved: 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

Investigating: Our Development and Support teams continue to actively investigate reports of saved login credentials unexpectedly being cleared within the iOS Forge App. This remains a high-priority investigation, and we continue to devote resources toward identifying the underlying cause.

As part of our ongoing troubleshooting efforts, we may have identified an instance where the issue was reproduced by a staff member using a debug version of the production iOS application. While this is an encouraging development, the investigation is still in progress and additional analysis is required.

We continue to encourage users testing the debug version of the iOS application to report any occurrences of this issue and provide as much detail as possible to assist with our investigation.

We understand the impact this issue has on affected users and appreciate your continued patience and cooperation. Please be assured that the investigation remains active and ongoing, and we will provide further updates as soon as significant new information becomes available.

Thank you for your continued partnership as we work toward a resolution.

[email protected] 1.888.889.7878 (option 2)

Investigating: Please be assured that we continue to treat this as a priority investigation and remain actively engaged with our Development team. Over the past several weeks, we've dedicated significant effort to reproducing the behavior internally and identifying a reliable pattern that would help us isolate the root cause.

Unfortunately, despite extensive testing, we have not yet been able to replicate the issue in our own environments. We've also worked with a small number of affected clients by providing debug versions of the iOS application to capture additional diagnostic information during reproduction attempts; however, these efforts have not yet produced any conclusive findings. While we do not have a meaningful update on the root cause at this time, the investigation remains active and ongoing. We understand the impact this issue has on your users and appreciate your patience as we continue working to gather the information necessary to move the investigation forward.

In the meantime, we encourage affected staff members to continue testing with the debug iOS application where possible. For impacted clients who have not yet received the debug version and would like to assist with troubleshooting, please let us know and we would be happy to provide it.

Should the issue occur again, any details surrounding the event would be extremely helpful to our investigation. In particular, we would appreciate information regarding the actions performed leading up to the login being cleared, the timestamp, the device type and model, the operating system version (iOS), and any screenshots or screen recordings that may help us better understand the circumstances under which the issue occurred.

We remain committed to resolving this issue and will provide further updates as soon as we have any significant developments to share. Thank you for your continued patience and understanding.

[email protected] - 1.888.889.7878 (option 2)

Investigating: We continue to investigate an issue affecting some members using the Forge App on iOS devices, where saved login information may not be retained as expected.

Through our investigation, we have identified a valid workaround that allows saved login functionality to continue working as designed. Members should ensure that Biometric Login (Face ID or Touch ID) is enabled within the Forge App. We have observed that when Biometric Login is disabled, saved login information may be removed, either immediately or after a period of time.

While the workaround has proven effective, our team continues to investigate the underlying cause. We have experienced challenges consistently reproducing the issue within our internal testing environments, which has extended the time required to identify the root cause and implement a permanent fix.

Our team remains actively engaged in the investigation and will provide additional updates as more information becomes available.

[email protected] - 1.888.889.7878 (option 2)

Investigating: We are currently investigating an issue affecting some users on iOS devices where saved login information is not being retained as expected on the v18.1 Forge App.

Some members reported that the issue was resolved after upgrading their device to iOS 26.5 operating system. While we have not yet confirmed this as a universal solution, members experiencing this issue may wish to ensure their device is running the latest available version of iOS.

Members can continue to access the service by manually entering their card number and password if their saved login is unavailable.

Our team is actively investigating the issue and working to determine the root cause. Additional updates will be provided as more information becomes available.

We apologize for any inconvenience and appreciate your patience while we work toward a resolution.

[email protected] - 1.888.889.7878 (option 2)