Done.

Thanks, it looks like -several- of the production proxies do answer now. But for whatever reason, about 70% of them don't?

{{{{
curl --compressed -i -v https://debuginfod.fedoraproject.org/metrics
* Trying 152.19.134.142:443...
* Connected to debuginfod.fedoraproject.org (152.19.134.142) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
[...]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
[... hangs for a few minutes ...]
<

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

}}}

Some proxies respond instantly. I haven't been able to figure out the right curl incantation to enumerate which ones are ok and which ones aren't. :-( I don't see anything on log01's merged-logs to explain it, and don't know of any access to the proxies' http/error logs.

Yeah, so... thats because debuginfod01.iad2.fedoraproject.org is not on our vpn, so the non iad2 proxies cannot reach it.

We can either:
1. Setup vpn on it.

or

1. Change dns to just resolve it to the iad2 proxies, not all proxies.

Up to you, would be glad to help with or rubber-stamp either option :-)

let's reopen until we implement one or the other solution for this

ok, just switching dns to make it work from iad2 only is a lot easier and so thats what I did. ;)