Regarding high latency from Los Angeles/surrounding area

[Rapture]

A bit of an update. Maybe or maybe not it has something to do with the "Network Difficulties" and "Notice of Network Recovery" notices S-E posted, but as of today I'm now being routed through that alternative Level3->Cogent->S-E path I mentioned the other day rather than Telia->Tata->S-E.

<1 ms <1 ms <1 ms | 192.168.1.254
<1 ms <1 ms <1 ms | 001.131-78-65.ftth.swbr.surewest.net [65.78.131.1]
<1 ms <1 ms <1 ms | 172.22.4.13
<1 ms <1 ms <1 ms | 172.21.1.9
<1 ms <1 ms <1 ms | 172.21.0.254
1 ms 1 ms 1 ms | te-7-1.car1.Sacramento1.Level3.net [4.53.200.37] - Sacramento, CA
4 ms 4 ms 4 ms | ae-11-11.car2.Sacramento1.Level3.net [4.69.132.150] - Sacramento, CA
4 ms 4 ms 4 ms | ae-4-4.ebr2.SanJose1.Level3.net [4.69.132.158] - San Jose, CA
4 ms 4 ms 4 ms | ae-62-62.csw1.SanJose1.Level3.net [4.69.153.18] - San Jose, CA
4 ms 4 ms 4 ms | ae-1-60.edge1.SanJose3.Level3.net [4.69.152.16] - San Jose, CA
5 ms 5 ms 5 ms | te0-3-0-2.ccr21.sjc03.atlas.cogentco.com [154.54.13.49] - San Jose, CA
6 ms 6 ms 6 ms | be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.105] - San Jose, CA
7 ms 7 ms 7 ms | be2166.mpd21.sfo01.atlas.cogentco.com [154.54.28.69] - Los Angeles, CA
67 ms 67 ms 68 ms | be2134.mpd21.mci01.atlas.cogentco.com [154.54.6.38] - Kansas City, MO [Edit: Latancy for this hop was 51ms when tested @ 6:30AM PDT 9/23]
88 ms 91 ms 91 ms | be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.130] - Chicago, IL [Edit: Latancy for this hop was 57ms when tested @ 6:30AM PDT 9/23]
81 ms 81 ms 81 ms | be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42.6] - Toronto, Canada
83 ms 83 ms 83 ms | be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206] - Montreal, Canada
83 ms 82 ms 82 ms | 38.122.42.34 - Montreal, Canada (Ormuco Fiber bandwidth provisioning from Cogent)
* * * Request timed out. | (this hop is a private network Ormuco IP which blocks remote pings, non-issue)
82 ms 83 ms 84 ms | 192.34.76.2 - Montreal, Canada (Ormuco Fiber bandwidth provisioning to Square Enix NA Datacenter)
83 ms 90 ms 85 ms | 199.91.189.234 - Montreal, Canada (Square Enix NA Datacenter, bandwidth provisioning from Ormuco Fiber)
83 ms 83 ms 83 ms | 199.91.189.39 - Montreal, Canada (Square Enix NA Datacenter, FFXIV Behemoth Server)

The Cogent hops at Kansas City and Chicago seem a bit lagged at the moment, but nothing as extreme as the horrible Telia->Tata & Tata->SE hops which were +75ms above normal. Though a few hours before this post ~5-6PM PDT, I was still seeing intermittent spikes to 100-125ms on only the Orumco and S-E Datacenter IPs during peak time (unlike the above trace), while the Cogent & Level 3 IPs prior were completely stable (identical to above). These same spikes only on S-E's & Orumco's network were seen when doing traces from the Looking Glass services provided by Cogent & Level 3 which are literally run directly from the 10-40GbE core backbone routers. S-E may still have a bit of an issue with their bandwidth provider and local network handling peak loads. I guess I'll see this week if the Cogent route behaves any better or if the intermittent pause->fastforward R0 lags still persist.

Anyone else in California notice they are being routed differently as of today, or is it just me?

[Edit 2: Just noticed, but this routing change is because the Behemoth Server IP changed from 199.91.189.36 to 199.91.189.39. In this case, my ISP seems to route IP addresses in S-E's NA Datacenter range ending with an 'even' number through the Telia->Tata->SE route while IP ending with an 'odd' number get routed Level3->Cogent->SE.]

[Brannigan]

From the Palm Springs, CA area to Excalibur, just now. I get constant rubberbanding unless I'm using PingZapper. It started a couple of weeks ago.

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 14 ms 11 ms ge7-7.plspcajn01h.socal.rr.com [76.166.23.49]
4 15 ms 14 ms 11 ms tge0-8-0-11.pldscabx01r.socal.rr.com [72.129.37.134]
5 20 ms 26 ms 22 ms agg20.lsancarc01r.socal.rr.com [72.129.37.0]
6 22 ms 20 ms 27 ms 107.14.17.132
7 17 ms 23 ms 22 ms 107.14.19.86
8 36 ms 33 ms 35 ms ix-5-3-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.165]
9 145 ms 146 ms 145 ms if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.144.73]
10 136 ms 132 ms 137 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
11 166 ms 147 ms * if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
12 134 ms 133 ms 137 ms 66.198.96.50
13 139 ms 133 ms 133 ms 192.34.76.2
14 130 ms 136 ms 132 ms 199.91.189.234
15 131 ms 128 ms 130 ms 199.91.189.38

Trace complete.

[Rapture]

Logged on right after maint and entered a WP instance. Saw two split-second pause->fastforward lags over the course of a 30min DF run. Issue still exists even with the different routing.

[Raymeo]

Same issue here. Using Time Warner Cable in Thousand Oaks, CA -- about 40 miles north of Los Angeles.

I was stuck on a JP Legacy server when 2.0 launched. My game played beautifully then, though I didn't realize it at the time. I had some delay issues with AoE -- not consistently, but still noticeable from time to time -- so when transfers opened up I switched to an NA server hoping that my ping would improve. Have only had worse lag ever since. It's not even just AoE delay on the NA servers. I am experiencing terribly consistent lag spikes in which everything freezes for a few seconds and then lurches forward in time.

Update: Tonight I'm getting constant delays 7-20+ seconds between hearing my pickaxe strike rock and receiving an item so that I can click again. When I click on a fresh node to start mining, I'm freezing for about ten seconds before I can even begin. Everything is painfully slow, so I just did a tracert to Balmung. Hopefully the following helps somebody somehow.

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 63 ms 57 ms 21 ms cpe-76-89-160-1.socal.res.rr.com [76.89.160.1]
2 22 ms 11 ms 11 ms tge7-7.wlvgcabn02h.socal.rr.com [76.166.19.213]
3 17 ms 20 ms 14 ms tge0-8-0-10.vnnycajz02r.socal.rr.com [72.129.13.108]
4 18 ms 20 ms 19 ms agg29.tustcaft01r.socal.rr.com [72.129.13.2]
5 16 ms 14 ms 15 ms 107.14.19.30
6 14 ms 15 ms 16 ms 107.14.19.67
7 77 ms 31 ms 32 ms ix-5-2-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.157]
8 * 142 ms 118 ms if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.144.73]
9 115 ms 135 ms 113 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
10 161 ms 138 ms 129 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
11 113 ms 130 ms * 66.198.96.50
12 117 ms 115 ms 115 ms 192.34.76.2
13 115 ms 147 ms 114 ms 199.91.189.234
14 126 ms 128 ms 159 ms 199.91.189.30

Trace complete.

[Ulf]

I've been running Tracert everytime I have an issues with lag spikes. There are times where it will time out over and over then just give up.

This game is unplayable when this occurs, and it does so often. It is quite unfortunate, but I'm just not willing to pay for a VPN service so that this game will run as it should. Regardless of who is at fault, we are all getting shafted.

*I'm in Torrance, part of LA County.

[Yumiko]

Thanks for the tracert, im noticing pretty big jumps at some times which does render it pretty hard to play. Even if i go through playing anyway its still frustrating and not enjoyable to do everything delayed. ,_, was easier dealing with jp datacenters. XD

[Ryel]

Yeah I can definitely attest to having the same problems here, ran a tracert myself and got similar results to the OP.

Here's to hoping we get a bit of feedback on this would love to see if something can be done.

[Ulf]

I urge everyone to write a ticket to SE outlining the issue. We have to inundate them with as much information as we can, the more the better.

I've already cancelled my subscription renewal until I know that they are working on the issue. That may sound harsh, but I main a tank, and I cannot tank properly with these insane lag spikes. It makes the game suck for me and the other 3-7 people I'm playing with.

[Ewgraf]

The game is now unplayable for me after the 10/23 maintenance. It now regularly freezes up to tens of seconds before catching up.

[Azuki_Azusa]

Mine's usually bad on weekends, but recently, I've been getting lag no matter where I am in the game. It's getting to the point where my macros with delays are failing half the time. Characters zoom past me after freezing. Things I press aren't acted upon for 2-3 seconds more often than not.

In San Diego, using Time Warner, and the tracert shows similar to OP's. Pings to the server gets about 5-10% timeouts. Pinging anything else would get 0% timeouts.

Edit:

9 141 ms 136 ms 142 ms if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.144.73]