pecl.php.net channel.xml unreachable from AWS eu-west-1

@svpernova09 as requested in php/php-src#22827.

Two CI builds failed, 2026-09-07 19:04 and 19:26 UTC:

Updating channel "doc.php.net"
Channel "doc.php.net" is not responding over https://, failed with message: File https://doc.php.net:443/channel.xml not valid (received: HTTP/1.1 504 Gateway Timeout)
Updating channel "pear.php.net"
Channel "pear.php.net" is up to date
Updating channel "pecl.php.net"
Channel "pecl.php.net" is not responding over https://, failed with message: File https://pecl.php.net:443/channel.xml not valid (redirected but no location)
Trying channel "pecl.php.net" over http:// instead
Cannot retrieve channel.xml for channel "pecl.php.net" (File http://pecl.php.net:80/channel.xml not valid (redirected but no location))
No releases available for package "pecl.php.net/redis"

pear.php.net answers in the same run. doc.php.net and pecl.php.net don't.

Source: AWS eu-west-1, EKS Fargate, kaniko, image dunglas/frankenphp:1.12.7-php8.4-alpine.
Same runner, same Dockerfile, green on 2026-09-04 12:14 UTC.

From a connection outside AWS, 2026-09-07 20:50 UTC: channel.xml and https://pecl.php.net/get/redis-6.3.0.tgz both return 200, server BunnyCDN-BE1-1161. Same with User-Agent PEAR/1.10.16/PHP/8.4.25.

NAT egress IP available on request.

Start with the two failed CI runs from AWS eu-west-1 on EKS Fargate and compare their requests to the successful external requests for pecl.php.net/channel.xml and the Redis archive. Check the reported NAT egress IP and the kaniko build using dunglas/frankenphp:1.12.7-php8.4-alpine; done means identifying and resolving why these AWS-origin requests receive invalid redirects or timeouts while pear.php.net remains reachable.