Central 1 Status Page

Aug 13, 2026 · resolved Aug 17

After thorough investigation and remediation efforts, this incident has been resolved. User Management (UM) Security Officer and Business User Administrator (BUA) permissions have been fully restored, and the synchronization process is now operating as expected. Any pending permission updates have been successfully processed and reflected in user accounts. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience and understanding while we worked to restore service.

Aug 10, 2026 · resolved Aug 13

*** This notice is for credit unions who have Everlink as their switch provider. *** Everlink has resolved the issue affecting INT network POS and SCD trace processing, and credit unions may now resume submitting new INT network POS and SCD trace requests. Follow-up requests for previously submitted INT network traces will be completed after September 10, once PPJV has cleared the backlog of new trace requests. Thank you for your patience while this issue was being addressed. Central 1 - [email protected] - 1.888.889.7878 Option 1

Aug 11, 2026 · resolved Aug 11

**Postmortem: INC226099 – Mobile Remote Deposit Capture \(mRDC\) Service Interruption** On August 11, 2026, between 2:05 a.m. and 10:13 a.m. PT \(5:05 a.m. and 1:13 p.m. ET\), the Mobile Remote Deposit Capture \(mRDC\) service experienced an interruption, preventing members from successfully submitting mobile cheque deposits. During this period, deposit requests could not be processed due to a loss of connectivity between the mRDC application and supporting data services. **Point of Failure** As part of a database governance and standardization initiative, database service account permissions were updated to align with enterprise standards. This change exposed an undocumented user privilege dependency within the mRDC environment where the application access relied upon a legacy access permission for a service account. **Resolution** The team restored service by re-establishing the required database permissions and restarting the affected application, restoring connectivity and allowing deposit processing to resume. Once service was recovered, queued transactions were processed, and normal member activity resumed. While these actions resolved the immediate service interruption, the incident highlighted opportunities to strengthen platform resiliency and change validation processes. Central 1 has initiated a series of corrective measures to reduce dependency on legacy configurations, improve monitoring and alerting capabilities, strengthen change controls, and enable faster operational recovery should a similar event occur in the future. **Corrective Actions \(PRB011762\)** * Document and enhance the database user governance change process, including validation and testing requirements. – In Progress * Review remaining databases for legacy access dependencies and remediate where required. – In Progress * Implement post-change reviews of SQL Server logs to identify access and authentication issues immediately following user governance changes. – Complete * Enhance monitoring and alerting for RDC transaction failures and abnormal transaction patterns. – In Progress * Require all database user governance changes to be executed through the formal Change Management process. – Complete * Implement monitoring for RDC deposit confirmation transactions. – In Progress We sincerely apologize for the disruption and the impact this incident had on your members and operations. We appreciate your patience and understanding while services were restored and thank you for your continued partnership Liz Ackroyd Manager, Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337

Jul 31, 2026 · resolved Jul 31

The Foreign Exchange (FX Trader) application is now available. Central 1 - [email protected] - 1.888.889.7878, press 1

Jul 31, 2026 · resolved Jul 31

**Postmortem: INC225671 – Delayed Incoming and Outgoing Wire Transfers** On July 31, 2026, between 4:41 a.m. and 7:58 a.m. PT \(7:41 a.m. and 10:58 a.m. ET\), Central 1 experienced a disruption that delayed the processing of both incoming and outgoing wire transfers. During this period, outgoing wires were unable to progress through processing, and incoming wires were not delivered to downstream systems as expected. Following an investigation across the wire-processing environment, the issue was traced to an application responsible for facilitating communication between core processing systems. After a network connectivity interruption, the application was unable to resume processing messages, resulting in a backlog and delayed transaction flow. **Point of Failure** On July 31, 2026, a network connectivity interruption impacted communication between components supporting wire processing. While the affected systems remained available, one of the applications failed to re-establish communication after the interruption, preventing transactions from progressing through the normal processing flow. **Resolution** Service was restored by restarting the affected application, which successfully re-established connectivity and resumed normal transaction processing. Once connectivity was restored, queued transactions were processed, and wire services returned to normal operation. While the restart resolved the immediate processing interruption, the underlying cause of the connectivity loss remains under investigation. As a result, Central 1 has initiated a series of corrective actions focused on improving application resiliency, enhancing transaction-flow and queue monitoring, strengthening alerting and escalation processes, and enabling faster operational recovery should a similar condition occur in the future.  **Corrective Actions \(PRB011760\)** * Implement application resiliency improvements to automatically recover from connectivity interruptions and reduce the risk of similar delays. **In Progress** * Validate PagerDuty routing, team assignments, and escalation processes to ensure rapid engagement and clear ownership during major incidents. **In Progress** * Provide an operational recovery script and training to the PS Software team and Computer Operators to ensure approved recovery procedures are executed consistently when known wire-processing issues occur. **Complete** * Work with Fiserv to implement queue-depth monitoring to improve visibility into processing delays. **In Progress** * Enhance PSD/MTS transaction-flow monitoring to enable earlier detection of processing interruptions. **In Progress** * Assess and implement potential message-queue reconnection enhancements to improve system resilience. **In Progress** 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 and understanding while services were restored and thank you for your continued partnership. **Liz Ackroyd** Manager, Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337

Is Central 1 down right now?

No — Central 1 is up. All systems operational as of Aug 28, 3:58 AM UTC.

What is Central 1's current status?

Central 1: All Systems Operational. Alert24 checks Central 1's status page continuously and can notify you the moment it changes.

How do I get alerted when Central 1 goes down?

Alert24 monitors Central 1 and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.