|
|
| 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. |
|
|
| 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. |
|
|