For Those with Time Warner Cable( Lag Issue)

[Gamersciz]

I live in LA and just recently moved and practically my only internet option is TWC. However, FF is the only game I have problems with. I have played on east coast servers with other games such as CSS and TF2 and even Battlefield. Never had a problem having just over 100ms ping. But it's gotten so bad that being my main a PLD I can't get past T2 with the lag that I get. I have since given up on my group as it wasn't fair that I would miss a silence on ADS and we would wipe because of it. Personally I don't think it's TWC that is the problem.

The problem is SE and their logic to place the only data center for North America way the hell north east into montreal. I don't care if I had FiOS max speed of 300DL and around 75UL. I would still have lag simply because the server is so damn far away. The tracert is only half the issue.

FYI to either ping or tracert your server check out www.arrstatus.com to get the correct IP for your server. Below is my tracert for Catcuar...im screwed for Coil.

Tracing route to 199.91.189.23 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 31 ms 20 ms 29 ms cpe-172-251-64-1.socal.res.rr.com [172.251.64.1]

3 9 ms 9 ms 16 ms tge0-7-0-18.lsaicaev02h.socal.rr.com [76.166.24.
141]
4 10 ms 11 ms 11 ms agg11.lsaicaev02r.socal.rr.com [72.129.18.194]
5 19 ms 12 ms 11 ms agg26.tustcaft01r.socal.rr.com [72.129.17.2]
6 12 ms 17 ms 11 ms 107.14.17.134
7 11 ms 15 ms 12 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
8 10 ms 9 ms 13 ms 66.109.9.122
9 85 ms 86 ms 86 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

10 92 ms 85 ms 86 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
11 85 ms 86 ms 89 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 85 ms 85 ms 86 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 85 ms 86 ms 85 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 84 ms 86 ms 86 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 86 ms 88 ms 86 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

16 91 ms 88 ms 89 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
17 84 ms 86 ms * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 84 ms 92 ms 89 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 115 ms 118 ms 117 ms 10.2.2.1
20 116 ms 117 ms 118 ms 192.34.76.2
21 117 ms 119 ms 122 ms 199.91.189.234
22 * 104 ms 101 ms 199.91.189.23

Trace complete.

[ZohnoReecho]

I live in LA and just recently moved and practically my only internet option is TWC. However, FF is the only game I have problems with. I have played on east coast servers with other games such as CSS and TF2 and even Battlefield. Never had a problem having just over 100ms ping. But it's gotten so bad that being my main a PLD I can't get past T2 with the lag that I get. I have since given up on my group as it wasn't fair that I would miss a silence on ADS and we would wipe because of it. Personally I don't think it's TWC that is the problem.

The problem is SE and their logic to place the only data center for North America way the hell north east into montreal. I don't care if I had FiOS max speed of 300DL and around 75UL. I would still have lag simply because the server is so damn far away. The tracert is only half the issue.

FYI to either ping or tracert your server check out www.arrstatus.com to get the correct IP for your server. Below is my tracert for Catcuar...im screwed for Coil.

I've a 130-200 ping from Italy and I can play fine. I think your issue is packets loss. Those "*" on nodes 17 and 22 mean that you lost packets, and in a short while too.
You have also some spikes at 2, 5 and 16; notice how some times they take longer to reply than their next node.
I suggest running tracert multiple times until you find the closest node at which your connection starts losing packets.

[Gamersciz]

I've a 130-200 ping from Italy and I can play fine. I think your issue is packets loss. Those "*" on nodes 17 and 22 mean that you lost packets, and in a short while too.
You have also some spikes at 2, 5 and 16; notice how some times they take longer to reply than their next node.
I suggest running tracert multiple times until you find the closest node at which your connection starts losing packets.

I am talking with TWC tech right now. I re-ran the tracert and came up with the following:

Tracing route to 199.91.189.23 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 21 ms 29 ms cpe-172-251-64-1.socal.res.rr.com [172.251.64.1]

3 8 ms 9 ms 9 ms tge0-7-0-18.lsaicaev02h.socal.rr.com [76.166.24.
141]
4 11 ms 12 ms 11 ms agg11.lsaicaev02r.socal.rr.com [72.129.18.194]
5 13 ms 12 ms 11 ms agg26.tustcaft01r.socal.rr.com [72.129.17.2]
6 10 ms 11 ms 12 ms 107.14.17.134
7 12 ms 9 ms 9 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
8 10 ms 9 ms 13 ms 66.109.9.122
9 88 ms 85 ms 86 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]

10 87 ms 85 ms 91 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
11 87 ms 85 ms 88 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 84 ms 86 ms 85 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 92 ms 85 ms 85 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 87 ms 85 ms 90 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 87 ms 85 ms 86 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

16 83 ms 86 ms 86 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
17 84 ms 86 ms 86 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 85 ms 92 ms 85 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 118 ms 117 ms 118 ms 10.2.2.1
20 118 ms 121 ms 117 ms 192.34.76.2
21 117 ms 118 ms 118 ms 199.91.189.234
22 101 ms 102 ms 101 ms 199.91.189.23

Trace complete.

At least it doesn't show any timeouts. But there is still a vast raise in ping while in my hometown which doesnt make sense. I will keep you updated.

[DontTouchMyHoHos]

I am talking with TWC tech right now. I re-ran the tracert and came up with the following:


At least it doesn't show any timeouts. But there is still a vast raise in ping while in my hometown which doesnt make sense. I will keep you updated.

You are miss reading that. #1 Is were you live number 22 is the destination.

[Gamersciz]

You are miss reading that. #1 Is were you live number 22 is the destination.

Oh I get that. It's the number 9 hop that confuses me. It's in Los Angeles still and jumps from 15ms to 85ms before even leaving my city. That's the part that doesn't make sense to me.

[Raist]

I live in LA and just recently moved and practically my only internet option is TWC. However, FF is the only game I have problems with. I have played on east coast servers with other games such as CSS and TF2 and even Battlefield. Never had a problem having just over 100ms ping. But it's gotten so bad that being my main a PLD I can't get past T2 with the lag that I get. I have since given up on my group as it wasn't fair that I would miss a silence on ADS and we would wipe because of it. Personally I don't think it's TWC that is the problem.

The problem is SE and their logic to place the only data center for North America way the hell north east into montreal. I don't care if I had FiOS max speed of 300DL and around 75UL. I would still have lag simply because the server is so damn far away. The tracert is only half the issue.

FYI to either ping or tracert your server check out www.arrstatus.com to get the correct IP for your server. Below is my tracert for Catcuar...im screwed for Coil.

Don't take those IP's at arrstatus as your actual server IP's. They have multiple front-ends for getting into the system, and then you get forwarded to the proper server for the current world/zone you are playing in. Your client may actually be connecting to a different IP then what is listed there. Note also that arrstatus has listed the same IP for different worlds (Adam, Faerie, Blamung all show the same IP address, and this happens for a few other IP's).

Open resmon and find the IP's your ffxiv is using, or run netstat in a CMD prompt while in game to verify for certain which one your client is actually using. For example, my client is connecting to .74, but arrstatus lists Midgard as .28.