For me (from Germany), fedoraproject.org resolves to these addresses:
$ host fedoraproject.org fedoraproject.org has address 209.132.181.15 fedoraproject.org has address 140.211.169.206 fedoraproject.org has address 152.19.134.142 fedoraproject.org has address 185.141.165.254 fedoraproject.org has address 209.132.190.2 fedoraproject.org has address 67.219.144.68 fedoraproject.org has address 152.19.134.198 fedoraproject.org has address 174.141.234.172 fedoraproject.org has address 8.43.85.67 fedoraproject.org has address 209.132.181.16 fedoraproject.org has address 140.211.169.196 fedoraproject.org has IPv6 address 2604:1580:fe00:0:dead:beef:cafe:fed1 fedoraproject.org has IPv6 address 2605:bc80:3010:600:dead:beef:cafe:fed9 fedoraproject.org has IPv6 address 2610:28:3090:3001:dead:beef:cafe:fed3
One of these, 2604:1580:fe00:0:dead:beef:cafe:fed1, does not respond. Neither to ICMP pings, nor to TCP connections on ports 80 or 443. I have the impression that this has been the case for some time. The reason why I noticed this at all is that every now and then NetworkManager indicates that it cannot determine if I am connected to the Internet (see question mark icon in attached screenshot). This happens when NetworkManager tries to do a request for http://fedoraproject.org/static/hotspot.txt and randomly picks 2604:1580:fe00:0:dead:beef:cafe:fed1 as the address to connect to. <img alt="screenshot.png" src="/fedora-infrastructure/issue/raw/575dd8090e0f1cc0926d391c16c948f637c2aea6327b6116ef0529538846229c-screenshot.png" />
Sorry about that.
Should be fixed now... we have ipv6 issues with this host from time to time.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Confirmed, thanks!
Hi, I noticed that the issue seems to have occurred again. The host 2604:1580:fe00:0:dead:beef:cafe:fed1 is not reachable for me since yesterday evening.
Metadata Update from @chref: - Issue status updated to: Open (was: Closed)
Fixed. We had monitoring for it at one point, but something seems to have changed. ;(
Also we need a better fix for this.
I am going to leave this open now and see if we can make it go away once and for all. In the mean time it should be up again now.
Confirmed, the host is reachable for me again.
I've commited the workaround here in ansible, so it should always be in place now.
:heavy_multiplication_x:
Login to comment on this ticket.