Can you attach output of 'traceroute fedorapeople.org' and 'ping fedorapeople.org' (from the several servers if they are on different networks).

It's working fine for me here. We do have one other report of an issue with routing in NCREN, this might be related. Additionally we often see people who have ipv6 configured incorrectly unable to reach it (it has a valid and reachable ipv6 address).

I don't have IPv6 networking available here so only the IPv4 will be used.

jansyren@server:/mnt/sdbb1$ traceroute -e fedorapeople.org
traceroute to fedorapeople.org (152.19.134.199), 30 hops max, 60 byte packets
1 *
2 *
3 *
4 *
5 *
6 *
7 *
8 *
9 *
10 *
11 *
12 *
13 *
14 *
15 *
16 *
17 *
18 *
19 *
20 *
21 *
22 *^C

This repeats all throughout my local machines using the ISP's standard gateway but when I connect through VPN through the same ISP it seems to work.

Through VPN on the server, same ISP

jansyren@server:~$ traceroute -e fedorapeople.org
traceroute to fedorapeople.org (152.19.134.199), 30 hops max, 60 byte packets
1 10.251.2.1 (10.251.2.1) 22.211 ms 23.174 ms 23.873 ms
2 h-85-24-253-1.NA.cust.bahnhof.se (85.24.253.1) 25.003 ms 25.005 ms 25.552 ms
3 sto-ste-dr1.sto-cr1.bahnhof.net (176.10.178.168) <MPLS:L=24207,E=0,S=1,T=1> 24.813 ms 24.802 ms 24.781 ms
4 sto-cr2.sto-cr3.bahnhof.net (46.59.113.21) 23.625 ms 23.686 ms 24.569 ms
5 se-sthb.nordu.net (195.69.119.24) 23.529 ms 23.531 ms 23.512 ms
6 dk-ore.nordu.net (109.105.97.130) <MPLS:L=90148,E=0,S=0,T=1/L=16,E=0,S=1,T=1> 32.354 ms dk-ore.nordu.net (109.105.97.130) <MPLS:L=96130,E=0,S=0,T=1/L=16,E=0,S=1,T=1> 31.337 ms dk-ore.nordu.net (109.105.97.130) <MPLS:L=90148,E=0,S=0,T=1/L=16,E=0,S=1,T=1> 31.289 ms
7 dk-bal2.nordu.net (109.105.97.249) <MPLS:L=32133,E=0,S=0,T=1/L=16,E=0,S=1,T=2> 39.908 ms 32.632 ms de-hmb.nordu.net (109.105.97.57) <MPLS:L=12029,E=0,S=0,T=1/L=16,E=0,S=1,T=2> 36.746 ms
8 nl-sar.nordu.net (109.105.97.51) <MPLS:L=32193,E=0,S=0,T=1/L=16,E=0,S=1,T=3> 43.398 ms dk-esbj.nordu.net (109.105.97.3) <MPLS:L=6200,E=0,S=0,T=1/L=16,E=0,S=1,T=3> 38.036 ms nl-sar.nordu.net (109.105.97.51) <MPLS:L=32193,E=0,S=0,T=1/L=16,E=0,S=1,T=3> 44.100 ms
9 uk-hex.nordu.net (109.105.97.127) <MPLS:L=390112,E=0,S=0,T=1/L=16,E=0,S=1,T=4> 56.053 ms 56.047 ms 56.968 ms
10 99.83.66.169 (99.83.66.169) 133.039 ms 133.902 ms 133.897 ms
11 ae-32.2603.rtsw2.ashb.net.internet2.edu (64.57.21.53) 130.883 ms 131.784 ms 127.870 ms
12 *
13 lo-0.8.rtsw.rale.net.internet2.edu (64.57.20.154) 136.406 ms 138.940 ms 139.344 ms
14 198.71.47.222 (198.71.47.222) 135.432 ms 134.666 ms 137.145 ms
15 ws-gw-to-rtp-gw.ncren.net (128.109.9.34) 140.609 ms 140.545 ms 140.563 ms
16 uncphillips-to-ws-gw.ncren.net (128.109.1.90) 144.228 ms 144.501 ms 144.616 ms
17 core-p-v1213.net.unc.edu (152.2.255.66) 144.351 ms 143.998 ms 144.783 ms
18 core-m-v1528.net.unc.edu (152.2.255.166) 144.696 ms 146.514 ms 146.502 ms
19 vm20.fedora.ibiblio.org (152.19.134.199) 144.608 ms !X 141.390 ms !X 142.269 ms !X

jansyren@server:~$ ping fedorapeople.org
PING fedorapeople.org (152.19.134.199) 56(84) bytes of data.
64 bytes from vm20.fedora.ibiblio.org (152.19.134.199): icmp_seq=1 ttl=46 time=141 ms
64 bytes from vm20.fedora.ibiblio.org (152.19.134.199): icmp_seq=2 ttl=46 time=141 ms
64 bytes from vm20.fedora.ibiblio.org (152.19.134.199): icmp_seq=3 ttl=46 time=141 ms
64 bytes from vm20.fedora.ibiblio.org (152.19.134.199): icmp_seq=4 ttl=46 time=140 ms

Here are the logs from my firewall, I forgot that it is blocking icmp so the traceroutes get a bit boring :) As you can see it reaches the same as hop 16 through the VPN and then it just stops, so there seems to be an issue there in the routing layer I would guess.

Watchdog> traceroute 152.19.134.199

Type escape sequence to abort.
Tracing the route to 152.19.134.199

1 100.127.64.1 0 msec 0 msec 0 msec
2 46.59.117.10 10 msec 10 msec 10 msec
3 46.59.117.9 20 msec 10 msec 10 msec
4 158.174.156.198 10 msec
158.174.156.166 10 msec 10 msec
5 158.174.156.161 10 msec 10 msec 20 msec
6 176.10.179.85 10 msec 20 msec 10 msec
7 212.237.193.24 30 msec 20 msec 30 msec
8 109.105.97.136 20 msec
109.105.97.116 20 msec
109.105.97.49 20 msec
9 109.105.97.3 30 msec
109.105.97.222 20 msec
109.105.97.132 30 msec
10 109.105.97.57 20 msec
109.105.97.3 30 msec 20 msec
11 109.105.97.127 40 msec
109.105.97.51 40 msec
99.83.66.169 120 msec
12 99.83.66.169 120 msec 120 msec
64.57.21.53 120 msec
13 64.57.21.53 120 msec 160 msec 120 msec
14 64.57.21.53 130 msec
64.57.20.154 120 msec
15 198.71.47.222 120 msec
64.57.20.154 130 msec 130 msec
16 64.57.20.154 140 msec
198.71.47.222 130 msec
64.57.20.154 130 msec
17 128.109.9.34 130 msec
198.71.47.222 130 msec 130 msec
18 128.109.1.90 130 msec
128.109.9.34 130 msec
19 128.109.1.90 130 msec *
20 * *
21 * *
22 * *
23 * *
24 * *
25 * *
26 * *
27 * *
28 * *
29 * * *
30 * * *

Hey, is this still happening? Another set of folks having issues reported recently that it started working again... can you retest?

works for me

Hey, is this still happening? Another set of folks having issues reported recently that it started working again... can you retest?

Hi, sorry have been out of office. Yes I can confirm it is working again. Might have been a temporary ban of the DHCP ip range from my isp or something. Thanks for getting back to me.

Br
Jan