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.

June 2026
INC224203 -- Saved logins issue on v18.1 iOS Forge App
minor Source not attested
Last archived state: resolved
View archived record details
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 ma...
INC224124 - Cash ordering domination drop-down is blank
Source not attested
Last archived state: resolved
View archived record details
monitoring
RBC has implemented a fix for the cash ordering denomination drop-down issue. Some users have reported success in selecting denominations after closing all browser sessions and opening a new browser before placing their order. However, other users continue to experience issues with the application. If your order is urgent, please submit it using the ServiceNow Cash Ordering Form. We will provide our next update by 7:00 a.m. PT / 10:00 a.m. ET tomorrow. Central 1 - Support@central1.com - ...
identified
Organizations continue to experience issues with cash ordering. The drop-down menu remains blank, even when using a fresh browser during order placement. If your order is urgent, please submit it using the ServiceNow cash ordering form. Our supplier is currently investigating the issue, and we will provide an update by 1:00 p.m. PT \4:00 p.m. ET. Central 1 - Support@central1.com - 1.888.889.7878, press
identified
Credit unions have confirmed that the cash ordering domination drop-down remains blank even after using a fresh browser when placing an order. If your order is urgent, please use the ServiceNow cash ordering form. Our supplier is investigating, and we will have an update by 10 a.m. PT\1 p.m. ET. Central 1 - Support@central1.com - 1.888.889.7878, press
NC224124 - Cash ordering domination drop-down is blank
Source not attested
Last archived state: resolved
View archived record details
investigating
Central 1 is aware that the cash ordering domination drop-down is blank in the application when placing an order. If your order is urgent, please use the ServiceNow cash ordering form. Our supplier is investigating, and we will have an update by 10 a.m. PT\1 p.m. ET. Central 1 - Support@central1.com - 1.888.889.7878, press
INC223958 - RESOLVED Delayed bill payments for Manitoba Hydro for June 9, 12, 13, 14 and 15
Source not attested
Last archived state: resolved
View archived record details
monitoring
Central 1 has been advised that Manitoba Hydro experienced internal technical issues which have resulted a delay in applying bill payments made on June 9, 12, 13, 14 and 15. The issue is expected to be resolved today and the payments will be applied to the clients' accounts tomorrow. Customers can reach out to Manitoba Hydro's Customer Engagement Center at 204-480-5900. Central 1 is actively working with the biller and will provide another update once we have confirmation all bill payments ha...
Resolved - INC223892 - AIBC0624 report is not available
Source not attested
Last archived state: resolved
View archived record details
identified
Central 1 is aware that the AIBC0624 file is currently unavailable on the FTP server. This issue does not impact Ontario credit unions, as the AIOC report remains available. Our technical support team is actively investigating. In the meantime, the same information can be accessed via the CDJ report within the DAIL file. We will provide an update by 10:00 a.m. PT (1:00 p.m. ET). Central 1 - Support@central1.com - 1.888.889.7878, press 1
INC223539 - Missing Unqualified Items - June 16, 2026
Source not attested
Last archived state: resolved
View archived record details
identified
We have identified the issue causing the delay in delivery of the June 16 Unqualified items. We are working towards getting the items moved over to FTP directories as soon as possible. Another update will be provided by 1:30 pm PT (4:30 pm ET). Central 1 – support@central1.com – 1.888.889.7878 (press 1)
investigating
We are continuing to investigate this issue. An update will be provided by 12 pm PT (3 pm ET). Central 1 – support@central1.com – 1.888.889.7878 (press 1)
investigating
Some clients may be missing their Unqualified clearing items for June 16. We are actively investigating the matter. We will provide the next update by 11 am PT (2 pm ET) with the latest information. Central 1 – support@central1.com – 1.888.889.7878 (press 1)
INC222835: International Funds Transfers – Transaction Failures
minor Source not attested
Last archived state: resolved
View archived record details
investigating
All impacted payments have now been returned to members through the standard payments return process. We have made significant progress in our investigation and have successfully validated a fix in our test environments. The issue was related to a recent system update that caused a compatibility problem, resulting in transfers not being completed as expected. A change has been prepared to address this issue and is tentatively scheduled for tomorrow morning. Once the change is complete, Agi...
investigating
We continue to investigate the issue affecting International Transfers in Forge. To prevent further customer impact, Agility has disabled the production connection, ensuring that no additional payments are processed and require reversal. Customers attempting to access the feature will see a service unavailable message. Investigation efforts are ongoing in UAT and Development environments as teams work to identify the root cause and implement a resolution. We will provide further updates a...
investigating
We are currently investigating an issue affecting International Funds Transfers. Since Monday evening, transfer attempts have been failing. In impacted cases, funds are being debited from customer accounts, but the corresponding bill payment transfers are not being created. Debited funds will be returned through the standard payments return process. Our teams are actively working to identify the root cause and restore normal service. We will provide further updates as more information becom...
INC222764 – Delayed bill payments to BMO for May 29
Source not attested
Last archived state: resolved
View archived record details
monitoring
Due to a technical issue at the Bank of Montreal (BMO), EDI bill payments for May 29, to billers using BMO as their lead bank, were delayed. All payments, except for those for BC Hydro and Capital One Mastercard, were processed by BMO on June 2. Please note that EDI billers honour the original payment date when applying payments so there will be no impact to customer accounts. Payments for BC Hydro and Capital One Mastercard are still being investigated. We are following up with BMO and wil...
INC222639 – Outgoing and Incoming wires delay
Source not attested
Last archived state: resolved
View archived record details
monitoring
Wires have been processing with minimal delay since 8:07 a.m. PT (11:07 a.m. ET) and all pending wires have been processed. Central 1 is continuing to work with our provider to monitor to ensure wires stability. An update will be provided by 12:00 p.m. PT (3:00 p.m. ET). Central 1 - Support@central1.com - 1.888.889.7878, press 1
monitoring
Central 1 we observed a delay for incoming and outgoing wires moving in our system between 7:25 to 8:07 a.m. PT (10:25 to 11:07 a.m. ET). All wires submitted prior to 7:25 a.m. PT (10:25 am, ET) have processed as expected. Wires have resumed and Central 1 is working with our provider to ensure wires impacted during the outage are released. An update will be provided by 9:30 a.m. PT (12:30 p.m. ET). Central 1 - Support@central1.com - 1.888.889.7878, press 1
May 2026
INC222092: Remember Me and Biometric Login Information Disappearing
Source not attested
Last archived state: resolved
View archived record details
identified
We are proceeding with an urgent OIDC release tonight to address the “Remember Me” expiry issue affecting desktop and manual login on mobile. <a href="https://status.central1.com/incidents/7rl1c39tfk5g">CHG170934 – Urgent Digital Banking OIDC Release 1.0.62</a> Once the release is complete, OIDC will refresh the “Remember Me” cookie expiry at login. This resolves the issue where saved login information was not being extended on return visits. This applies to Desktop login and Ma...
identified
Update: Remember Me and Biometric Login Information Further to our previous communication, we would like to provide additional details on the issue affecting saved login information. Current Status • A fix for OIDC (desktop and manual login flows) is currently in development and is expected to be ready for testing shortly. • Once validated, this will be deployed via an urgent OIDC release. • An Android and iOS Mobile App update is also required to address the issue with biometric logi...
identified
We have identified an issue affecting Remember Me and Biometric login information in both Digital Banking OIDC and the Mobile App. Our investigation has determined that both OIDC and the Mobile App are not updating the expiry date on the “Remember Me” cookie. While this cookie is configured to expire in 10 years, recent changes in modern web browsers now limit the duration that such data can be retained to approximately 13 months (400 days). As a result, any longer durations are automati...