Bad rubberbanding since early Nov 26

[Janyd]

So, in what I hope is a separate issue altogether from the last time I experienced rubberbanding/packet loss in FFXIV in October, I had a nasty case of rubberbanding in The Copied Factory around 12AM Central on November 26 (today).

It has persisted throughout the day, even during Beast Tribe daily quests and during Guildhests and Trust Dungeons.

All of that is on Sargatanas/Aether, for what it's worth.

I've tried power cycling all devices and the gateway, and flushed the DNS cache. No changes. This is on a Wi-Fi connection, since hard-wiring via Ethernet is not feasible in my current living space. A hotspot saw no change in the problem, either.

I'm at my wit's end as to what I can do next. Enclosed is the traceroute I ran a short time ago.


Tracing route to 204.2.229.9 over a maximum of 30 hops

1 27 ms 1 ms 2 ms dsldevice.attlocal.net [192.168.1.254]
2 33 ms 33 ms 17 ms 76-250-208-1.lightspeed.livnmi.sbcglobal.net [76.250.152.1]
3 39 ms 32 ms 51 ms 64.148.112.49
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 46 ms 55 ms 46 ms 32.130.16.15
8 70 ms 42 ms 57 ms dlstx401igs.ip.att.net [12.123.16.77]
9 80 ms 43 ms 51 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
10 73 ms 51 ms 50 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
11 91 ms 83 ms 71 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 85 ms 88 ms 69 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 90 ms 87 ms 69 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 71 ms 70 ms 81 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * * 68 ms 204.2.229.230
16 * 80 ms 68 ms 204.2.229.9

Trace complete.


EDIT 6:25 PM CST:
After flushing the DNS cache and power cycling again, I decided to run another traceroute.
Unfortunately, I cannot check in-game at the moment due to other things needing my attention, but here it is:

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 2 ms 5 ms dsldevice.attlocal.net [192.168.1.254]
2 19 ms 20 ms 17 ms 76-250-208-1.lightspeed.livnmi.sbcglobal.net [76.250.152.1]
3 21 ms 19 ms 51 ms 64.148.112.49
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 34 ms 27 ms 32 ms 32.130.16.15
8 32 ms 31 ms 29 ms dlstx401igs.ip.att.net [12.123.16.77]
9 38 ms 41 ms 41 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
10 40 ms 39 ms 43 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
11 76 ms 67 ms 71 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 75 ms 66 ms 72 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 70 ms 80 ms 81 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 71 ms 72 ms 77 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 87 ms * 70 ms 204.2.229.230
16 94 ms 72 ms 69 ms 204.2.229.9

Trace complete.

Seems the 15th hop (the Lobby server, I believe) has improved a bit since then, as have hops 2 and 3. Strange.