Central 1 Status

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

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

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

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

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

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

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

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

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

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

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

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

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)