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.

[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.

[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

[DSanchez]

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

Yes, the problem appears to be with one or more of their routers.

[DanteMog]

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.

If thats true try being Aussie with 250 - 400+ in every mmo, that would open your eyes on whats a good ping time..

[Kisik]

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.

I think perhaps, anything under 40-50 is low, that's no where near what high ping is considered.

[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.