Problems with connection (R0) lag

[MimoIxel]

Rubber banding issue here as well. Makes it impossible to heal any boss fights in level 50 instances. Even walking around in the world people move for a few seconds, stop, and then jump forward. Didn't have this issue through all of phase 3 and 4 of beta and through release until this past week. Must be something that was done in the patch.

ISP- Cox Communications (Cable)
Location- Surprise(Phoenix, AZ)

[Kaaltet]

Same issue on Adamantoise. Cox 65d/19u ISP. Casa Grande, Arizona. Never had the problem before today.

Just did HM Ifrit and it was impossible. Same thing people are describing. My connection is perfect, I'm running around at 60 fps, but it's the rest of the world that just stops for several seconds, and then plays in fast-forward to catch back up. So I was missing interrupts and getting hit by plumes that exploded as fast as they appeared. During the transitions, Ifrit would jump up in the air, then nothing would happen for several seconds, then all three Ifrits would land and instantly charge.

There isn't a thing wrong on my end.


EDIT: Same issue just walking around Thanalan. Everyone else just stops for a few seconds, then fast-forwards.

EDIT 2: Even crafting is becoming unbearable from the lag spikes.

And now it's back again tonight. So no play tonight either. What's the story with this? SE aware of it? Fix? Anything?

[cenie]

I have been having the same issue. As far as I can recall it has only been happening since the latest maintenance. I've lowered my settings as low as it can go, I restarted my modem last night. People skip around town and primal fights are incredibly difficult.

I have Cox here in San Diego.

[LithiumFlower]

I've been having the same issue for the last couple of days. Tried all the usual stuff but nothing works.

ISP: Cox Communications (Cable)
Location: Temp, AZ

[Tyberius]

Exact same scenario here with Cox Communication in San Diego and it was perfectly fine since the last maintenance on Wednesday (Never Forget). The last time it was this bad was during Phase 4 beta weekend prior the Early Start period.

[JJbad]

Toss me on that list for having this problem.

Cox
Phx, AZ

[Avynia]

Consistent lag spikes here as well and worse in duty finders. It's nearly impossible to tank anything effectively or play the claim game for fates.

ISP: Cox Communcations
Las Vegas, NV.

Here are some trace routes;
http://pastebin.com/qk2WN4n3

[Kurlaran]

Is everyone in the last few days with this problem on Cox in the Southwest portion of the United States? Has anyone run a tracert on their connection to ffxiv? I am interested to see if anyone else times out at the same juncture I do when I run it. It may very well be a routing problem with cox. If someone would run: tracert neolobby02.ffxiv.com in cmd prompt and post the results it would be helpful. An asterix means it timed out. Mine seems to time out consistently it what seems to be an LA routing center from Cox

[Kurlaran]

Consistent lag spikes here as well and worse in duty finders. It's nearly impossible to tank anything effectively or play the claim game for fates.

ISP: Cox Communcations
Las Vegas, NV.

Here are some trace routes;
http://pastebin.com/qk2WN4n3

tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 21 ms 15 ms 21 ms 10.64.0.1
2 11 ms 50 ms 58 ms 24-234-16-229.ptp.lvcm.net [24.234.16.229]
3 59 ms 12 ms 32 ms 24-234-6-29.ptp.lvcm.net [24.234.6.29]
4 10 ms 8 ms 8 ms 24-234-6-218.ptp.lvcm.net [24.234.6.218]
5 * 72 ms 35 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14]
6 25 ms 21 ms 32 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
7 104 ms 107 ms 104 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
8 108 ms 93 ms 96 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
9 107 ms 107 ms 128 ms 192.34.76.2
10 128 ms 117 ms * 199.91.189.234
11 99 ms 97 ms 101 ms 199.91.189.74

Trace complete.

[cenie]

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 9 ms 7 ms 10.139.0.1
3 9 ms 7 ms 8 ms 68.6.11.52
4 * * * Request timed out.
5 9 ms 8 ms 8 ms fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 69 ms 28 ms 27 ms sanjbprj02-ae0.0.rd.sj.cox.net [68.1.5.186]
7 24 ms 20 ms 21 ms te0-7-0-30.ccr21.sjc03.atlas.cogentco.com [154.54.10.125]
8 21 ms 30 ms 36 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.113]
9 31 ms 28 ms 31 ms te0-0-0-4.ccr22.sfo01.atlas.cogentco.com [154.54.2.125]
10 68 ms 68 ms 69 ms be2133.ccr22.mci01.atlas.cogentco.com [154.54.30.66]
11 81 ms 81 ms 79 ms te0-7-0-4.mpd21.ord01.atlas.cogentco.com [154.54.2.234]
12 95 ms 94 ms 95 ms be2081.ccr21.yyz02.atlas.cogentco.com [154.54.42.10]
13 96 ms 102 ms 101 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25.26]
14 103 ms 100 ms 102 ms 38.122.42.34
15 * * * Request timed out.
16 98 ms 97 ms 140 ms 192.34.76.2
17 96 ms 95 ms 96 ms 199.91.189.234
18 98 ms 100 ms 96 ms 199.91.189.74

Trace complete.

There's mine.