Lag Spikes In Duties Since Patch

Hi,

I've been experiencing random lag spikes within duties since the patch on the 24th. Others I have spoken to have also been experiencing them. So far, oddities people have noticed:

- Getting constantly hit by Titan AoE while out of it - even other people can tell you dodged the AoE but got hit anyway.
- I once watched a healer stand in 3 stacked Titan plumes, die, then slide out of the plumes *after death*. The positional update delay was especially obvious with this one.
- Repel on Demon Wall proc'd 5-10 seconds after it finished casting. MNK had moved back into position by then and was shoved off.

Several people have complained about Titan lag spikes. Experienced groups are constantly wiping because of these. I'm in South America so I normally get 190-270ms ping, but I've heard complaints from people all over the world. A tracert shows the latency spike is somewhere near SE's servers for me:

tracert 199.91.189.23

Rastreando a rota para 199.91.189.23 com no máximo 30 saltos

1 8 ms 29 ms 10 ms bd215001.virtua.com.br [189.33.80.1]
2 11 ms 11 ms 7 ms spovsortd01.virtua.com.br [201.6.0.90]
3 9 ms 27 ms 25 ms c9062941.virtua.com.br [201.6.41.65]
4 21 ms 19 ms 20 ms embratel-T0-0-0-0-uacc01.ctamc.embratel.net.br [
201.56.239.17]
5 22 ms 23 ms 51 ms ebt-T0-15-0-12-tcore01.ctamc.embratel.net.br [20
0.244.140.218]
6 132 ms 136 ms 135 ms ebt-BP1451-intl01.nyk.embratel.net.br [200.230.2
20.110]
7 139 ms 140 ms 140 ms ae59.edge2.NewYork1.Level3.net [4.71.230.241]
8 150 ms 138 ms 141 ms vlan60.csw1.NewYork1.Level3.net [4.69.155.62]
9 137 ms 140 ms 141 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
10 277 ms 208 ms 151 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
11 136 ms 140 ms 139 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
12 141 ms 142 ms 152 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
13 162 ms 159 ms 159 ms 192.34.76.10
14 157 ms 155 ms 183 ms 199.91.189.242
15 156 ms 155 ms 158 ms 199.91.189.23

Having the exact same issue with that same node...

Trace route taken just now, 12/26/2013 @7:41pm EST:

Verizon FiOS / Maryland, USA

Code:

|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | Wireless_Broadband_Router.home - 0 | 302 | 302 | 0 | 0 | 3 | 0 | | L100.BLTMMD-VFTTP-52.verizon-gni.net - 0 | 302 | 302 | 5 | 7 | 16 | 7 | | G0-7-2-4.BLTMMD-LCR-21.verizon-gni.net - 0 | 302 | 302 | 5 | 9 | 27 | 10 | | so-1-1-0-0.RES-BB-RTR1.verizon-gni.net - 0 | 302 | 302 | 7 | 15 | 84 | 66 | | 0.xe-2-3-0.BR1.IAD8.ALTER.NET - 0 | 302 | 302 | 8 | 10 | 59 | 10 | | ae17.edge1.washingtondc12.level3.net - 2 | 290 | 287 | 30 | 36 | 85 | 36 | |vl-3602-ve-226.ebr2.Washington12.Level3.net - 0 | 302 | 302 | 35 | 40 | 51 | 40 | | 4.69.201.61 - 1 | 299 | 298 | 35 | 41 | 53 | 41 | | ae-81-81.csw3.NewYork1.Level3.net - 0 | 302 | 302 | 35 | 41 | 52 | 45 | | ae-82-82.ebr2.NewYork1.Level3.net - 0 | 302 | 302 | 35 | 42 | 52 | 40 | | ae-5-5.car1.Montreal2.Level3.net - 0 | 302 | 302 | 36 | 71 | 443 | 45 | | ae-11-11.car2.Montreal2.Level3.net - 22 | 163 | 128 | 0 | 30 | 199 | 36 | | ORMUCO-COMM.car2.Montreal2.Level3.net - 1 | 298 | 297 | 36 | 43 | 53 | 40 | | 192.34.76.10 - 1 | 294 | 292 | 32 | 37 | 90 | 34 | | 199.91.189.242 - 2 | 290 | 287 | 35 | 37 | 48 | 36 | | 199.91.189.25 - 2 | 290 | 287 | 32 | 36 | 44 | 38 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

I'm having the same exact issue here. Verizon FioS in Maryland, US.

Still having issues after network maintenance since 2.1, rubber banding, I phoned Verizon FIOS provider as well:

Code:

tracert 199.91.189.33 Tracing route to 199.91.189.33 over a maximum of 30 hops 1 6 ms 5 ms 6 ms Wireless_Broadband_Router.home [192.168.1.1] 2 12 ms 13 ms 13 ms L100.PHLAPA-VFTTP-53.verizon-gni.net [96.227.232.1] 3 18 ms 16 ms 14 ms G0-10-1-3.PHLAPA-LCR-22.verizon-gni.net [130.81.182.64] 4 16 ms 15 ms 12 ms ae6-0.PHIL-BB-RTR2.verizon-gni.net [130.81.199.210] 5 * * * Request timed out. 6 53 ms 54 ms 56 ms ae17.edge1.washingtondc12.level3.net [4.68.62.137] 7 50 ms 48 ms 46 ms vl-3603-ve-227.ebr2.Washington12.Level3.net [4.69.158.42] 8 73 ms 60 ms 48 ms 4.69.201.61 9 50 ms 44 ms 47 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78] 10 70 ms 58 ms 60 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45] 11 58 ms 53 ms 54 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 12 * 28 ms 29 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 13 51 ms 51 ms 50 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74] 14 47 ms 49 ms 49 ms 192.34.76.10 15 44 ms 42 ms 44 ms 199.91.189.242 16 41 ms 42 ms 41 ms 199.91.189.33 Trace complete.

Code:

tracert 199.91.189.33 Tracing route to 199.91.189.33 over a maximum of 30 hops 1 6 ms 7 ms 6 ms Wireless_Broadband_Router.home [192.168.1.1] 2 19 ms 13 ms 13 ms L100.PHLAPA-VFTTP-53.verizon-gni.net [96.227.232.1] 3 17 ms 15 ms 15 ms G0-10-1-3.PHLAPA-LCR-22.verizon-gni.net [130.81.182.64] 4 15 ms 13 ms 17 ms ae6-0.PHIL-BB-RTR2.verizon-gni.net [130.81.199.210] 5 * * * Request timed out. 6 73 ms 70 ms * ae17.edge1.washingtondc12.level3.net [4.68.62.137] 7 * 48 ms 49 ms vl-3603-ve-227.ebr2.Washington12.Level3.net [4.69.158.42] 8 50 ms 49 ms 48 ms 4.69.201.61 9 48 ms 48 ms 52 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78] 10 50 ms 50 ms 50 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45] 11 61 ms 69 ms 61 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 12 31 ms 28 ms 29 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 13 51 ms 48 ms 45 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74] 14 48 ms 46 ms * 192.34.76.10 15 43 ms 43 ms 43 ms 199.91.189.242 16 46 ms 40 ms 43 ms 199.91.189.33 Trace complete.

http://na.finalfantasyxiv.com/lodest...17f68d323f7112

Hoping w/e happening tonight fix the lag issue.

Bump, it's still happening (in fact, it seems to have gotten worse).

I am experiencing this also. Sending is 23 and receiving is 3k+. I have spoken to Time Warner and they have verified it seems to be an issue on SE end, a backbone in Canada (which TWC stated SE would need to push for repair) or their Data Center. I, for one, am about done with dealing with this. I have paid for 180 days, but at this point, I am about to start demanding a refund for a product that does not work. Maybe everyone should and when the game goes under again like before, they might rethink taking these latency issues a bit more seriously.

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.

- Furlamseere