Dear CentOS Infrastructure Team,
My name is Adam and I'm the Product Manager for Registry integrations at JFrog. I'm reaching out on behalf of our mutual users and customers that are experiencing serious disruptions in service when trying to download from http://mirror.centos.org/.
We suspect some form of User Agent and/or IP blocking and we would like to work together to mitigate the issue. Here is a list of our NAT IPs https://jfrog.com/help/r/what-are-artifactory-cloud-nated-ips/what-are-artifactory-cloud-nated-ips and also information about our User Agent https://jfrog.com/help/r/artifactory-user-agent
Could you please investigate this urgently and let us know the reason for the block and the steps required to have it removed? We are available to provide any further information you may need from our end.
You can reach us directly at registry-ops@jfrog.com
Thank you for your prompt attention to this critical matter.
Sincerely, Adam
Hi @adam-browning, thanks for reaching out. Can you be more explicit about what issues you're facing? What are you trying to do, and do you have any logs you can share? I'm not sure I understand the traffic flow given you mention your users, but then reference the JFrog IP lists.
Thanks!
Hi @gwmngilfen thanks for responding. We started seeing increases in status 404 and 408 responses reported by our customers. In the past there were cases where our NAT IPs were blocked and we wanted to check if any such user agent or IP blocks were recently introduced and if so for what reason as we would like to mitigate on our side of course.
Currently our investigation revealed mostly issues of misconfiguration on our end that we are fixing. I think that we can close this issue for now and if find something more concrete we'll re-open . Thank you for your time and patients Thanks and sorry for the false alarm
Metadata Update from @adam-browning: - Issue close_status updated to: Insufficient Data - Issue status updated to: Closed (was: Open)
Metadata Update from @arrfab: - Issue close_status updated to: Invalid (was: Insufficient Data)
Log in to comment on this ticket.