- Detected by Pingoru
- Jun 17, 2026, 04:20 PM UTC
- Resolved
- Jun 17, 2026, 07:34 PM UTC
- Duration
- 3h 14m
Affected: Payment Services
Timeline · 4 updates
-
investigating Jun 17, 2026, 04:20 PM UTC
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 – [email protected] – 1.888.889.7878 (press 1)
-
investigating Jun 17, 2026, 06:13 PM UTC
We are continuing to investigate this issue. An update will be provided by 12 pm PT (3 pm ET). Central 1 – [email protected] – 1.888.889.7878 (press 1)
-
identified Jun 17, 2026, 07:08 PM UTC
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 – [email protected] – 1.888.889.7878 (press 1)
-
resolved Jun 17, 2026, 07:34 PM UTC
The Unqualified clearing items for June 16 are now available on the FTP server.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 05:18 PM UTC
- Resolved
- Jun 16, 2026, 10:30 PM UTC
- Duration
- 11d 5h
Affected: Digital Banking ServicesIncident Alerting
Timeline · 4 updates
-
investigating Jun 05, 2026, 05:18 PM UTC
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 wire 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 becomes available. [email protected] - 1.888.889.7878 (option 2)
-
investigating Jun 10, 2026, 10:17 PM UTC
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 as more information becomes available. [email protected] - 1.888.889.7878 (option 2)
-
investigating Jun 15, 2026, 05:57 PM UTC
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, Agility will re-enable the production connection to restore service. We will continue to provide updates as we move toward resolution. [email protected] - 1.888.889.7878 (option 2)
-
resolved Jun 16, 2026, 10:30 PM UTC
Service for International Transfers in Forge has been restored and is now operating normally. The fix was successfully deployed, and Agility has re-enabled the production connection. All previously impacted payments were returned to members, and new transfers are now processing as expected. We will continue to monitor the service to ensure stability. Thank you for your patience. [email protected] - 1.888.889.7878 (option 2)
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 08:56 PM UTC
- Resolved
- Jun 03, 2026, 10:27 PM UTC
- Duration
- 1h 30m
Affected: Payment Services
Timeline · 2 updates
-
monitoring Jun 03, 2026, 08:56 PM UTC
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 will provide an update as soon as possible. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at [email protected].
-
resolved Jun 03, 2026, 10:27 PM UTC
Central 1 has resolved the issue with BMO. Payments for BC Hydro and Capital One Mastercard were processed today, June 3. All payments have been 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 →
- Detected by Pingoru
- Jun 01, 2026, 03:35 PM UTC
- Resolved
- Jun 01, 2026, 06:29 PM UTC
- Duration
- 2h 54m
Affected: Central 1 ServicesPayment ServicesTreasury Services
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 01:21 AM UTC
- Resolved
- May 22, 2026, 09:53 PM UTC
- Duration
- 20h 32m
Affected: Payment ServicesTreasury ServicesDigital Banking Services
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 08:54 PM UTC
- Resolved
- May 22, 2026, 03:37 PM UTC
- Duration
- 18h 42m
Affected: Digital Banking ServicesIncident Alerting
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 02:09 PM UTC
- Resolved
- May 21, 2026, 10:44 PM UTC
- Duration
- 2d 8h
Affected: Central 1 ServicesPayment ServicesTreasury ServicesDigital Banking Services
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 02:26 AM UTC
- Resolved
- May 19, 2026, 12:27 PM UTC
- Duration
- 10h
Affected: Central 1 ServicesPayment Services
Timeline · 2 updates
-
investigating May 19, 2026, 02:26 AM UTC
Central 1 is currently experiencing degraded performance affecting the Client Centre (https://clients.central1.com/). Some customers may encounter intermittent access issues when logging in or navigating the site. At this time, the issue appears to impact a subset of users, and retrying the action may result in successful access. Central 1 teams are actively investigating the issue and working to restore full service. We will continue to provide updates as more information becomes available. Central 1 Support - [email protected] - 1‑888‑889‑7878 (press 1)
-
resolved May 19, 2026, 12:27 PM UTC
Resolved - The issue affecting access to the Client Centre (https://clients.central1.com/) has been resolved, and full service has been restored. Central 1 will continue to monitor the environment to ensure ongoing stability. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- May 17, 2026, 11:50 AM UTC
- Resolved
- May 17, 2026, 02:08 PM UTC
- Duration
- 2h 18m
Affected: Payment Services
Timeline · 2 updates
-
identified May 17, 2026, 11:50 AM UTC
Central 1 is aware that PaymentStream Direct is not accessible and has initiated an immediate investigation. The user will receive an error message that the server is unavailable after entering the 2-step token code. Keeping you informed during this incident is important to us. We’ll share another update with you by 9:30 a.m. PT (12:30 a.m. ET) today, or as soon as we have significant developments to report. Central 1 - [email protected] - 1.888.889.7878, press 0
-
resolved May 17, 2026, 02:08 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 17, 2026, 11:49 AM UTC
- Resolved
- May 17, 2026, 11:43 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 17, 2026, 11:49 AM UTC
Central 1 is aware that PaymentStream Direct is not accessible and has initiated an immediate investigation. The user will receive an error message that the server is unavailable after entering the 2-step token code. Keeping you informed during this incident is important to us. We’ll share another update with you by 9:30 a.m. PT (12:30 a.m. ET) today, or as soon as we have significant developments to report. Central 1 - [email protected] - 1.888.889.7878, press 0
Read the full incident report →
- Detected by Pingoru
- May 09, 2026, 06:11 PM UTC
- Resolved
- May 09, 2026, 07:40 PM UTC
- Duration
- 1h 29m
Affected: Central 1 ServicesPayment ServicesTreasury ServicesDigital Banking Services
Timeline · 2 updates
-
investigating May 09, 2026, 06:11 PM UTC
Central 1 is currently experiencing degraded performance affecting the Client Centre (https://clients.central1.com/). Some customers may encounter intermittent access issues when logging in or navigating the site. At this time, the issue appears to impact a subset of users, and retrying the action may result in successful access. Central 1 teams are actively investigating the issue and working to restore full service. We will continue to provide updates as more information becomes available. Central 1 Support - [email protected] - 1‑888‑889‑7878 (press 1)
-
resolved May 09, 2026, 07:40 PM UTC
The issue affecting access to the Client Centre (https://clients.central1.com/) has been resolved, and full service has been restored. Earlier today, some customers experienced intermittent access issues. As an interim measure, a workaround was implemented at approximately 11:30 a.m. PT (2:30 p.m. ET), allowing impacted users to log in while teams continued investigating. The underlying point of failure has since been identified and corrected, and the Client Centre is now operating normally for all users. Central 1 will continue to monitor the environment closely to ensure ongoing stability. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 08:35 PM UTC
- Resolved
- May 08, 2026, 08:45 PM UTC
- Duration
- 1d
Affected: Digital Banking ServicesIncident Alerting
Timeline · 2 updates
-
monitoring May 07, 2026, 08:35 PM UTC
Please be advised that our 2SV text/voice vendor experienced a service degradation between 11:18 AM and 11:48 AM PST (2:18 PM–2:48 PM EST). Members were intermittently unable to log in to online banking. Members using email-based 2SV were not affected. The issue has been resolved. We are currently monitoring the situation. [email protected] - 1.888.889.7878
-
resolved May 08, 2026, 08:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 02:40 PM UTC
- Resolved
- May 05, 2026, 03:44 PM UTC
- Duration
- 1h 4m
Affected: Payment Services
Timeline · 4 updates
-
identified May 05, 2026, 02:40 PM UTC
Please be advised that Central 1 experienced a Client Centre (https://clients.central1.com/) outage today between 9:00 to 9:20 a.m. PT (12:00 to 12:20 p.m. ET). You may have experienced issues logging into Client Centre or Central 1 applications during that time. A postmortem will be provided within the next two weeks. Central 1 - [email protected] – 1.888.889.7878, press 1
-
identified May 05, 2026, 02:40 PM UTC
We are continuing to work on a fix for this issue.
-
identified May 05, 2026, 02:47 PM UTC
Central 1 has identified that some clients are missing the ORPI (CAD) and the ORUI (USD) online returns cheque processed items reports this morning for items returned in ORS yesterday, May 4, 2026. We will provide our next update by 9 a.m. PT (12 p.m. ET) after our technical team has further investigated. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)
-
resolved May 05, 2026, 03:44 PM UTC
The CAD and USD cheque returns were successfully processed yesterday; however, due to a technical issue, the corresponding reports were not generated. The returned items that would have appeared on this morning’s report will instead be included in tomorrow’s report (May 6). Central 1 Support – [email protected] | 1.888.889.7878 (press 1)
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 04:57 PM UTC
- Resolved
- May 07, 2026, 05:36 PM UTC
- Duration
- 3d
Affected: Central 1 ServicesPayment ServicesTreasury ServicesIncident Alerting
Timeline · 14 updates
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 04:36 PM UTC
- Resolved
- May 04, 2026, 04:36 PM UTC
- Duration
- —
Affected: Central 1 ServicesPayment ServicesTreasury ServicesDigital Banking ServicesIncident Alerting
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 08:18 PM UTC
- Resolved
- Apr 30, 2026, 08:18 PM UTC
- Duration
- —
Affected: Central 1 ServicesPayment ServicesTreasury ServicesDigital Banking ServicesIncident Alerting
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2026, 02:38 PM UTC
- Resolved
- Apr 27, 2026, 06:54 PM UTC
- Duration
- 4h 16m
Affected: Payment Services
Timeline · 2 updates
-
identified Apr 27, 2026, 02:38 PM UTC
Payments Canada has notified Central 1 that BNC (National Bank of Canada) did not send one of the two files in the morning exchange. The larger of the two AFT files was successfully received and processed. We will provide an update once we have received and processed the remaining BNC file. Central 1 – [email protected] – 1.888.889.7878, press 1
-
resolved Apr 27, 2026, 06:54 PM UTC
We have received this mornings missing AFT file from BNC. The 160 transactions missed in the file this morning will be included in this afternoon's AFT CR03/ON03. Central 1 – [email protected] – 1.888.889.7878, press 1
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2026, 06:28 PM UTC
- Resolved
- Apr 25, 2026, 06:28 PM UTC
- Duration
- —
Affected: Payment ServicesDigital Banking Services
Timeline · 1 update
-
resolved Apr 25, 2026, 06:28 PM UTC
Central 1 is aware that users were not seeing the OAS production login link on the Client Centre. The link for OAS has been restored. Central 1 - [email protected] - 1.888.889.7878, press 1
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 08:56 PM UTC
- Resolved
- Apr 23, 2026, 11:23 AM UTC
- Duration
- 14h 27m
Affected: Payment ServicesTreasury ServicesIncident Alerting
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 11:45 PM UTC
- Resolved
- Apr 20, 2026, 11:45 PM UTC
- Duration
- —
Affected: Central 1 ServicesPayment ServicesDigital Banking Services
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 12:15 PM UTC
- Resolved
- Apr 20, 2026, 02:49 PM UTC
- Duration
- 2h 33m
Affected: Central 1 ServicesPayment ServicesTreasury Services
Timeline · 5 updates
-
investigating Apr 20, 2026, 12:15 PM UTC
Central 1 is currently unable to send or receive CAD, USD, or FX wires. Wires can still be created and reviewed in PS-Wires. Central 1’s technical resources are actively working to restore full service. We will provide an update by 5:45 a.m. PT (8:45 a.m. ET). Central 1 – [email protected] - 1.888.889.7878, press 1
-
investigating Apr 20, 2026, 01:00 PM UTC
Central 1 continues to experience a technical issue preventing incoming and outgoing wires from being processed. Wires can be created and approved in PS-Wires. We have engaged our technical teams along with our 3rd party providers, Fiserv and IBM An update will be provided by 6:45 a.m. PT (9:45 a.m. ET) or sooner if the incident is resolved. Central 1 – [email protected] - 1.888.889.7878, press 1
-
identified Apr 20, 2026, 02:00 PM UTC
Central 1 continues to experience a technical issue preventing the processing of incoming and outgoing wires. Wires can be created and approved in PS-Wires. The technical issue has been identified, and we are waiting for our vendor to implement a fix to their system. The fix will be applied by 7:30 a.m. PT (10:30 a.m. ET). As soon as the wires are processed, we will send a confirmation via this channel. Central 1 – [email protected] - 1.888.889.7878, press 1
-
identified Apr 20, 2026, 02:32 PM UTC
Our vendor addressed their technical issue at 7:02 am PT (10 am ET), and after a server restart, service has recovered at 7:04 am PT (10:04 am ET). Inbound and Outbound wires are now processing. Wires in pending status could take an additional 30 minutes to process. We continue to monitor the system and will send an update on system performance within the next hour. Central 1 – [email protected] - 1.888.889.7878, press 1
-
resolved Apr 20, 2026, 02:49 PM UTC
After further monitoring of the wire system, we can confirm that both incoming and outgoing wires are now processing. Central 1 – [email protected] - 1.888.889.7878, press 1
Read the full incident report →
- Detected by Pingoru
- Apr 19, 2026, 07:04 PM UTC
- Resolved
- Apr 19, 2026, 07:47 PM UTC
- Duration
- 42m
Affected: Payment ServicesIncident Alerting
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 07:28 PM UTC
- Resolved
- Apr 29, 2026, 01:26 PM UTC
- Duration
- 12d 17h
Affected: Digital Banking Services
Timeline · 7 updates
-
investigating Apr 16, 2026, 07:28 PM UTC
Please be advise that International transfer services are currently unavailable in online banking. We are conducting a thorough analysis of the systems involved and working towards resolving the issue. We will provide an update on or before Friday April 17, 2 p.m. PT / 5 p.m. ET. [email protected] - 1.888.889.7878, option 2
-
investigating Apr 17, 2026, 09:24 PM UTC
We are continuing to investigate the root cause of the international transfer service interruption. Our technical teams remain focused on the analysis and resolution process. We will provide the next update on or before Monday, April 20, by 2 p.m. PT / 5 p.m. ET.
-
investigating Apr 21, 2026, 06:17 PM UTC
We are continuing to investigate the root cause of the international transfer service interruption. Our technical teams remain focused on the analysis and resolution process. We will provide the next update on or before Tuesday, April 21, by 2 p.m. PT / 5 p.m. ET.
-
investigating Apr 24, 2026, 12:33 AM UTC
We believe we have identified the root cause of the International Transfer Service interruption. A fix has been applied in our lower environments and is currently undergoing testing. Our technical teams are closely monitoring results as we progress toward resolution. We will provide the next update on or before Monday, April 27, by 2 p.m. PT / 5 p.m. ET [email protected] - 1.888.889.7878, option 2
-
investigating Apr 27, 2026, 10:43 PM UTC
Our teams continue to validate the fix identified for the international transfer service interruption. We are tentatively targeting a resolution later this week, pending successful testing. We will provide the next update tomorrow, on or before 2 p.m. PT / 5 p.m. ET. [email protected] - 1.888.889.7878, option 2
-
investigating Apr 28, 2026, 08:45 PM UTC
Please be advised that a fix will be deployed with Urgent Digital Banking Core Release 768 (CHG170247) The release has been scheduled for Wednesday April 29, 2026 at 1 a.m. PT (4 a.m. ET). [email protected] - 1.888.889.7878
-
resolved Apr 29, 2026, 01:26 PM UTC
Please be advised that the urgent release is deployed and International Transfer is available in online banking.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 06:02 PM UTC
- Resolved
- Apr 15, 2026, 08:27 PM UTC
- Duration
- 2h 24m
Affected: Digital Banking ServicesIncident Alerting
Timeline · 3 updates
-
investigating Apr 15, 2026, 06:02 PM UTC
Please be advised that certain TeamSite components, including the Find a Branch/ATM tool, are experiencing inconsistent behaviour. Our internal platform team and OpenText are conducting an immediate investigation and are working to resolve the issue as quickly as possible. [email protected] - 1.888.889.7878, option 2
-
investigating Apr 15, 2026, 06:41 PM UTC
We are continuing to investigate this issue.
-
resolved Apr 15, 2026, 08:27 PM UTC
Please be advised that the reported performance issues have been resolved. The fix involved applying a necessary certificate to the environment. Following diligent work by the OpenText team, all services are now fully operational.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 05:30 PM UTC
- Resolved
- Apr 14, 2026, 06:16 PM UTC
- Duration
- 45m
Affected: Digital Banking Services
Timeline · 3 updates
Read the full incident report →