Server-side "lag" not just EU

What I, and many like me have been experiencing for over the past month or longer, is NOT ping/latency related lag(that I can tell anyway). I am in the east coast US. First some background information.

1. I have a 30Mb connection. My ISP(Charter Communications) does not P2P throttle.
2. My rig (i5 3570k, 8GB Ram, Geforce 660 TI, Windows 7 Pro). No issues there.
3. Netstat -b shows 32+ TCP connections on various ports to ffxiv.exe. A tracert to the main IP (199.91.189.58) give me 125ms.
4. Depending on what they put in a hotfix/weekly patch the issue has seen improvement and has gotten very bad. Depends on the week.

I notice the issue the most while crafting or gathering. Click on a node or action, it will take 5-10 seconds to respond or put loot in my bags. Also, while raiding or doing a dungeon, I can move freely while everything else around me is either stopped or skipping 10 frames at a time. The best explanation of what happens is stop-action or claymation filming.

This really needs to be addressed.

Same issue here. SE have royally messed up in a recent patch.

im getting no lag and im on a NA server and in the EU

Code:

---

>pathping 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

 <initial hops removed for securitty>
  4  24.93.64.128
  5  107.14.19.42
  6  ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
  7  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  8  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
  9  64.86.85.1
 10  if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86.32.33]
 11  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 12  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 13  66.198.96.50
 14  192.34.76.2
 15  199.91.189.234
 16  199.91.189.58

Computing statistics for 400 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  4  30ms    24/ 100 = 24%    0/ 100 =  0%  24.93.64.128
                                0/ 100 =  0%  |
  5  35ms    24/ 100 = 24%    0/ 100 =  0%  107.14.19.42
                                0/ 100 =  0%  |
  6  33ms    24/ 100 = 24%    0/ 100 =  0%  ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
                                1/ 100 =  1%  |
  7  31ms    84/ 100 = 84%    59/ 100 = 59%  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
                                0/ 100 =  0%  |
  8  33ms    26/ 100 = 26%    1/ 100 =  1%  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
                                0/ 100 =  0%  |
  9  52ms    26/ 100 = 26%    1/ 100 =  1%  64.86.85.1
                                0/ 100 =  0%  |
 10  54ms    26/ 100 = 26%    1/ 100 =  1%  if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86.32.33]
                                0/ 100 =  0%  |
 11  68ms    25/ 100 = 25%    0/ 100 =  0%  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
                                0/ 100 =  0%  |
 12  77ms    25/ 100 = 25%    0/ 100 =  0%  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
                                0/ 100 =  0%  |
 13  74ms    25/ 100 = 25%    0/ 100 =  0%  66.198.96.50
                                0/ 100 =  0%  |
 14  75ms    25/ 100 = 25%    0/ 100 =  0%  192.34.76.2
                                0/ 100 =  0%  |
 15  83ms    25/ 100 = 25%    0/ 100 =  0%  199.91.189.234
                                0/ 100 =  0%  |
 16  80ms    25/ 100 = 25%    0/ 100 =  0%  199.91.189.58

Trace complete.

---

Just saying, you need to investigate what is really going on in your route before you claim there is no throttling going on. It may not be getting classified as P2P traffic, but in this trace, there is either some sort of traffic shaping going on or at least one router along the way is about to die. Either way, there is a strong possibility you have a problem in route that needs to be investigated.

To further illustrate the stability problems in route, here's the exact same test run again 15 minutes later from the same system:

Code:

---

>pathping 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops
<initial hops removed for security>
  4  24.93.64.128
  5  107.14.19.42
  6    *        *    ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
  7  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  8  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
  9  64.86.85.1
 10  if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86.32.33]
 11  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 12  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 13  66.198.96.50
 14  192.34.76.2
 15  199.91.189.234
 16  199.91.189.58

Computing statistics for 400 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
                                0/ 100 =  0%  |
  4  28ms    0/ 100 =  0%    0/ 100 =  0%  24.93.64.128
                                0/ 100 =  0%  |
  5  35ms    0/ 100 =  0%    0/ 100 =  0%  107.14.19.42
                                0/ 100 =  0%  |
  6  38ms    0/ 100 =  0%    0/ 100 =  0%  ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
                                0/ 100 =  0%  |
  7  ---    100/ 100 =100%  100/ 100 =100%  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
                                0/ 100 =  0%  |
  8  40ms    0/ 100 =  0%    0/ 100 =  0%  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
                                0/ 100 =  0%  |
  9  56ms    0/ 100 =  0%    0/ 100 =  0%  64.86.85.1
                                0/ 100 =  0%  |
 10  57ms    0/ 100 =  0%    0/ 100 =  0%  if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86.32.33]
                                0/ 100 =  0%  |
 11  69ms    0/ 100 =  0%    0/ 100 =  0%  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
                                0/ 100 =  0%  |
 12  79ms    0/ 100 =  0%    0/ 100 =  0%  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
                                0/ 100 =  0%  |
 13  79ms    0/ 100 =  0%    0/ 100 =  0%  66.198.96.50
                                0/ 100 =  0%  |
 14  80ms    0/ 100 =  0%    0/ 100 =  0%  192.34.76.2
                                0/ 100 =  0%  |
 15  84ms    0/ 100 =  0%    0/ 100 =  0%  199.91.189.234
                                0/ 100 =  0%  |
 16  83ms    0/ 100 =  0%    0/ 100 =  0%  199.91.189.58

Trace complete.

---

*note that no one else is on my network, only this PC is up, and the only thing I've done during this time is this thread in Firefox and the Dos Prompt for running pathping. System booted and AV updated while I fixed food and I've been eating while watching the news, not doing anything else on the system but running these tests and then posting in the thread.

Well OK, lets assume you are right and there is an issue with the trafic somewhere along the tracert. What can be done about this? All else being equal, I have never had any lag in LOTRO, SWTOR, GW2, AION, Secret World, or Wow. I am fairly certain these companies have their NA servers located in various places around the US. So does that indicate it is an issue with the location SE has chosen? With their backbone provider? If so, it is VERY unlikely that this issue will ever go away since moving/changing either of those would be very costly.

Hello,

If i may ask when did you play SWTOR last? This is not a snarky question :) If you take a peak on their forums, you will see that they have been having HUGE issues with lag (exactly the same symptoms as here) for a couple of months now. I played SWTOR without trouble too BUT that was before the problem with routing. Nowadays i see hundreds of gamers of my country still on that game and they cannot play just like us here. The same is happening in Diablo3, world of warcraft, world of tanks or star craft to name a few. It appears to be a "far-west" stand out between ISPs ; The Route Providers such as Cogent-tata and the companies using the internet for their content such as the gaming companies, google-youtube, even facebook is affected here in france, although many won't notice a small delay in http browsing. Nobody wants to pay for the traffic so it gets completly overloaded and we get our butts done.

Greetings,

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.