Closed erichiller closed 7 years ago
I have no problems accessing repo.msys2.org. Something with your network
Now - looking around - I see most can...
Hop IP Address HostName
1 208.123.79.34 mxtb-hsrp1.mxtoolbox.com
2 198.252.182.148 aus-core-10-v11.corenap.com
3 64.20.229.137 net64-20-229-137.static-customer.corenap.com
4 64.125.32.197 xe-2-2-0.mpr1.aus1.us.zip.zayo.com
5 64.125.27.29 ae1.cr1.dfw2.us.zip.zayo.com
6 64.125.20.66 ae11.er1.dfw2.us.zip.zayo.com
7 154.54.10.117 be3029.ccr41.dfw03.atlas.cogentco.com
8 154.54.28.73 be2763.ccr21.dfw01.atlas.cogentco.com
9 66.28.4.18 be2938.rcr21.dfw04.atlas.cogentco.com
10 154.24.9.210 te0-0-2-1.nr11.b028597-0.dfw04.atlas.cogentco.com
11 38.140.236.58 * * *
12 199.231.224.66 * * *
13 45.59.69.178 * * *
Step Time IP - Hostname / IP, Provider and Location details
1 0.395 ms 213.239.229.17 - core23.fsn1.hetzner.com
2 2.934 ms 213.239.245.225 - core11.nbg1.hetzner.com
3 3.197 ms 213.239.229.162 - juniper5.rz2.hetzner.de
4 3.621 ms 149.6.158.21 - te0-0-1-2.nr11.b040138-0.nue01.atlas.cogentco.com
5 3.755 ms 154.25.2.121 - te0-3-1-1.rcr21.nue01.atlas.cogentco.com
6 5.889 ms 154.54.37.218 - be2270.ccr22.muc03.atlas.cogentco.com
7 11.051 ms 154.54.36.53 - be2959.ccr41.fra03.atlas.cogentco.com
8 17.735 ms 130.117.0.121 - be2813.ccr41.ams03.atlas.cogentco.com
9 27.581 ms 154.54.77.246 - be2182.ccr21.lpl01.atlas.cogentco.com
10 96.965 ms 154.54.44.162 - be3042.ccr21.ymq01.atlas.cogentco.com
11 104.197 ms 154.54.44.105 - be2093.ccr22.yyz02.atlas.cogentco.com
12 111.496 ms 154.54.31.233 - be2994.ccr22.cle04.atlas.cogentco.com
13 119.405 ms 154.54.7.129 - be2718.ccr42.ord01.atlas.cogentco.com
14 129.983 ms 154.54.42.165 - be2831.ccr21.mci01.atlas.cogentco.com
15 140.302 ms 154.54.3.133 - be2432.ccr21.dfw01.atlas.cogentco.com
16 141.416 ms 154.54.6.114 - be2939.rcr21.dfw04.atlas.cogentco.com
17 142.433 ms 154.24.9.206 - te0-0-2-0.nr11.b028597-0.dfw04.atlas.cogentco.com
(me , starting at the cogent handoff)
be3056.ccr41.lax05.atlas.cogentco.com (154.54.10.65) 11.535 ms 18.414 ms 12.527 ms
be3033.ccr22.lax01.atlas.cogentco.com (154.54.26.41) 12.526 ms be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 13.910 ms be3033.ccr22.lax01.atlas.cogentco.com (154.54.26.41) 12.444 ms
be2932.ccr22.phx02.atlas.cogentco.com (154.54.45.161) 23.577 ms 23.597 ms be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 23.761 ms
be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 31.687 ms 31.708 ms be2930.ccr21.elp01.atlas.cogentco.com (154.54.42.78) 31.672 ms
be2928.ccr42.iah01.atlas.cogentco.com (154.54.30.161) 49.434 ms be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 49.453 ms 50.042 ms
be2441.ccr21.dfw01.atlas.cogentco.com (154.54.41.66) 50.116 ms 50.072 ms 49.603 ms
be2939.rcr21.dfw04.atlas.cogentco.com (154.54.6.114) 49.900 ms be2938.rcr21.dfw04.atlas.cogentco.com (66.28.4.18) 49.856 ms 50.228 ms
te0-0-2-0.nr11.b028597-0.dfw04.atlas.cogentco.com (154.24.9.206) 51.023 ms te0-0-2-1.nr11.b028597-0.dfw04.atlas.cogentco.com (154.24.9.210) 50.970 ms 50.913 ms 15 38.140.236.58 (38.140.236.58) 51.265 ms 51.219 ms 51.162 ms
199.231.224.66 (199.231.224.66) 51.507 ms 51.516 ms 51.500 ms
@Alexpux can you provide a traceroute? Obviously not looking for your IP - just the last cogentco.com parts - I'll have to get in touch with cogent's netengs. What a waste of time, damn cogent. Any info you have though will help.
traceroute repo.msys2.org
traceroute to diablo.msys2.org (45.59.69.178), 64 hops max, 52 byte packets
1 www.asusnetwork.net (192.168.1.1) 2.331 ms 1.925 ms 1.243 ms
2 ip1-22.ethernet.wplus.ru (94.188.22.1) 3.641 ms 51.659 ms 19.550 ms
3 195.131.236.1 (195.131.236.1) 8.445 ms 24.546 ms 28.102 ms
4 195.131.233.1 (195.131.233.1) 10.789 ms 5.308 ms 465.031 ms
5 212.1.239.142 (212.1.239.142) 18.872 ms 4.390 ms 6.453 ms
6 212.1.251.112 (212.1.251.112) 57.586 ms 112.283 ms 39.881 ms
7 be4766.nr21.b015761-2.fra06.atlas.cogentco.com (149.14.69.217) 38.618 ms 54.065 ms 55.271 ms
8 154.25.9.45 (154.25.9.45) 50.199 ms 92.730 ms 70.771 ms
9 be2845.ccr41.fra03.atlas.cogentco.com (154.54.56.189) 45.599 ms
be2846.ccr42.fra03.atlas.cogentco.com (154.54.37.29) 42.837 ms 40.281 ms
10 be2813.ccr41.ams03.atlas.cogentco.com (130.117.0.121) 63.224 ms
be2814.ccr42.ams03.atlas.cogentco.com (130.117.0.141) 83.665 ms 70.413 ms
11 be2183.ccr22.lpl01.atlas.cogentco.com (154.54.58.69) 55.178 ms
be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 65.579 ms
be2183.ccr22.lpl01.atlas.cogentco.com (154.54.58.69) 56.234 ms
12 be3042.ccr21.ymq01.atlas.cogentco.com (154.54.44.162) 127.201 ms 132.942 ms
be3043.ccr22.ymq01.atlas.cogentco.com (154.54.44.166) 163.625 ms
13 be2090.ccr21.yyz02.atlas.cogentco.com (154.54.30.205) 151.305 ms 150.265 ms 296.119 ms
14 be2993.ccr21.cle04.atlas.cogentco.com (154.54.31.225) 229.550 ms
be2994.ccr22.cle04.atlas.cogentco.com (154.54.31.233) 150.223 ms 158.959 ms
15 be2718.ccr42.ord01.atlas.cogentco.com (154.54.7.129) 155.782 ms 154.103 ms
be2717.ccr41.ord01.atlas.cogentco.com (154.54.6.221) 152.943 ms
16 be2831.ccr21.mci01.atlas.cogentco.com (154.54.42.165) 174.320 ms
be2832.ccr22.mci01.atlas.cogentco.com (154.54.44.169) 167.216 ms 181.790 ms
17 be2432.ccr21.dfw01.atlas.cogentco.com (154.54.3.133) 202.572 ms
be2433.ccr22.dfw01.atlas.cogentco.com (154.54.3.213) 189.377 ms
be2432.ccr21.dfw01.atlas.cogentco.com (154.54.3.133) 178.237 ms
18 be2938.rcr21.dfw04.atlas.cogentco.com (66.28.4.18) 189.496 ms
be2939.rcr21.dfw04.atlas.cogentco.com (154.54.6.114) 206.137 ms
be2938.rcr21.dfw04.atlas.cogentco.com (66.28.4.18) 183.024 ms
19 te0-0-2-0.nr11.b028597-0.dfw04.atlas.cogentco.com (154.24.9.206) 245.993 ms 520.058 ms
te0-0-2-1.nr11.b028597-0.dfw04.atlas.cogentco.com (154.24.9.210) 177.510 ms
20 38.140.236.58 (38.140.236.58) 184.769 ms 191.194 ms 211.692 ms
21 199.231.224.66 (199.231.224.66) 171.785 ms 187.094 ms 175.872 ms
22 45.59.69.178 (45.59.69.178) 174.942 ms 211.374 ms 250.055 ms
@Alexpux Ok - thanks, I will get in touch with them, if not today, then tomorrow, maybe this will help others, I know it isn't local - probably some source based stuff either my ISP or cogent is doing. I'll know soon.
This is happening to me today, same results. Good to know it's probably not a local issue but frustrating. @erichiller Did you ever find more information?
Closing. I don't think we can do anything with this, but if someone thinks of something, I'm all ears.
Also, there are mirrors.
@dakotahawkins It is definitely an ISP / route-specific issue - I had a neighbour who also has Old Time Warner (now Charter) and it doesn't work there either. Here's his tests:
ping
ping repo.msys2.org
PING diablo.msys2.org (45.59.69.178): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^C
--- diablo.msys2.org ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
traceroute
traceroute repo.msys2.org
traceroute to diablo.msys2.org (45.59.69.178), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.1) 1.042 ms 0.898 ms 1.002 ms
2 142.254.236.25 (142.254.236.25) 17.630 ms 13.543 ms 9.227 ms
3 76.167.31.245 (76.167.31.245) 9.707 ms 10.074 ms 14.003 ms
4 agg20.lamrcadq02r.socal.rr.com (72.129.10.130) 10.706 ms 14.958 ms 11.831 ms
5 agg28.tustcaft01r.socal.rr.com (72.129.9.2) 15.656 ms 16.098 ms 16.098 ms
6 bu-ether16.tustca4200w-bcr00.tbone.rr.com (66.109.6.64) 17.233 ms 16.323 ms 16.171 ms
7 0.ae1.pr0.lax10.tbone.rr.com (66.109.6.131) 12.216 ms
0.ae5.pr0.lax10.tbone.rr.com (107.14.19.121) 11.402 ms
0.ae1.pr0.lax10.tbone.rr.com (66.109.6.131) 11.323 ms
8 be3056.ccr41.lax05.atlas.cogentco.com (154.54.10.65) 12.135 ms 13.295 ms 16.824 ms
9 be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 18.262 ms
be3033.ccr22.lax01.atlas.cogentco.com (154.54.26.41) 13.633 ms
be3032.ccr21.lax01.atlas.cogentco.com (154.54.31.53) 12.758 ms
10 be2932.ccr22.phx02.atlas.cogentco.com (154.54.45.161) 24.365 ms
be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 23.291 ms
be2932.ccr22.phx02.atlas.cogentco.com (154.54.45.161) 23.765 ms
11 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 31.375 ms
be2930.ccr21.elp01.atlas.cogentco.com (154.54.42.78) 32.035 ms
be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 33.777 ms
12 be2928.ccr42.iah01.atlas.cogentco.com (154.54.30.161) 48.615 ms
be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 49.630 ms
be2928.ccr42.iah01.atlas.cogentco.com (154.54.30.161) 49.311 ms
13 be2443.ccr22.dfw01.atlas.cogentco.com (154.54.44.230) 49.423 ms
be2441.ccr21.dfw01.atlas.cogentco.com (154.54.41.66) 49.202 ms
be2443.ccr22.dfw01.atlas.cogentco.com (154.54.44.230) 49.494 ms
14 be2939.rcr21.dfw04.atlas.cogentco.com (154.54.6.114) 52.814 ms
be2938.rcr21.dfw04.atlas.cogentco.com (66.28.4.18) 50.845 ms
be2939.rcr21.dfw04.atlas.cogentco.com (154.54.6.114) 50.356 ms
15 te0-0-2-1.nr11.b028597-0.dfw04.atlas.cogentco.com (154.24.9.210) 52.157 ms 52.073 ms
te0-0-2-0.nr11.b028597-0.dfw04.atlas.cogentco.com (154.24.9.206) 51.462 ms
16 38.140.236.58 (38.140.236.58) 51.169 ms 51.560 ms 51.830 ms
17 199.231.224.66 (199.231.224.66) 51.564 ms 51.622 ms 51.293 ms
18 * * *
1/4 mile away my work's connection operates fine (they are most definitely not TWTC).
from there:
traceroute
Tracing route to diablo.msys2.org [45.59.69.178]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.202.78.1
2 1 ms 1 ms 1 ms 10.202.2.9
3 1 ms 1 ms 1 ms 192.91.144.3
4 2 ms 2 ms 2 ms 1-1-5.mpr2.lax12.us.zip.zayo.com [208.185.22.53]
5 2 ms 2 ms 2 ms ae14.cs1.lax112.us.eth.zayo.com [64.125.27.40]
6 2 ms 2 ms 2 ms ae1.mpr2.lax12.us.zip.zayo.com [64.125.28.231]
7 2 ms 2 ms 2 ms be6461.ccr41.lax05.atlas.cogentco.com [154.54.11.13]
8 3 ms 2 ms 3 ms be3033.ccr22.lax01.atlas.cogentco.com [154.54.26.41]
9 14 ms 14 ms 14 ms be2932.ccr22.phx02.atlas.cogentco.com [154.54.45.161]
10 22 ms 22 ms 22 ms be2930.ccr21.elp01.atlas.cogentco.com [154.54.42.78]
11 36 ms 36 ms 36 ms be2928.ccr42.iah01.atlas.cogentco.com [154.54.30.161]
12 36 ms 36 ms 36 ms be2443.ccr22.dfw01.atlas.cogentco.com [154.54.44.230]
13 37 ms 37 ms 37 ms be2939.rcr21.dfw04.atlas.cogentco.com [154.54.6.114]
14 37 ms 37 ms 38 ms te0-0-2-1.nr11.b028597-0.dfw04.atlas.cogentco.com [154.24.9.210]
15 38 ms 37 ms 38 ms 38.140.236.58
16 44 ms 56 ms 38 ms 199.231.224.66
17 37 ms 37 ms 37 ms 45.59.69.178
@erichiller I have old TWC at home as well. I contacted them (in case it was my specific dynamic IP) and apparently I won't be assigned a new IP until next month.
What's strange is that we're all getting to the same next-to-last node in the route, and then it either fails or succeeds to get a response from diablo.msys2.org.
@elieux The fact that it only fails when it gets to diablo.msys2.org is what makes me think that perhaps you could do something about it! What that thing is, I don't know, but I don't know how that server is configured either. Perhaps an over-zealous blacklist? Maybe we happen to have dynamic IPs that used to be assigned to people who actually belong on a blacklist?
@dakotahawkins, yeah, that is plausible. I'll ask around and see what I can do.
So far it doesn't seem like anything's wrong with/on the server. The hosting company will be adding another uplink connection from another ISP in ~2 months, which -- I hope -- will work around any Cogent-related issues.
@elieux If you think the server logs something that might be useful I could always try to ping it while you look. Very weird for it to get all the way to the end of the route and fail, but I guess it could be either the next-to-last hop failing to hit the server or the server refusing the connections.
I have the same issue.
With ISP1,
11 * 273 ms * ionity-11.edge3.dal006.pnap.net [63.251.44.10]
12 270 ms 270 ms 270 ms 199.231.224.66
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * 185 ms if-ae-32-2.tcore2.NTO-New-York.as6453.net [63.243.216.22]
18 * 201 ms 195 ms if-ae-12-2.tcore1.N75-New-York.as6453.net [66.110.96.5]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 244 ms * * edge3.ae1-edgenet.dal006.pnap.net [107.150.140.178]
29 * * * Request timed out.
30 * * * Request timed out.
With ISP2,
15 268 ms 268 ms 266 ms ionity-11.edge3.dal006.pnap.net [63.251.44.10]
16 270 ms 270 ms 269 ms 199.231.224.66
17 280 ms 272 ms 280 ms 45.59.69.178
Both tests, at the same location. The fact that it works up to the next-to-last hop suggests something to do with diablo.msys2.org
It's NOD32!
haha thats global issue
Experiencing similar results here on TWC in so-cal. Any updates on what's causing this?
I am unable to reach repo.msys2.org.
Unsure if this is related to whatever issue caused #163 , but the diagnostics I have done say it is down.
http://repo.msys2.org/mingw/i686/
is unreachabledebug output:
(output continues just checking packages)
I've run all of
pacman -Sy && pacman -S pacman-mirrors
pacman -Su
pacman -Syuu
Not sure what to think at this point. anyone else experiencing this?