2024-03-06T01:21:58 *** teepee_ is now known as teepee 2024-03-06T11:40:18 *** teepee_ is now known as teepee 2024-03-06T12:10:43 seems bugzilla is dying 2024-03-06T14:03:40 seems to be a local issue for some reason. do bugzilla.suse.com and openqa.o.o have something in common that build.o.o or www / wiki / planet don't? 2024-03-06T14:04:38 the first ones timeout, the others work 2024-03-06T18:16:37 krop: bugzilla and openqa have in common, that they are _not_ hosted in the openSUSE infrastructure :) 2024-03-06T18:17:39 and they're still unreachable from here 2024-03-06T18:17:51 works for me 2024-03-06T18:18:26 same here, but Rado also complained that some services do not work for him. Is it possible that some ISPs like O2 or similar have an outage? 2024-03-06T18:18:35 (same here as it works for me) 2024-03-06T18:20:00 they are routed through the same ISP (IPv4 at least - IPv6, which are not offered by openQA/Bugzilla and only be the other services, is using a different ISP) 2024-03-06T18:20:28 so maybe ISP on the client end 2024-03-06T18:20:33 is there another site I could check? 2024-03-06T18:20:36 you can check with traceroute 2024-03-06T18:21:20 with opensuse.org you can compare -4 and -6 2024-03-06T18:22:56 I tried with both traceroute -I / -T I don't get anything (literally) 2024-03-06T18:24:39 sounds like something on your end .. works fine for me (both with and without the extra options) 2024-03-06T18:25:00 It's really suspicious that I've seen that from multiple people. 2024-03-06T18:25:32 I hope it's not some malicious site protection and you and Rado use the same router :-) 2024-03-06T18:25:58 if someone with the issue has some publicly reachable address, I am happy to try in the opposite direction 2024-03-06T18:26:15 but only from openSUSE infra 2024-03-06T18:26:19 ack 2024-03-06T18:26:24 Thank you Georg! 2024-03-06T18:27:19 you can try tracing sakura.krop.fr 2024-03-06T18:28:35 does it allow icmp? 2024-03-06T18:29:01 it's supposed to reply to pings 2024-03-06T18:29:42 ping works neither from openSUSE nor from my home 2024-03-06T18:29:47 here is traceroute from openSUSE https://paste.opensuse.org/pastes/817ea89e350a 2024-03-06T18:32:10 from my home, it gets stuck at the same hop 2024-03-06T18:42:50 ah interesting.. a traceroute to www.opensuse.org fails but traceroute6 works 2024-03-06T18:44:14 then that explains the different behavior between the mentioned services 2024-03-06T21:49:03 I made more tests with the different prefixes from AS 29298 only adresses in 91.193.113.0/24 can be traced. 195.135.223.0/24 fails and 195.135.222.0/24 seems to have a problem 2024-03-06T21:58:25 what I do not understand, you say you do not get "anything" with traceroute. if it's specific to these target networks, you should at least have hops from your ISP show up 2024-03-06T21:58:55 otherwise it looks like these networks are filtered already at your gateway which would be quite odd 2024-03-06T21:59:22 the 91.x one is in the US so it probably goes a different path 2024-03-06T22:00:16 maybe you could try with mtr ? 2024-03-06T22:06:11 nothing more (with mtr -c 5 -i 2 -rw 195.135.223.242 > report.txt) the route seems completely unknown 2024-03-06T22:07:45 *** danidoni7 is now known as danidoni 2024-03-06T22:15:50 report.txt is empty? 2024-03-06T22:16:13 just my router ip and nothing else 2024-03-06T22:17:07 is your router doing any sort of vpn or similar? 2024-03-06T22:17:25 I suspected the bottleneck could be cogent, that's the shortest route, but I can ping my ip from their looking glass 2024-03-06T22:18:06 and it can ping the SUSE ips as well 2024-03-06T22:19:24 given it gets stuck at cogent from openSUSE side as well, I do think it's possible 2024-03-06T22:19:33 the looking glass might run through some different system 2024-03-06T22:19:35 but it can't trace after 149.11.206.74, that's also cogent 2024-03-06T22:26:40 interesting situation 2024-03-06T22:27:03 I created a ticket to check and reach out to the ISP if needed. But it's already late so probably will only be read tomorrow .. 2024-03-06T22:29:54 from Austria, I also get stuck at 149.11.206.74 when trying to reach your 82.64.233.13. from Germany, it passes 149.11.206.74 and continues over 194.149.163.29, pinging fine 2024-03-06T22:30:41 194.149.163.29 is ProXad. maybe something between Congent and ProXad 2024-03-06T22:31:16 can't find a looking glass for Proxad though