New Multi-region uptime checks and custom-domain status pages

Central 1 Outage History

Daily provider-status observations and published incident history for Central 1.

Operational

Central 1 is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Central 1 for future changes.

100% of 28 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

August 2026
INC226796 - Scheduled and Recurring e-Transfers Not Processing on Due Date
minor Observed active window 570h 55m

View incident details and source

Started:

Payment Services Digital Banking Services
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 - Support@central1.com - 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 - Support@central1.com - 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 - Support@central1.com - 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 - Support@central1.com - 1.888.889.7878 Option 1
June 2026
INC224203 -- Saved logins issue on v18.1 iOS Forge App
minor

View incident details and source

Started:

Digital Banking Services Incident Alerting
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. DigitalBanking_Support@Central1.com 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. DigitalBanking_Support@Central1.com - 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. DigitalBanking_Support@Central1.com - 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. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

Legacy Incident Archive

40 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
INC226167 - UM Security Officer and BUA admins updates to users temporarily unavailable
Source not attested
Last archived state: resolved
View archived record details
Payment Services Treasury Services Digital Banking Services
identified
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 i...
identified
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 expect...
identified
We are continuing to work on a fix for this issue.
identified
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 wi...
INC226099 - Potential Issue Impacting Remote Deposit Capture (RDC)
Source not attested
Last archived state: resolved
View archived record details
investigating
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 - Support@central1.com - 1.888.889.7878 Option 1
INC226073 - Everlink POS and SCD Trace Processing Delay
Source not attested
Last archived state: resolved
View archived record details
identified
*** 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 ...
July 2026
INC225674 – Foreign Exchange (FX Trader) is currently down
Source not attested
Last archived state: resolved
View archived record details
investigating
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 treasury@central1.com 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 - Support@central1.com - 1.888.889.7878, press 1
INC225671: Outgoing Wires Delays
Source not attested
Last archived state: resolved
View archived record details
investigating
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 support@central1.com
INC224893 - Delayed AMEX Bill Payments for July 10
Source not attested
Last archived state: resolved
View archived record details
monitoring
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 bptrace@central1.com.
monitoring
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 bptrace@central1.com.
INC224781 – Delayed Bill Payments to TD Bank for July 11
Source not attested
Last archived state: resolved
View archived record details
monitoring
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 bptrace@central1.com.
monitoring
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 bptrace@central1.com.
INC224528 - OREC0707 File Delayed
Source not attested
Last archived state: resolved
View archived record details
investigating
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 - Support@central1.com - 1.888.889.7878, press 1
INC224453 - Delayed AFT Posting at TD Bank
Source not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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 – support@central1.com – 1.888.889.7878 (press 1)
INC224352 - EDI Bill Payment files from BNS dated June 26 and June 29 not processed
Source not attested
Last archived state: resolved
View archived record details
identified
Central 1 has been advised that the EDI Bill Payment files from BNS, dated June 26 and June 29, have not been processed. Central 1 is actively working with BNS to have the missing files resent and processed as quickly as possible. We will provide our next update at 2:00 p.m. PT (5:00 p.m. ET). Central 1 - Support@central1.com - 1.888.889.7878, press 1
Get alerts for Central 1 Subscribe to the provider incident feed Browse all services