Regarding high latency from Los Angeles/surrounding area

[Graypoupon]

Cox Phoenix first time ever having problems, and it is completely unplayable. Bummer if Cox decided to start throttling.

It has nothing to do with cox. run a tracert to your server. if your not sure of your server's IP

Command Prompt: type netstat
your FFXIV server should be something like 199.91.xx.xx
Next type: tracert 199.91.189.18 (gilgamesh as an example)

You will likely see 3hops if you live in PHX.
ae2-223.1lax20.ip4.tinet.net 173.241.128.81
xe-1-3-0.mt110.ip4.tinet.net 89.149.184.74
ormuco-gw.ip4.tinet.net 216-221-156-110

These servers are the issue causing issues for Cox subscribers in PHX area.

The internet backbone in the United States is a complete and total piece of shit... It's an embarrassment... it really is. tata, tinet, cogentco... are all complete shit...

The issues with the above mentioned ISP's (if you can call them that) have been going on for well over a year. I've seen reports consistently for ip's owned by tata, tinet, and cogentco causing unplayable lag for WoW, LoL, FF14, SWtoR, and just about ever other online game.

The issue is your ISP, and SE's ISP will both work to bypass the currently effected servers, however as soon as they do, it overloads another piece of shit server-cluster owned by the same piece of shit companies.

1day America won't have 3rd world internet.... 1day.

[Ademre]

C:\Users\ender>tracert 199.91.189.32

Tracing route to 199.91.189.32 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 12 ms 9 ms 10.108.0.1
3 11 ms 11 ms 10 ms 68.6.13.4
4 11 ms * * ip68-4-11-229.oc.oc.cox.net [68.4.11.229]
5 12 ms 11 ms 11 ms ip68-4-11-228.oc.oc.cox.net [68.4.11.228]
6 12 ms 13 ms 13 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 15 ms 13 ms 13 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
8 91 ms 92 ms 92 ms xe-1-3-0.mtl10.ip4.tinet.net [89.149.184.74]
9 96 ms 97 ms 97 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 101 ms 98 ms 101 ms 192.34.76.2
11 94 ms 98 ms 92 ms 199.91.189.234
12 96 ms 97 ms 95 ms 199.91.189.32

Trace complete.