I'm happy I can announce that Copr should work newly for IPv6-only clients (IOW became available both on IPv4 and IPv6): $ host copr.fedorainfracloud.org copr.fedorainfracloud.org is an alias for copr-fe.aws.fedoraproject.org. copr-fe.aws.fedoraproject.org has address 3.225.109.36 copr-fe.aws.fedoraproject.org has IPv6 address 2600:1f18:8ee:ae00:7029:de62:a198:cfd7 $ host copr-be.cloud.fedoraproject.org copr-be.cloud.fedoraproject.org is an alias for copr-be.aws.fedoraproject.org. copr-be.aws.fedoraproject.org has address 52.44.175.77 copr-be.aws.fedoraproject.org has IPv6 address 2600:1f18:8ee:ae00:4303:a354:dbd2:4d89 The backend repositories are cached through AWS CDN: $ host download.copr.fedorainfracloud.org d1nld9ovj32u75.cloudfront.net has address 65.9.96.6 d1nld9ovj32u75.cloudfront.net has address 65.9.96.110 ... d1nld9ovj32u75.cloudfront.net has IPv6 address 2600:9000:2127:7200:4:bbc1:1840:93a1 d1nld9ovj32u75.cloudfront.net has IPv6 address 2600:9000:2127:6c00:4:bbc1:1840:93a1 ... That means that the crucial Copr infrastructure should be completely ipv6-aware. The IPv6 infrastructure in AWS doesn't allow us to preallocate the used IPv6 addresses, and assign them to any VMs we have there (Elastic IP support). So once we'll be moving the infrastructure from Fedora 33 to newer version (likely Fedora 35) we will allocate new set of infrastructure machines, and it will imply new set of IPv6 addresses. This of course implies slightly larger outage-window because we'll have to update the AAAA DNS records (not needed for IPv4). The (other) release notes are hosted here: https://docs.pagure.org/copr.copr/release-notes/2021-01-21.html Pavel