Cited on HN 6 times, 2021–2025, never outright recommendedscore 0
Years with an HN recommendation, 2007–2026
HN cites it in IPv6 threads as an example of a large adopter, especially for address-space collisions after mergers and conflicts in 10/8.
Wells Fargo engineers walk through the bank's four-year IPv6 journey at the North American IPv6 Summit 2014. They cover motivation, approach, achievements and observations.
“See this talk from Wells Fargo as an example” (HN, 2025)
> What is the sales pitch you would bring to the CEO of a Fortune 500? When you buy or merge companies, and they both have RFC 1918 addresses, you'll probably have a conflict between the two entities. You'll probably have to implement NAT with-in your own network and hope the two sides don't have to talk to each other that much. (Or you completely re-IP the acquisition.) With IPv6, either the companies will be using their own PI IPv6 space and/or they will be using unique ULA prefixes, so the chance of conflicts will be very small. This at least was one of the business cases for Wells Fargo, "the fourth largest bank in the United States by total assets and is one of the largest as ranked by bank deposits and market capitalization": * [this video]
Wells Fargo's business case for IPv6 including merger address conflicts
> There’s (IMO) a much better reason: so your endpoints can have globally unique addresses. Complications with address space collisions (esp. M&A) was one of the reasons give in this Wells Fargo presentation from 2014: * [this video]
Wells Fargo cites address collisions in mergers as IPv6 reason
> I have yet to meet an infrastructure engineer or even hear of one who switched to IPv6 on purpose because they thought it was better. T-Mobile US: * [link] Wells Fargo: * [this video] Microsoft * [link] * [link] Google: * [link] LinkedIn: * [link] Facebook is famously IPv6-only internally (and as of 2016, 60% of user traffic was over IPv6): * [link] * [link] * [link]
> IPv6 can work side by side with IPv4 on the servers, but it cannot replace IPv4. Facebook is famously IPv6-only internally (and as of 2016, 60% of user traffic was IPv6-only): * [link] * [link] * [link] Microsoft and Google are IPv6-only single-stack (or moving in that direction) on their internal corporate networks: * [link] * [link] * [link] Also Wells Fargo: * [this video] The main 'advantage' IPv4 has is inertia.
> Not sure why you'd need more than 10/8 Large organizations have moved to IPv6 because they, and everyone else, are using 10/8, and so when mergers and acquisitions happen trying to connect the networks together becomes a nightmare. See this talk from Wells Fargo as an example: * [this video]
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
Plays via YouTube's privacy-enhanced embed
6 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Read more