Resolved - INC220447 - Issue Impacting Wires

Update timeline

1. investigating Apr 22, 2026, 08:56 PM UTC

   We are currently investigating an issue impacting Wires. At approximately 1:25 p.m. PT (4:25 p.m. ET), we observed incoming and outgoing wires not moving in our system. At this time, we are working to validate scope. We will provide an update within 30 minutes or sooner as more information becomes available. Central 1 – [email protected] - 1.888.889.7878, press 1

2. investigating Apr 22, 2026, 09:22 PM UTC

   Fiserv has raised a critical incident and have their team engaged reviewing a core issue within their infrastructure causing impacts to our wires system. As a workaround, Central 1 is currently manually releasing incoming and outgoing wires. The work around will prevent any further delays in wires processing while Fiserv continue to triage their incident. We will provide an update within 1 hour or sooner as more information becomes available. Central 1 – [email protected] - 1.888.889.7878, press 1

3. monitoring Apr 22, 2026, 10:26 PM UTC

   Central 1 has been able to manually process incoming and outgoing wires up to 3 p.m. PT (6 p.m. ET) wires close time (SWIFT gateway closed). Fiserv continues to triage their critical incident and have Central 1 teams engaged to ensure we can establish connectivity with their system. Central 1 and Fiserv will work to ensure there is system stability for tomorrow mornings 5 a.m. PT (8 a.m. ET) wires opening. We will provide an update tomorrow at 5:30 a.m. PT (8:30 a.m. ET). Central 1 – [email protected] - 1.888.889.7878, press 1

4. monitoring Apr 23, 2026, 03:08 AM UTC

   Fiserv has provided an update to Central 1 that they have resolved their technical issues within their Azure environment. Central 1 and Fiserv will complete additional validation steps to ensure system stability prior to Wires business hours resuming tomorrow morning at 5 a.m. PT (8 a.m. ET) wires opening prior to confirming the incident is resolved. We will provide another update tomorrow by 5:30 a.m. PT (8:30 a.m. ET).

5. resolved Apr 23, 2026, 11:23 AM UTC

   Central 1 has confirmed that both outgoing and incoming wire transfers have resumed normal processing. Central 1 – [email protected] - 1.888.889.7878, press 1

6. postmortem May 04, 2026, 01:08 PM UTC

   **INC220447 – Postmortem: Wire Transfer Service Disruption** On April 22, 2026, between 12:58 p.m. PT \(3:58 p.m. ET\) and 3:25 p.m. PT \(6:25 p.m. ET\), Central 1 experienced a service disruption impacting incoming and outgoing wire transfers. During this time, wire creation through PaymentStream Direct remained available; however, transmission, processing, and transaction inquiry functions were unavailable due to an issue with a third-party service provider. Central 1 began manually releasing wires at 2:30 p.m. PT \(5:30 p.m. ET\) and was able to complete processing all wires by end of day. **Point of Failure:** The disruption originated within the Enterprise Payments Platform \(EPP\), which supports wire processing and regulatory screening. Fiserv, in collaboration with its vendor partner, completed a preliminary root cause analysis. The issue was traced to a prior request to increase the network route count limit within the vendor’s infrastructure. However, only one of the fifteen required devices was updated. As a result, the network route limit was exceeded, causing service interruptions for applications hosted in the affected Azure U.S. regions. **Corrective Actions** Central 1 is taking the following steps to reduce the risk of recurrence and improve response times: * Enhancing monitoring capabilities to improve early detection of third-party processing failures * Reviewing vendor support and escalation processes to ensure faster resolution * Assessing internal incident management procedures to strengthen coordination and response during third-party outages **Fiserv Actions** * Working with its vendor partner to ensure consistent application of increased route limits across all network gateways * Strengthening change validation protocols for future route-limit modifications * Implementing stricter network expansion governance, requiring application teams to adopt modern infrastructure before requesting additional capacity; exceptions will require executive approval and careful scheduling * Implementing route aggregation \(target completion: May 17, 2026\) to reduce the risk of exceeding routing limits * Enhancing resiliency \(target: July 2026\) to reduce dependency on a single region and improve recovery during regional disruptions * Enabling active-active ingress to support auto-scaling and provide dedicated resources for improved availability and consistent access during peak demand. 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 being restored. Liz Ackroyd | Manager of Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337