Lots of consumer router/gateways out there are old and don't have IPv6 turned on. If you turn off IPv4 for your services, those folks just won't be able to conn

Lots of consumer router/gateways out there are old and don't have IPv6 turned on. If you turn off IPv4 for your services, those folks just won't be able to connect and they won't know why, they'll just move on. Any who want to complain won't even know who to complain to, and they won't be able to fix it themselves. That's bad. And yes, you could put a CDN in front of everything, but won't that wipe out some/all of the savings (assuming you're with a cloud provider that's charging for IPv4)? This basically explains why I put the brakes on our IPv6 migrations. From our clients' perspective it would have been an unforced error.