Regarding high latency from Los Angeles/surrounding area

[Saikou]

What I can derive from what we know, the edits to the OP and the data that has been shown: Once your connection enters TATA airspace, ping goes to hell. Even if your connection doesn't go thought TATA, your ping will still go to hell once it reaches Montreal and likely even before that at whichever backbone connection is getting you into Canada. The problem with, er, the problem being TATA is that they do not talk to peons like us. It would take our ISP's or SE talking to TATA to get them to work on the packet loss issues with the routes controlled by them. And even if TATA fixed its issues, there's still the problem of severe packet loss happening at the datacenter itself.

I live in Washington State and my ISP is Comcast.

I experience positional update lag and input lag all the time. Occasionally there is rubberbanding. As an example of positional update lag, I can almost never avoid magitek cannon in Castrum Meridianum or Keeper of Halidom's targeted AOE in Wanderer's Palace.

As you can see, my latency isn't anywhere near as bad as the OP or anyone else in SoCal being routed through TATA's Palo Alto or San Jose routers. It is, however, notably worse than my experience with WoW, SWTOR, Rift, and Terra. In battles where seconds matter, like Titan and Binding coil, this is very frustrating.

Based on the following:

http://www.reddit.com/r/ffxiv/commen...th_lag_repost/

http://forums.timewarnercable.com/t5...rnia/td-p/9059

Some of the first chokepoints are owned by consumer grade ISP's (comcast, time warner, fios, etc). But the bigger problem comes with the routes controlled by business tier ISP's: TATA, Cogentco, and Tinet. Almost everybody is running into a router inside their network where packet loss, and therefore positional lag (hit by voidzones you weren't in), input lag (you hit the button and the ability doesn't go off until several seconds later), and rubberbanding (the game seems to freeze and then all the actions that happened in the frozen period happen rapidly as your computer catches up to everything it missed), is happening.

I fear that SE's intervention may be our only hope for getting both tiers of ISPs to do something, as most of us who have either been brushed off or given the run-around.

My own Tracert

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 4 ms 4 ms 3 ms 192.168.1.1
2 11 ms 12 ms 11 ms 73.104.212.1
3 11 ms 14 ms 17 ms 68.85.240.37
4 16 ms 17 ms 15 ms ae-41-0-ar03.burien.wa.seattle.comcast.net [69.1
39.164.29]
5 87 ms 34 ms 15 ms ae-41-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.33] ((Comcast is having data loss issues of it's own))
6 17 ms 16 ms 15 ms he-1-12-0-0-11-cr01.seattle.wa.ibone.comcast.net
[68.86.93.177]
7 14 ms 16 ms * ix-7-2-2-0.tcore1.00S-Seattle.as6453.net [64.86.
123.33] ((Entering TATA airspace...))
8 18 ms 19 ms 20 ms if-13-0-0-4.core1.00S-Seattle.as6453.net [64.86.
124.13]
9 89 ms 87 ms 87 ms if-8-1-2-4.tcore2.CT8-Chicago.as6453.net [64.86.
124.22] ((My first major packet loss with TATA doesn't happen until we get to Chicago))
10 88 ms 96 ms 88 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
11 90 ms 90 ms 90 ms 66.198.96.58
12 89 ms 90 ms 89 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
13 88 ms 91 ms 97 ms 72.55.128.44
14 92 ms 92 ms 88 ms 184.107.107.176 ((Latency is still in hell on all the hops between Chicago and the datacenter, leading to the conclusion that there are still problems on SE's end))

Trace complete.