You are not logged in.
Hi guys...I have very big problem...one week ago I lost connection to archlinux.org.
Traceroute archlinux.org say:
1 mihairu (192.168.152.4) 0.413 ms 0.299 ms 0.288 ms
2 192.168.152.1 (192.168.152.1) 21.137 ms 6.176 ms 2.964 ms
3 213.29.11.1 (213.29.11.1) 3.566 ms 3.155 ms 2.707 ms
4 62.84.143.5 (62.84.143.5) 7.835 ms 16.050 ms 43.567 ms
5 fra-tr1-p1-1-0-3.gtsce.net (195.39.208.81) 20.980 ms 21.853 ms 23.391 ms
6 decix.mpd01.fra03.atlas.cogentco.com (80.81.192.63) 66.667 ms 52.989 ms 51.520 ms
7 g9-0-0.core01.fra03.atlas.cogentco.com (130.117.0.1) 26.322 ms 32.531 ms 23.944 ms
8 * * *
9 p13-0.core01.par01.atlas.cogentco.com (130.117.1.137) 115.934 ms 113.441 ms 117.035 ms
10 t2-3.mpd02.par01.atlas.cogentco.com (130.117.2.50) 137.813 ms 146.916 ms 114.648 ms
11 * t8-4.mpd01.dca01.atlas.cogentco.com (130.117.2.102) 114.726 ms 114.630 ms
12 t7-1.ccr02.dca01.atlas.cogentco.com (154.54.7.234) 116.755 ms 120.639 ms 118.891 ms
13 g1-0-0.core01.dca01.atlas.cogentco.com (154.54.3.157) 114.547 ms 170.192 ms 116.082 ms
14 p15-0.core02.dca01.atlas.cogentco.com (66.28.4.22) 115.082 ms 114.578 ms 114.183 ms
15 t3-1.mpd01.dca01.atlas.cogentco.com (154.54.5.50) 118.545 ms 116.837 ms 115.309 ms
16 t8-1.mpd01.dca02.atlas.cogentco.com (154.54.1.70) 122.411 ms 120.427 ms 212.395 ms
17 v3495.mpd01.iad01.atlas.cogentco.com (154.54.5.62) 331.412 ms 357.301 ms 244.338 ms
18 g9-0-0-3492.core01.iad01.atlas.cogentco.com (154.54.3.221) 219.599 ms 118.356 ms 118.202 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Ping:
PING archlinux.org (66.211.213.17) 56(84) bytes of data.
anyone who knows, where could be a problem?
my outer IP: 62.209.230.5
Proud to be ArchLinux64 user.
configs: http://github.com/Mihairu/config-files/tree/master
current desktop: here
Offline
Last sunday i had a similar problem for several hours, but since then i've been able to access the site without problems.
The trace route i took on sunday looked very similar to yours, this is the current traceroute :
traceroute www.archlinux.org
traceroute to archlinux.org (66.211.213.17), 30 hops max, 40 byte packets
1 SpeedTouch.lan (10.0.0.138) 1.274 ms 0.592 ms 0.533 ms
2 195.190.249.72 (195.190.249.72) 6.038 ms 5.794 ms 5.363 ms
3 42.ge-2-1-0.xr4.3d12.xs4all.net (194.109.5.105) 10.602 ms 10.084 ms 10.452 ms
4 0.so-6-0-0.xr1.tc2.xs4all.net (194.109.5.10) 10.685 ms 10.382 ms 10.586 ms
5 po1.ccr01.ams03.atlas.cogentco.com (195.69.144.124) 10.763 ms 10.122 ms 10.415 ms
6 t10-0-0.core01.ams03.atlas.cogentco.com (130.117.0.237) 10.989 ms 10.375 ms 10.677 ms
7 p1-0.core02.lon01.atlas.cogentco.com (130.117.1.110) 19.360 ms 18.609 ms 19.077 ms
8 p9-0.core02.jfk02.atlas.cogentco.com (66.28.4.253) 93.196 ms 93.317 ms 93.327 ms
9 t3-3.mpd03.jfk02.atlas.cogentco.com (154.54.5.234) 285.302 ms 93.844 ms 94.304 ms
10 t3-3.ccr02.dca01.atlas.cogentco.com (154.54.5.246) 280.900 ms 195.153 ms 222.152 ms
11 t4-1.mpd01.dca02.atlas.cogentco.com (154.54.2.182) 281.895 ms 107.159 ms 207.615 ms
12 t1-4.mpd01.iad01.atlas.cogentco.com (154.54.7.162) 97.638 ms 97.076 ms 97.103 ms
13 g2-0-0-3491.core01.iad01.atlas.cogentco.com (154.54.5.33) 101.177 ms 100.756 ms 100.987 ms
14 p3-0.core01.pit02.atlas.cogentco.com (154.54.3.26) 106.384 ms 106.085 ms 106.379 ms
15 g0-2.na01.b016102-1.pit02.atlas.cogentco.com (38.112.37.166) 103.762 ms 103.124 ms 102.937 ms
16 Velocity_dot_net.demarc.cogentco.com (38.112.28.14) 107.668 ms 107.776 ms 107.442 ms
17 66-211-254-1.velocity.net (66.211.254.1) 115.247 ms 114.586 ms 116.485 ms
18 66-211-250-2.velocity.net (66.211.250.2) 117.538 ms 115.447 ms 115.497 ms
19 66-211-213-17.velocity.net (66.211.213.17) 114.927 ms 115.741 ms 113.974 ms
I have heard of similar problems accessing some US sites over the past months , and it appears the problem occurs when one or more of the routers along the route are under heavy load.
In this case it would be the routers in the 154.54.x.x part.
As enduser there seem to be only 2 options :
- wait until the route works again (waiting period can vary between a few minutes and several days)
- use a proxy in a different country so the site is accessed over another route (hopefully one without problems)
Edit : for some reason it's usually europeans who have this trouble
Last edited by Lone_Wolf (2007-11-20 22:04:35)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I've had the same problem for 2 days, I just got it back a few minutes ago. It's the second time this happens, I really wonder what might be causing this...
Have you Syued today?
Free music for free people! | Earthlings
"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery
Offline
I had the same problem this weekend, it "solved itself" yesterday (nov 19) afternoon. My traceroutes also indicated problems with (or maybe rather one hop beyond) a Cogent router, in my case g14-0-0.core01.iad01.atlas.cogentco.com (154.54.5.57). I tested tracerouteing to www.archlinux.org from different locations using their Looking Glass, and noticed that all Europe routers except for one of them (I think it was the one in Amsterdam) could get to www.archlinux.org.
Anyway, I just wanted to say "+1" and point to the Looking Glass page (for people to test in case this happens again)
Offline
The problem was with cogent.
The "solving itself" was cogent fixing their problem.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Thanks cactus, now I feel a bit better since I know where the problem was
Have you Syued today?
Free music for free people! | Earthlings
"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery
Offline
The problem was with cogent.
The "solving itself" was cogent fixing their problem.
Yes, of course it was, if it sounded like I implied otherwise, I apologize.
Offline