|
i experience problems too. Problem located in 12th line
Tracing route to gofuckyourself.net [66.60.188.248]
over a maximum of 30 hops:
1 181 ms 160 ms 160 ms loop00-noc01.cos.internet.gr [62.1.255.203]
2 160 ms 160 ms 160 ms vlan81-csr02.core.internet.gr [62.1.0.227]
3 180 ms 160 ms 161 ms fasteth10-noc01.core.internet.gr [62.1.0.1]
4 170 ms 161 ms 160 ms athens5.gr.eqip.net [195.90.65.237]
5 260 ms 280 ms 261 ms london2.gb.eqip.net [195.206.64.133]
6 280 ms 280 ms 241 ms london50.gb.eqip.net [195.206.64.37]
7 291 ms 300 ms 281 ms amsterdam11.nl.eqip.net [195.206.64.157]
8 260 ms 261 ms 400 ms pos4-0-1-155M.br1.AMS2.gblx.net [62.8.32.109]
9 260 ms 261 ms 280 ms so3-1-0-622M.cr2.AMS2.gblx.net [62.8.32.61]
10 601 ms 461 ms 420 ms pos1-0-622M.cr2.SFO1.gblx.net [206.132.110.126]
11 440 ms 461 ms 421 ms pos4-0-0-155M.ar2.SFO1.gblx.net [206.251.1.201]
12 * * * Request timed out.
13 440 ms 421 ms 441 ms 7513-1.net.surewest.net [208.45.228.240]
14 441 ms 461 ms 420 ms 254.100MB.firstname.com [66.60.131.254]
15 461 ms 440 ms 440 ms 66.60.188.248
Trace complete.
Pinging gofuckyourself.net [66.60.188.248] with 32 bytes of data:
Reply from 66.60.188.248: bytes=32 time=541ms TTL=111
Reply from 66.60.188.248: bytes=32 time=401ms TTL=111
Reply from 66.60.188.248: bytes=32 time=430ms TTL=111
Reply from 66.60.188.248: bytes=32 time=431ms TTL=111
Ping statistics for 66.60.188.248:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 401ms, Maximum = 541ms, Average = 450ms
|