On the corporate side, it's annoying that Github, Twitter and OSUOSL (which hosts a lot of Free Software projects) still don't have IPv6 enabled (although I was told 2016-Q1 for OSUOSL).
On the corporate side, it's annoying that Github, Twitter and OSUOSL (which hosts a lot of Free Software projects) still don't have IPv6 enabled (although I was told 2016-Q1 for OSUOSL).
The ISPs even refuse to offer IPv6 when it comes to "big" customers, like apartment cooperatives with hundreds of apartments... You have to turn to the small/local ISPs for (consumer) IPv6 here.
VPS? Datacenter?
For example only: Stop Forum Spam only recently began testing their work for IPv6: https://www.stopforumspam.com/forum/viewtopic.php?pid=44371
I re-wrote my comment spam solution (not specifically for the comment spam problem, was doing some other stuff) and have long since enabled IPv6, but it's worth bearing in mind that network is one thing, sometimes what holds someone back from flipping the switch are the tools we use.
https://support.cloudflare.com/hc/en-us/articles/202494830-P...
So when 2001:db8:a1:b2::c:3 has sent spam to you, you can't know if you should block the network 2001:db8:a1:b2::/64 or the specific address 2001:db8:a1:b2::c:3. Some blacklists (carelessly) take the former approach and block entire datacenters.