This is generally caused by ignorance. Don't understand IPv6 so turn it off without investigating what the actual problem is. Usually it's caused by a broken IPv6 configuration - eg a route being announced but no actual connectivity.
Here IPv6 works perfectly and doesn't cause any problems. Many sites are much faster over v6 than legacy IP. Google stats show 45% of users access google over IPv6 so clearly it's working for all those millions of users too.
If IPv6 is not working you need to fix it, not turn it off.
> I cannot tell you how many devices or software have had a notice of "just disable IPV6, that will fix X" and it's worked perfectly.
I’ve heard this advice dozens of times, but it hasn’t worked once, to the point where I firmly believe that everyone giving out such advice either completely doesn’t care or know anything about networking, or, is suffering from some sort of a mental difficulty.
Eh, I disagree. There are ton of crappy consumer grade devices that claim to support IPv6 but there are obscure implementation issues and these same devices offer zero visibility into what the cause might be. Sure, a packet sniffer might explain some of it but the remedy may require adjustment to the device which abstracts all the IP config away. The situation sucks all around.
That’s just the natural consequence of running two protocols simultaneously.
People get issues with v4. But “just switch off v4” is never suggested as a solution cos it’s either all people have or they need it for the sites that only have it. So people fix problems they get with v4. If they get a problem with v6? Switch it off, v4 is working.
Granted v6 has had many teething problems and still isn’t as hassle-free as v4. But in recent years things have improved an awful lot.
I cannot tell you how many devices or software have had a notice of "just disable IPV6, that will fix X" and it's worked perfectly.
If V6 was working everywhere and it was a simple toggle I'd say sure. But it's not.