pure said:I don't think so , not all proxys workfrostyfrosty said:pure said:Yeah, can't connect to it either unless i use a proxy.. You can use a proxy webpage to connect to it.. isn't that fast but better than nothing just google for itharryk said:Quick trace route:
Code:ÂÂ7ÂÂÂÂ13 msÂÂÂÂ11 msÂÂÂÂ10 msÂÂvix2.core01.vie01.atlas.cogentco.com [193.203.0.113] ÂÂ8ÂÂÂÂ26 msÂÂÂÂ25 msÂÂÂÂ24 msÂÂte1-3.ccr01.muc01.atlas.cogentco.com [130.117.3.21] ÂÂ9ÂÂÂÂ80 msÂÂÂÂ23 msÂÂÂÂ24 msÂÂte2-2.ccr01.fra03.atlas.cogentco.com [130.117.0.65] 10ÂÂÂÂ31 msÂÂÂÂ31 msÂÂÂÂ30 msÂÂte7-1.ccr02.ams03.atlas.cogentco.com [130.117.2.230] 11ÂÂÂÂ41 msÂÂÂÂ40 msÂÂÂÂ40 msÂÂte7-4.ccr01.lon01.atlas.cogentco.com [130.117.1.225] 12ÂÂ 114 msÂÂ 113 msÂÂ 111 msÂÂte3-2.ccr01.jfk02.atlas.cogentco.com [66.28.4.189] 13ÂÂ 119 msÂÂ 119 msÂÂ 119 msÂÂte2-1.mpd01.dca01.atlas.cogentco.com [154.54.6.5] 14ÂÂ 148 msÂÂ 147 msÂÂ 144 msÂÂte3-2.mpd01.iah01.atlas.cogentco.com [154.54.5.202] 15ÂÂ 152 msÂÂ 152 msÂÂ 152 msÂÂte4-1.ccr01.aus01.atlas.cogentco.com [154.54.1.65] 16ÂÂ 173 msÂÂ 171 msÂÂ 171 msÂÂte4-1.ccr01.phx02.atlas.cogentco.com [154.54.1.166] 17ÂÂ 185 msÂÂ 178 msÂÂ 445 msÂÂte4-1.ccr01.san01.atlas.cogentco.com [154.54.7.86] 18ÂÂ 181 msÂÂ 178 msÂÂ 179 msÂÂvl3512.na21.b006463-1.san01.atlas.cogentco.com [38.20.33.126] 19ÂÂ 184 msÂÂ 181 msÂÂ 181 msÂÂge1-2.gw65-02.kmc01.sdcix.net [66.28.28.126] 20ÂÂ 188 msÂÂ 184 msÂÂ 185 msÂÂc5-po3.cari.net [216.98.153.25] 21ÂÂÂÂ *ÂÂÂÂÂÂÂÂ*ÂÂÂÂÂÂÂÂ*ÂÂÂÂ Request timed out. 22ÂÂÂÂ *ÂÂÂÂÂÂÂÂ*ÂÂÂÂÂÂÂÂ*ÂÂÂÂ Request timed out.
20 hops is quite much to begin with, and the reaction times are very high. Somehow I can't get any further. I would say the problem lies in the bad server link-up (connection).![]()
well if your able to proxy on through, then it sounds like the problem lies on your side.![]()
Also I'm not the only one with connectivity issues here ^.^
you guys are funny

















