Wells Fargo's outage is a vendor dependency audit

At Wells Fargo Advisors, the continuity plan has become the production system. AdvisorHub reported Wednesday that brokers were placing orders by phone and email a week after a vendor disruption first appeared and a day after it flared up again, and the manual channel is still in use.

AdvisorHub, citing two sources, tied the trouble to BetaNXT, the trade processing and tax reporting vendor inside the firm's operations, which Wells has not named publicly. A spokesperson said an unspecified outside vendor was experiencing a disruption affecting clients and that the firm was using established systems and processes to minimize the impact while it worked to restore service.

BetaNXT is no one-firm supplier: backed by Clearlake Capital and Motive Partners, it counts LPL Financial, Janney Montgomery Scott, and Stifel Financial among its customers. Its partnership with Wells reaches back before 2024, and the vendor now sits inside Advisor Gateway, the just-announced desktop at the center of a billion-dollar overhaul of Wells' wealth management division. Advisor Gateway connects with roughly 200 internal and third-party applications, BetaNXT included.

That shared client list turns a back-office problem into a cross-firm drill. Janney, with about 900 brokers, told AdvisorHub its order flow was unaffected, and Stifel, with more than 2,000, said no issues were immediately apparent. LPL, with around 32,500, said through a spokesperson it would not comment, though one LPL broker told the outlet that orders were taking longer than usual but were clearing. AdvisorHub's sources said the outage did not seem as widespread at other firms, though it may have been more pervasive at the larger ones.

For the practice, the episode has a sharper edge than a vendor status page: Wells, which has around 12,000 employee and independent advisors, is running its order desk the way firms ran order desks before trading software existed. A manual process only qualifies as a backup if the humans executing it have done it recently; an advisor who has spent years placing orders through a desktop application should not assume a verbal order will be second nature the day the desktop goes dark, and an operations team that has not taken a phone order in years will be rebuilding its own procedure in real time.

The dependency is not the number of vendors a practice uses but the number of functions that stop when a single vendor stops. Advisor Gateway's roughly 200 connections are 200 points of failure, each with its own vendor behind it, each with its own history of uptime. The practical question before choosing or renewing any trading, custody, or tax reporting utility is what the firm's own operations actually do on the morning the reliability promises in the marketing deck fail.

The due diligence should go one step further: ask what priority your firm gets when the vendor's largest clients are all on the phone at the same time, because the answer determines whether an outage is a footnote or a client event. A 12,000-advisor firm with a century of telephone protocols can absorb a manual stretch; a smaller practice with one operations person and a voice mailbox inherits the outage differently.

BetaNXT's website describes its retail product as a way to make execution, validation, and settlement run cleanly across asset classes. That is the marketing language of every back-office platform, and it is exactly why an outage lands on an advisor's desk rather than staying in the operations department. The smoother the rail, the more of the daily business travels on it, and the practices that take the right lesson from this week will run their manual drills before a vendor decides their schedule for them.