
Originally Posted by
bebop_bo
heres my ping from EVE server:
Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=22ms TTL=245
Reply from 87.237.38.200: bytes=32 time=22ms TTL=245
Reply from 87.237.38.200: bytes=32 time=22ms TTL=245
Reply from 87.237.38.200: bytes=32 time=28ms TTL=245
Ping statistics for 87.237.38.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 28ms, Average = 23ms
& now my ping from FFXIV server done 2 sec later:
Pinging 199.91.189.39 with 32 bytes of data:
Reply from 199.91.189.39: bytes=32 time=181ms TTL=238
Reply from 199.91.189.39: bytes=32 time=184ms TTL=238
Request timed out.
Reply from 199.91.189.39: bytes=32 time=184ms TTL=238
Ping statistics for 199.91.189.39:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 181ms, Maximum = 184ms, Average = 183ms
gogo SE!
Well, for starters, that server is in Iceland and not Montreal.
http://myip.ms/info/whois/87.237.38.200
And there are many of us in the US who have had latency issues with their servers in the past. Especially the DUST514 players... omg, that was nightmarish at times.
And a single ping does not tell much either. You stand a better chance of seeing something useful in a pathping, or at least a tracert. For example, from my system:
Code:
Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
<Initial hops removed for security>
4 29 ms 26 ms 30 ms 24.93.64.128
5 32 ms 34 ms 34 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 32 ms * 32 ms ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
7 36 ms * 40 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
8 116 ms 116 ms 133 ms if-3-2.tcore2.NJY-Newark.as6453.net [216.6.87.10]
9 111 ms 111 ms 114 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1]
10 162 ms 116 ms 141 ms if-7-2.tcore1.L78-London.as6453.net [66.198.70.26]
11 119 ms 119 ms 124 ms if-1-2.tcore2.L78-London.as6453.net [80.231.130.122]
12 120 ms 121 ms 119 ms if-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
13 113 ms 113 ms 111 ms if-4-0-0.core4.LDN-London.as6453.net [80.231.62.26]
14 110 ms 110 ms 110 ms ix-12-0-0-3046.core4.LDN-London.as6453.net [195.219.67.246]
15 111 ms 110 ms 110 ms srv246-f.ccp.cc [87.237.37.246]
16 115 ms 117 ms 112 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete.
Code:
Tracing route to 199.91.189.39 over a maximum of 30 hops
4 29 ms 30 ms 26 ms 24.93.64.124
5 34 ms 34 ms 34 ms 107.14.19.20
6 32 ms * 33 ms ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
7 36 ms 34 ms 37 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
8 57 ms 55 ms 58 ms if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
9 55 ms 56 ms 58 ms 64.86.85.1
10 56 ms 55 ms 53 ms if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86.32.33]
11 57 ms 64 ms 62 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
12 57 ms 56 ms 55 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
13 63 ms 67 ms 55 ms 66.198.96.50
14 66 ms 57 ms 59 ms 192.34.76.2
15 56 ms 64 ms 69 ms 199.91.189.234
16 55 ms 55 ms 53 ms 199.91.189.39
Trace complete.
Notice how when tracing to both the IP's you gave, there are problems in the DC/VA area? It's going tit's up with potential packet loss or extensive delays around the handoff from my ISP to their routing partner, TATA--one of the handful of third party ISP's that are at the root of a LOT of users problems with this game. The fact that shaping rules are causing ICMP to get clamped down at that point is evidence there may be a congestion problem around that section of the route.
That is what we are talking about--trying to get some accountability from these middle-men that are dropping the ball.