История сбоев Central 1

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

The OREC0707 file is now available on the FTP server.

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)

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.

Payments Canada has confirmed that TD has resolved its internal issue and that all impacted AFT payments have been successfully posted to the recipient accounts. Central 1 – support@central1.com – 1.888.889.7878 (press 1)

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

Central 1 has successfully received the previously missing EDI Bill Payment files dated June 26 and June 29. Processing of these files is scheduled for this evening's bill payment processing cycle. Central 1 - Support@central1.com - 1.888.889.7878, press 1

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)

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)

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

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

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 - 1.888.889.7878, press

RBC and additional testing with several credit unions have confirmed that the denomination drop-down menu is now displaying currencies correctly. If your credit union continues to experience issues with the cash ordering system, please have affected users clear their browser history, then try again. Should the issue persist, please contact Central 1 Support for further assistance. Central 1 - Support@central1.com - 1.888.889.7878, press

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

RBC has confirmed that this incident is now resolved. To get the denominations to appear in the application's drop-down, you need to close all current browser sessions and reopen a fresh session. Please contact us if you have any further issues with the Cash Ordering application. Central 1 - Support@central1.com - 1.888.889.7878, press

PPJV (the service provider for most credit unions in Alberta, Saskatchewan, and Manitoba) experienced internal AFT system issues and was unable to send Central 1 AFT files since the second exchange yesterday (June 24, 2026). Central 1 has now received all the missing AFT files, and they will be processed in the next exchange at 3 p.m. PT (6.p.m. ET). Central 1 - Support@central1.com - 1.888.889.7878, press 1

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 have been posted. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at bptrace@central1.com.

Manitoba Hydro has confirmed all delayed payments have now been applied effective the original payment date. If you have any questions regarding this matter, please contact the Central 1 Bill Payment Operations team at bptrace@central1.com.

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

The AIBC0624 file is now available in your organization's FTP folder. Central 1 - Support@central1.com - 1.888.889.7878, press 1

Central 1 would like to advise that Telus is currently experiencing delays in processing bill payment trace requests. The impacted billers are: Telus Communications, Telus Mobility Inc, Telus Quebec and Telus Services Inc. At this time, the Central 1 Bill Payment tracing team will not be submitting 2nd and 3rd requests for any Telus traces as per their request. Telus expects to have the backlog cleared by mid-July. We appreciate your understanding and cooperation. If you have any urgent concerns, please feel free to contact the bill payment tracing department at bptrace@central1.com.

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)

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)

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)

The Unqualified clearing items for June 16 are now available on the FTP server.

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 becomes available. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

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. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

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. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

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. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

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 bptrace@central1.com.

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 bptrace@central1.com.

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

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

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 - Support@central1.com - 1.888.889.7878, press 1

**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 [eackroyd@central1.com](mailto:eackroyd@central1.com) | 905.301.1337

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 automatically reduced by the browser. Because the expiry is not being refreshed when users return, previously saved login details may expire sooner than intended and may no longer be available. This is why some users are experiencing their saved login information disappearing.   Our team is actively working on an update to ensure that login preferences are refreshed appropriately and maintained more reliably going forward.   In the meantime, if users’ saved login details are missing, they will need to re‑enter their information. This will restore functionality in the short term, although persistence remains subject to the current limitation until the fix is deployed. We appreciate your patience and understanding while we implement a permanent solution. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

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 login. Mobile App Update • The fix will require a new version of the mobile app. • Members will need to download/update the app to receive this fix (it will not apply automatically unless they have auto updates enabled). • This update will not require members to reconfigure their login details or biometrics beyond the current one-time re-entry if their saved information has already expired. Scope and Impact • This impacts all clients with Biometric Login enabled in the Mobile app and ‘Remember Me’ on OIDC. • For clients not yet on V18 App, the fix will be included as part of their upgrade. • For clients already on V18 App, a hot fix release will be deployed to the App and Play Stores. User Experience • If a user is currently able to log in and has working saved credentials, their “Remember Me” will continue to function until the cookie reaches its expiry. • If saved login information has already expired, users will need to re-enter their details once. Online Banking • There is no impact to online banking functionality outside of the “Remember Me” behaviour already described. This issue is the result of: • Modern browser changes limiting cookie lifespan to ~13 months, and • The application not currently refreshing the cookie expiry on return visits Next Steps: 1. Deployment of the OIDC fix. 2. Release of updated Mobile Apps across platforms We will provide further updates, including timelines for app availability in the app stores, as progress continues. We appreciate your patience while we implement a permanent solution. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

We are proceeding with an urgent OIDC release tonight to address the “Remember Me” expiry issue affecting desktop and manual login on mobile. CHG170934 – Urgent Digital Banking OIDC Release 1.0.62 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 Manual login within the mobile app. A corresponding Mobile App fix for biometric login is currently in internal testing. We will provide timelines for app release once testing is complete. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

The OIDC fix has been successfully deployed, addressing the “Remember Me” expiry issue for desktop and manual login within the mobile app. The system will now refresh the “Remember Me” cookie at login, ensuring saved login information is maintained with ongoing use. A fix for Biometric and QuickView persistence is being delivered via native Mobile App updates. These updates are being coordinated directly through Client Delivery for each client. Please reach out to your Delivery Consultant through the v18 app upgrade ticket to address timeline. The Native App hot fix does not require client testing. Once the new apps are in production end users will receive the update through the App Store (iOS) and Google Play Store (Android) (automatic for most users, depending on device settings). Once the users app has been updated, then the system will refresh the Biometric and Quickview settings when a user logs in via Biometric, ensuring saved login information is maintained with ongoing use. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

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 - support@central1.com - 1 888 889 7878, press 1

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 - support@central1.com - 1 888 889 7878 (press 1)

**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 [jseale@central1.com](mailto:jseale@central1.com) | 778.558.5627

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. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

The system has remained stable thought the night. A postmortem will be completed, and a summary will be shared once available. DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)

**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 [santino.parrotta@intellectdesign.com](mailto:santino.parrotta@intellectdesign.com)

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 - support@central1.com - 1 888 889 7878 (press 1)

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.

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.

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 - support@central1.com - 1 888 889 7878 (press 1)

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 - support@central1.com - 1 888 889 7878 (press 1)

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 - support@central1.com - 1 888 889 7878, press 1

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 - support@central1.com - 1‑888‑889‑7878 (press 1)

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.

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 - Support@central1.com - 1.888.889.7878, press 0

This incident has been resolved.