How do you check your ping?

[Nagashi]

How do you check your ping?

[Rexcaldur]

Windows Key + R
Type "resmon"
Tab "Network"
Click "FFXIV"
Look under "TCP Connections" and you will see two FFXIV entries showing you the ping.

A fc mate showed me this.

[Nagashi]

Thanks you!

[Ulathskullsplitter]

Windows Key + R
Type "resmon"
Tab "Network"
Click "FFXIV"
Look under "TCP Connections" and you will see two FFXIV entries showing you the ping.

A fc mate showed me this.

Interesting. So according to that mine is between 150-160ms. Thought it would be better from the chicago area to montreal.

[DSanchez]

Interesting. So according to that mine is between 150-160ms. Thought it would be better from the chicago area to montreal.

Anything higher than 40-50 is high and you can do a pathping {ip address} from your command prompt to see where that latency is coming from.

[Ulathskullsplitter]

Anything higher than 40-50 is high and you can do a pathping {ip address} from your command prompt to see where that latency is coming from.

Ok so how do i interpret this. It looks like the problem is right at the end with SE?

Tracing route to 199.91.189.25 over a maximum of 30 hops

0 .in.comcast.net. [10.0.0.5]
1 10.0.0.1
2 24.12.32.1
3 68.86.114.229
4 te-1-8-0-4-ar01.area4.il.chicago.comcast.net [68.87.230.157]
5 he-3-6-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.95.9]
6 ix-0-2-2-0.tcore1.CT8-Chicago.as6453.net [64.86.137.45]
7 if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
8 if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
9 66.198.96.50
10 192.34.76.2
11 199.91.189.234
12 199.91.189.25

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 .in.comcast.net. [10.0.0.5]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 24.12.32.1
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 68.86.114.229
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% te-1-8-0-4-ar01.area4.il.chicago.comcast.net [68.87.230.157]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% he-3-6-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.95.9]
0/ 100 = 0% |
6 13ms 0/ 100 = 0% 0/ 100 = 0% ix-0-2-2-0.tcore1.CT8-Chicago.as6453.net [64.86.137.45]
0/ 100 = 0% |
7 13ms 0/ 100 = 0% 0/ 100 = 0% if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
0/ 100 = 0% |
8 42ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
0/ 100 = 0% |
9 107ms 3/ 100 = 3% 3/ 100 = 3% 66.198.96.50
0/ 100 = 0% |
10 38ms 1/ 100 = 1% 1/ 100 = 1% 192.34.76.2
0/ 100 = 0% |
11 111ms 5/ 100 = 5% 5/ 100 = 5% 199.91.189.234
0/ 100 = 0% |
12 36ms 0/ 100 = 0% 0/ 100 = 0% 199.91.189.25

Trace complete.

[Pygar]

Interesting. So according to that mine is between 150-160ms. Thought it would be better from the chicago area to montreal.

I am not sure, but I believe it is at this point, a Comcast problem.

If you check routes to comcast.com (not.net) and you will see some issues there as well. I have someone looking into it from dslreports.com but Comcast are doing some major network updates nation wide that probably account for routing issues.

I'm in Chicago as well and have the exact same problem.

[AdvancedWind]

Interesting. So according to that mine is between 150-160ms. Thought it would be better from the chicago area to montreal.

Something must be wrong there, I sometimes get this ping all the way from Brazil.

[Hobo]

Ok so how do i interpret this. It looks like the problem is right at the end with SE?

Well now we know your name is Tom or ... at the very least you're using Tom's computer haha

[Eli_Jin]

PingPlotter freeware is also a nifty tool that does min/max/avg ping with tracert showing packet loss at each router hop, and has nifty graphs.

All you need to do is plug in the FFXIV IP (199.91.189.25 from above) and enjoy. A while back I let it run each night at different times. I'm with Time Warner and the last hop out of their network space tbone.rr.com to atlas.cogentco.com routers is dropping between 2% up to a whopping 49% of packets, depending on time of day. The final hops to Montreal data center (via mtl.iweb.com) have no loss for me.

Good thing I'm switching ISPs very soon to a different fiber backbone than Time Warner's Road Runner. I bet much of the "server lag" people complain about is their own ISP, or the routing through eastern NA right now, dropping packets. I've seen definite lag on server side events as well, like demon wall push back delayed 5 seconds with battle continuing normally, so their servers aren't perfect either.