Is Central 1 down?
Last checked 7m ago2 active incidents: CHG171693 – Central 1 Wires Vendor Disaster Recovery Test, INC222835: International Funds Transfers – Transaction Fail…
Central 1 is reporting degraded performance right now (last checked 7m ago). Services are up but slower or partially failing.
Real-time Central 1 status, recent outages, and incident history — pulled directly from Central 1's official status page at https://status.central1.com every 5 minutes. Pingoru tracks 5 Central 1 services and has captured 49 incidents in the last 90 days (89.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Central 1 reports a new incident — free for 5 monitors, no credit card.
Active incident 1
- Digital Banking ServicesIncident Alerting
Timeline · 2 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)
Latest: We continue to investigate the issue affecting International Transfers in Forge. To prevent further customer impact, Agility has disabled the production connection, ensuring that n…
-
Recent outages & incidents
Past 90 days- 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].
Latest: 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 acc…
-
- Central 1 ServicesPayment ServicesTreasury Services
Timeline · 4 updates
- monitoring · Jun 01, 2026, 03:35 PM UTC
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 - [email protected] - 1.888.889.7878, press 1
- monitoring · Jun 01, 2026, 04:35 PM UTC
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 - [email protected] - 1.888.889.7878, press 1
- resolved · Jun 01, 2026, 06:29 PM UTC
Wire processing has remained stable since 8:07 a.m. PT (11:07 a.m. ET), and all pending wires have been successfully processed. Central 1 has not observed any further delays and will continue to monitor closely with our provider to ensure ongoing stability. At this time, the incident is considered resolved. If you continue to experience any issues, please contact our Support team. Central 1 - [email protected] - 1.888.889.7878, press 1
- postmortem · Jun 05, 2026, 05:10 PM UTC
**Postmortem: INC222639 – Outgoing and Incoming Wire Transfers Delayed** On June 1, 2026, between 7:25 and 10:55 a.m. PT \(10:25 and 1:55 a.m. ET\), a Central 1 third-party tool used for wire reviews intermittently displayed an error to Central 1 users. Despite the error messages, wire transfers continued to process in the background. Some transactions had to be manually restarted, causing a brief delay. The issue was traced to a problem with our external vendor, Fiserv’s Enterprise Payments Platform \(EPP\), which supports wire processing. Service was fully restored after the vendor made the necessary fixes, and normal operations resumed. To resolve the issue, Fiserv completed a system configuration update at 9:24 a.m. PT \(12:34 p.m. ET\), addressing a compatibility problem that was causing the errors. **Point of Failure:** Fiserv has performed a preliminary root cause analysis and determined that this incident was caused by a Fiserv vendor-managed component \(Ingress Controllers\) that was upgraded across several environments. This triggered the outage due to incompatibility with a Fiserv monitoring component used within the affected configuration \(Ingress Controller setup\). **Corrective Actions:** Fiserv is working with Microsoft to reduce the likelihood of recurrence by enhancing validation and testing procedures for configuration changes and ensuring that all server dependencies are identified and addressed before deployment. Additional monitoring will also be implemented to detect and address EPP UI proxy errors in real time. At Central 1, we improved our monitoring to catch issues with third-party systems earlier. We are also reviewing vendor support and escalation processes to help resolve issues faster. In addition, we’ve evaluated our internal incident response procedures to improve coordination and response during vendor-related outages. * Central 1 has implemented an automated daily test at 4:00 a.m. PT \(7:00 a.m. ET\) to confirm outgoing wire transfers are working properly and to detect issues earlier. We sincerely apologize for the disruption and the impact this incident had on your operations, particularly for time-sensitive wire transactions. We appreciate your patience while services were restored. Liz Ackroyd, Manager of Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337
Latest: **Postmortem: INC222639 – Outgoing and Incoming Wire Transfers Delayed** On June 1, 2026, between 7:25 and 10:55 a.m. PT \(10:25 and 1:55 a.m. ET\), a Central 1 third-party tool us…
-
- Payment ServicesTreasury ServicesDigital Banking Services
Timeline · 3 updates
- identified · May 22, 2026, 01:21 AM UTC
Central 1 is currently experiencing a recurrence of the Client Centre access issue. Users may encounter the “Sorry Page” when attempting to access the site. Our teams are actively engaged and escalating with our vendor to address this issue. In parallel, we are working on alternative solutions to mitigate the impact and resolve the underlying environment issue as quickly as possible. The “Sorry Page” remains available and provides access to key applications via direct links. We will continue to provide updates as more information becomes available and appreciate your patience. Central 1 Support - [email protected] - 1 888 889 7878, press 1
- resolved · May 22, 2026, 09:53 PM UTC
Client Centre service has been restored, and access is now fully available at https://clients.central1.com/. As part of the resolution, Central 1 has successfully transitioned Client Centre off the previous 3rd party hosting environment and into our Azure infrastructure. This change is intended to improve overall service stability and resiliency going forward. We will continue to monitor performance closely to ensure a stable experience for our clients. If you experience any issues accessing Client Centre, please refresh your browser or clear your cache before attempting again. We appreciate your patience and understanding throughout this incident. Central 1 Support - [email protected] - 1 888 889 7878 (press 1)
- postmortem · Jun 02, 2026, 09:25 PM UTC
**Postmortem: INC221480 – Client Centre Intermittent Login Failures** Between May 4 and May 22, 2026, clients experienced intermittent access issues when attempting to log in to Client Centre \([clients.central1.com](http://clients.central1.com)\). Full service was restored on May 22, 2026, at approximately 2:10 p.m. PT \(5:10 p.m. ET\). The disruption was caused by instability within an external hosting environment supporting Client Centre at the time, which resulted in intermittent degradation of authentication services. During this period, some users experienced login failures or inconsistent access. No data loss or security concerns were identified. Central 1 restored stability by transitioning Client Centre to a Central 1-managed Azure-hosted environment, significantly improving reliability, and reducing dependency on the previous hosting platform. For a more detailed root cause review, please refer to the Client Centre news item: [https://clients.central1.com/news\_updates/client-centre-service-disruption-update/](https://clients.central1.com/news_updates/client-centre-service-disruption-update/) **Corrective Actions – PRB011734** * **PTASK – Transition to Central 1-managed hosting – COMPLETED** • Migrated Client Centre to an Azure-hosted environment to improve stability and control. * **PTASK – Enhance monitoring and alerting – IN PROGRESS** • Improving detection capabilities to identify degradation conditions earlier. * **PTASK – Strengthen resiliency controls – IN PROGRESS** • Implementing additional safeguards to reduce the likelihood and impact of similar disruptions. * **PTASK – Improve incident communication and escalation – IN PROGRESS** • Enhancing coordination and communication processes during service disruptions. We apologize for the disruption experienced during this incident. Central 1 is taking these steps to strengthen platform stability, improve monitoring, and ensure a more consistent experience for clients. Jason Seale | Director of Client Support Services [[email protected]](mailto:[email protected]) | 778.558.5627
Latest: **Postmortem: INC221480 – Client Centre Intermittent Login Failures** Between May 4 and May 22, 2026, clients experienced intermittent access issues when attempting to log in to Cl…
-
- Digital Banking ServicesIncident Alerting
Timeline · 3 updates
- monitoring · May 21, 2026, 08:54 PM UTC
Members may have experienced an error message "There was an error processing your request" when attempting to log in to online banking between 1:02 p.m. and 1:30 p.m. PT (4:02 p.m. to 4:30 p.m. ET). The issue has now been resolved. A postmortem will be completed, and a summary will be shared once available. [email protected] - 1.888.889.7878 (option 2)
- resolved · May 22, 2026, 03:37 PM UTC
The system has remained stable thought the night. A postmortem will be completed, and a summary will be shared once available. [email protected] - 1.888.889.7878 (option 2)
- postmortem · Jun 05, 2026, 06:03 PM UTC
**Postmortem: INC222016 – Digital Banking Login Errors** On May 21, 2026, between approximately 1:02 p.m. PT \(4:02 p.m. ET\) and 1:30 p.m. PT \(4:30 p.m. ET\), some Digital Banking users experienced intermittent login errors when accessing online banking. During this time, users may have received the message “There was an error processing your request.” The incident was caused by a temporary resource constraint within the Azure environment hosting Central 1’s F5 load balancer. A brief period of CPU contention on the shared cloud infrastructure impacted the load balancer’s ability to process health checks and maintain synchronization between nodes within expected time thresholds. This resulted in delayed failover behavior and required manual intervention to restore normal service. The impact was limited in scope to Digital Banking login services and was short in duration for affected users. Payment services were not impacted. No data loss or security concerns were identified. **Corrective Actions – PRB011739** * **PTASK0010574 – Fine-tune HA failover capability – IN PROGRESS** • Improve failover responsiveness to reduce dependence on manual intervention during similar conditions. * **PTASK0010575 – Improve F5 monitoring – COMPLETED** • Enhanced monitoring to provide earlier detection of load balancer performance degradation. * **PTASK0010576 – Test and implement vendor-recommended fixes – IN PROGRESS** • Evaluate and apply vendor guidance to improve resilience under constrained resource conditions. * **PTASK0010577 – Escalate CPU contention concerns with Microsoft Azure – IN PROGRESS** • Engage Microsoft to review resource allocation behaviour and reduce risk of recurrence. We apologize for the disruption experienced during this incident. Central 1 is taking these steps to strengthen resilience and improve failover performance within our cloud-hosted infrastructure. Santino Parrotta | Manager, Client Support Services [[email protected]](mailto:[email protected])
Latest: **Postmortem: INC222016 – Digital Banking Login Errors** On May 21, 2026, between approximately 1:02 p.m. PT \(4:02 p.m. ET\) and 1:30 p.m. PT \(4:30 p.m. ET\), some Digital Bankin…
-
- Central 1 ServicesPayment ServicesTreasury ServicesDigital Banking Services
Timeline · 6 updates
- investigating · May 19, 2026, 02:09 PM UTC
Central 1 is currently experiencing degraded performance affecting the Client Centre (https://clients.central1.com/). Currently, users should receive the Sorry Page providing direct links to applications. 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)
- investigating · May 19, 2026, 05:13 PM UTC
We’re continuing to work with our partners and internal teams to restore full access to the Client Centre. While the issue is still under investigation, we have implemented a temporary solution that allows users to access key applications through a dedicated page. Our teams are actively working to resolve the issue as quickly as possible and improve overall service resiliency. We’ll continue to provide updates as more information becomes available and appreciate your patience in the meantime.
- investigating · May 19, 2026, 06:22 PM UTC
We are conducting a thorough analysis of the systems involved and working toward resolving the Client Centre issue. In the event you are receiving an error trying to access our Sorry Page (via Client Centre), please use the links provided on the Sorry Page, or use from the list below: - https://paymentstream.secure.central1.com/product/paymentstream/ for PaymentStream Direct - https://branchcapture.secure.central1.com/ for Branch Capture - https://filesandreports.secure.central1.com/login for the File & Report Exchange - https://central1-prod.aric.featurespace.co.uk/ for EFM - https://fas.secure.central1.com/fas/ for FAS - https://fxd.secure.central1.com/extranet for FX Drafts - https://olt.secure.central1.com/olt/ for OLT (Online Tracing) - https://ors.secure.central1.com/ors/ for ORS (Online Return System) - https://central1.service-now.com/support/ for ServiceNow - https://cms.memberdirect.net/ for TeamSite - https://admin.secure.central1.com/um/ui/flex/ModifyUser/ for User Management - https://treasuryconnect.secure.central1.com/tos/ Treasury Connect Please ensure you do not use bookmarks/favorites for your Applications. We’ll continue to provide updates as more information becomes available and appreciate your patience in the meantime.
- investigating · May 20, 2026, 01:58 AM UTC
We’re continuing to work closely with our vendor and internal teams to restore full Client Centre functionality. At this time, there are no new material updates; however, efforts remain actively underway and resolution remains a top priority. The temporary “Sorry Page” continues to provide access to key applications via direct links. If you encounter issues accessing the page, please use the application links provided in the previous update. We will provide our next update by end of business tomorrow by 2 p.m. PT (5 p.m. ET), or sooner if additional information becomes available. We appreciate your continued patience. Central 1 Support - [email protected] - 1 888 889 7878 (press 1)
- investigating · May 20, 2026, 09:09 PM UTC
We’re continuing to work closely with our vendor and internal teams to restore full Client Centre functionality. While there are no new material updates at this time, this issue remains a top priority and work is actively progressing toward resolution. The temporary “Sorry Page” remains in place and continues to provide access to key applications via direct links. We will provide our next update by tomorrow at 2 p.m. PT (5 p.m. ET), or sooner if additional information becomes available. We appreciate your continued patience and understanding. We will provide our next update by end of business tomorrow by 2 p.m. PT (5 p.m. ET), or sooner if additional information becomes available. We appreciate your continued patience. Central 1 Support - [email protected] - 1 888 889 7878 (press 1)
- resolved · May 21, 2026, 10:44 PM UTC
Client Centre access has now been fully restored and services are operating normally. Users can resume accessing applications through https://clients.central1.com/ as usual. If you continue to experience issues or are still seeing the “Sorry Page,” this may be due to cached browser data. Please clear your cache (Ctrl + Shift + Delete) and refresh your browser before attempting to log in again. We appreciate your patience while we worked to resolve this issue. Central 1 Support - [email protected] - 1 888 889 7878, press 1
Latest: Client Centre access has now been fully restored and services are operating normally. Users can resume accessing applications through https://clients.central1.com/ as usual. If you…
-
See the full Central 1 outage history
28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Central 1 outage history →Or sign up free to get alerts when Central 1 breaks · 10 free monitors · No credit card
- Started Jun 05, 2026, 05:18 PM UTC · ● 8d 3h
- Started Jun 03, 2026, 08:56 PM UTC · Resolved Jun 03, 2026, 10:27 PM UTC · 1h 30m
- Started Jun 01, 2026, 03:35 PM UTC · Resolved Jun 01, 2026, 06:29 PM UTC · 2h 54m
- Started May 22, 2026, 01:21 AM UTC · Resolved May 22, 2026, 09:53 PM UTC · 20h 32m
- Started May 21, 2026, 08:54 PM UTC · Resolved May 22, 2026, 03:37 PM UTC · 18h 42m
- Started May 19, 2026, 02:09 PM UTC · Resolved May 21, 2026, 10:44 PM UTC · 2d 8h
- Started May 19, 2026, 02:26 AM UTC · Resolved May 19, 2026, 12:27 PM UTC · 10h
- Started May 17, 2026, 11:50 AM UTC · Resolved May 17, 2026, 02:08 PM UTC · 2h 18m