01THE HOUR
Morning
Friday 2 May 2025. United States. Reconstructed to the day; timeline elements carry approximate hours where the record supports them.
The issue was already running. Fiserv, one of the three largest core banking processors in the United States, had experienced an internal issue at one of its data centers earlier Friday. Something in the issue escalated.
User reports surged on DownDetector, and for most of the day customers at Bank of America, Ally, Old National Bank, Navy Federal and others found Zelle unavailable, wire transfers frozen, ACH payments stalled and online bill pay unresponsive. Card payments at the terminal continued.
02THE SEQUENCE
2 May, early morning
Fiserv experienced an internal issue at one of its data centers. The issue was not a result of malicious activity. Something in the issue propagated further than intended and disrupted internal systems.
2 May, around 7:43 a.m. ET
DownDetector reports surged, with about sixty Fiserv applications going down for some clients. Customers at Bank of America, Capital One, Navy Federal Credit Union, Truist, TD Bank, Ally, Synchrony and Citizens Bank lost the ability to move money externally: Zelle transfers, ACH payments, wire transfers and online bill pay all became unavailable. One source said problems escalated by 7 a.m.; the difference is consistent with the lag between internal failure and public reporting.
2 May, morning
Bank of America messaged customers directly. Scheduled payments may be delayed, the message said, and wire transfers are temporarily unavailable. The bank identified it as a vendor-related issue affecting multiple banks.
2 May, morning
Early Warning Services, the company behind Zelle, issued a statement. The situation, it said, involved "an independent third-party that provides services to particular financial institutions." Users who attempted Zelle transfers saw transactions marked "payment pending."
2 May, morning to afternoon
DownDetector reports peaked at approximately 1,000. Around 1:30 p.m., Fiserv said it had identified the problem and instituted a fix. Reports dropped to around 100 within the hour.
2 May, afternoon
Fiserv released a statement: "Earlier today, we experienced an internal issue that temporarily disrupted service. The issue has since been resolved, and we are now working to process the backlog." The company confirmed the outage was not a result of malicious activity.
2 May, evening onward
Resolution took longer than the afternoon statement suggested. American Banker reported it was more than twelve hours before service was fully restored. Fiserv had provided updates every fifteen minutes and larger communications every hour throughout.
3 May, morning
Truist confirmed all issues were resolved. DownDetector reports dropped to around 100. The outage had run from Friday morning into Saturday.
5 May
Fiserv disclosed the disruption occurred during a planned enhancement. The impact, it said, was limited to financial institutions whose systems were connected to the affected data center.

E.O. 14330 unlocks new 401(k) opportunity

Two ways to play it, inside

See this document?

It brings sweeping changes to your 401(k) — and yet almost nobody knows about it.

Hidden inside it is what one 40-year trading veteran calls the "biggest opportunity he's seen in years."

It's all right there in Section 3.

That's where Washington opens your retirement account up to a group of companies that have grown as much as 10,000%... 325,000%... and even 600,000%.

These are the fastest growing companies in America, previously off-limits to everyday folks.

But no longer — and yet that's not even the best part…

Because hedge fund legend Larry Benedict has spotted something in this executive order that almost nobody else has...

This executive order is about to transfer as much as $1 trillion of retirement money from one corner of the market to another…

And Larry has found the one ticker sitting in the path of this movement.

P.S. The last time Washington rewrote the retirement rules, Larry's readers had the chance at 188% gains. Now it's happening again — on a far bigger scale. Get the ticker before the money starts moving here.

03THE HIDDEN DEPENDENCY
The headline was Zelle. The dependency was underneath it: the layer where a core processor assembled and routed payment instructions on behalf of the banks it served.
Of the 2,200 financial institutions enrolled in Zelle at the time, eighteen connected directly to the network without using a third-party reseller. The rest routed through resellers including Fiserv, FIS and Jack Henry. Those eighteen institutions kept Zelle running on Friday morning while it was unavailable at banks whose systems connected through the affected Fiserv data center.
The same processor connection carried ACH file submissions, wire-transfer instructions and bill-pay requests to their respective settlement networks. The connection feeding instructions to each network was the layer that failed.
The connection feeding instructions to each network was the layer that failed.
04WHAT STILL WORKED
CARD-NETWORK TRANSACTIONS
Visa and Mastercard continued to process transactions throughout the outage. The card networks ran on infrastructure separate from Fiserv's core processing layer. An industry consultant confirmed to American Banker that neither network went down.
DIRECT ZELLE CONNECTIONS
Eighteen of the 2,200 financial institutions enrolled in Zelle connected directly to the network rather than through a third-party reseller. Those institutions maintained Zelle service throughout Friday.
BANKS ON UNAFFECTED DATA CENTERS
Fiserv stated the impact was limited to financial institutions whose systems were connected to the affected data center.
05THE PLUMBING
THE PLUMBING
2024
An ACH payment begins as a file. The originating institution, or the processor acting on its behalf, assembles entries into a batch, assigns an Effective Entry Date and delivers the file to an ACH Operator: either the Federal Reserve or The Clearing House's Electronic Payments Network. The Operator sorts the entries and settles them through the receiving institutions' reserve or clearing accounts.
When the processor that assembles the file cannot operate, the entries are never created. The Operator receives nothing and settles nothing.
06THE PATTERN LIBRARY
5 of 33 entries shown.
1When one retail withdrawal channel closes or fails, demand concentrates on whichever channel is left open, and the capacity of that channel sets what a depositor can obtain.
Observed: Northern Rock 2007, Cyprus 2013, India 2016, Greece 2015, United States 1933, Argentina 2001, Lebanon 2019, Worldpay 2026, TSB 2018, Afghanistan 2021, Nigeria 2023, Square 2023, United States 2025, Fiserv 2025, United States 2021.
26Core deposit processing for multiple banks can run through a single third-party vendor data center, concentrating the posting function at one site. A localized power loss and hardware failure at that site removed deposit posting and balance visibility for all client institutions simultaneously, even as payment networks continued delivering incoming transactions to the vendor.
Observed: United States 2025.
27A payment network that connects most of its enrolled institutions through third-party resellers can remain operational while a reseller's outage severs the connection for that reseller's clients, so the failure boundary follows the reseller relationship rather than the network itself.
Observed: Fiserv 2025.
32A branchless financial service whose card issuing, app and account access all run through a single third-party processor can lose every customer-facing channel at once when that processor fails, leaving no in-institution fallback.
Observed: Chime 2019.
33A failure at a third-party core processor severed peer-to-peer transfers, ACH, wire transfer and bill-pay services at once while card-network transactions continued, because the affected payment types shared a common connection through the processor rather than running on independent rails.
Observed: United States 2025.
CHANGED TODAY: No existing entries gained United States 2025. Entry 33 added, on a shared core processor connection severing multiple payment types while card networks on separate infrastructure continued.