IPv6 Excuse Bingo

My transit provider doesn't support IPv6 IPv6 just isn't a priority NAT444 is fine Can't we just buy more IPv4 addresses? AWS doesn't support it
It's too complicated Our vendor doesn't support it There's no certification track We don't have a lab to test it We don't need that many addresses
I don't want to lose the security provided by NAT Our business intelligence team can't even parse IPv4 logfiles It's not supported by Google Compute No one else has deployed it
Azure doesn't support it We forgot to include IPv6 in our last RFP IPv6 is a security risk We'll deploy IPv6 right after we deploy DNSSEC IPv6 isn't supported by OVH Cloud
Too many people have broken IPv6 stacks Larger headers are less efficient We would have to rewrite our entire application to support it What do you mean I have to wrap an IP in square brackets? We've still got plenty of IPv4
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses