LAG issues starting at 1:30pm (hawaii) time everyday

[Strategy]

Hi,

Everyday for the past 2 weeks I have been having terrible lag starting at 1:30pm hawaii time. In the mornings or late evenings I have 0 problems, only from 1:30 to about 6pmish.
I can only assume this is because it is prime time server for mainland players and could be causing the issue? I have no lag on any other internet applications, this problem is stuck with FFXIV.
I have read some posts about TWC maybe having a problem and that is what I use (oceanic TWC).
Additionally, I have tried ping reducing things like pingzapper and others to no avail.

However, this is what I find when I do a ping test (I figured out how to do that on another post):

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=161ms TTL=47
Reply from 184.107.107.176: bytes=32 time=159ms TTL=47
Request timed out.
Reply from 184.107.107.176: bytes=32 time=171ms TTL=47

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 159ms, Maximum = 171ms, Average = 163ms

Pinging 184.107.107.176 with 32 bytes of data:
Request timed out.
Reply from 184.107.107.176: bytes=32 time=162ms TTL=47
Reply from 184.107.107.176: bytes=32 time=161ms TTL=47
Reply from 184.107.107.176: bytes=32 time=161ms TTL=47

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 161ms, Maximum = 162ms, Average = 161ms


Pinging 209.130.141.243 with 32 bytes of data:
Reply from 209.130.141.243: bytes=32 time=194ms TTL=52
Reply from 209.130.141.243: bytes=32 time=191ms TTL=52
Reply from 209.130.141.243: bytes=32 time=200ms TTL=52
Reply from 209.130.141.243: bytes=32 time=194ms TTL=52

Ping statistics for 209.130.141.243:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 191ms, Maximum = 200ms, Average = 194ms

Pinging 202.67.53.202 with 32 bytes of data:
Reply from 202.67.53.202: bytes=32 time=168ms TTL=45
Reply from 202.67.53.202: bytes=32 time=168ms TTL=45
Reply from 202.67.53.202: bytes=32 time=169ms TTL=45
Reply from 202.67.53.202: bytes=32 time=169ms TTL=45

Ping statistics for 202.67.53.202:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 169ms, Average = 168ms


So I think that (25%) packet loss thing is a problem? >.>

My lag consists of normal play, and then GIANT lag spikes. Sometimes it is just a second or two, sometimes its a good 10 seconds or more.
If I can't resolve this sometime soon, I will just have to stop playing. I like the game, but it is useless if I can't play during normal hours.

[Noahlimits]

Those aren't good logs since it only does it in bursts of four. Try putting a "-t" without the quotations. That will make the ping run until you stop it (with ctrl+c). That will give you a much better idea of how many packets you're losing.

[Raist]

Would also provide more useful data if you are pinging the IP's your game client is using (those IP's aren't the game servers--two of them are already known to be used for hosting web sites). They should start with either 199 or 124. The 199 IP's are the servers in Canada, while the 124 ones are servers in Japan. You can get the full IP addresses by running the netstat command in a cmd window (like where you run the ping command). If the results are a bit overwhelming, you can run resmon from your Run or Search box if on the newer versions of Windows--under the Network or TCP sections you will see the ffxiv executable listed with the IP's it is using.

As to the likely suspects, if you are coming across the US to get at the servers in Canada there is a big problem with congestion getting across California. While it has mostly been reported with TWC customers, it is not isolated to just TWC customers, as some of the routing partners in that area are also fighting this problem--and not only in California, so you may be getting hit with it multiple times in your route to the servers.

Since you seem to be doing well with running the ping command and copy/pasting results from that, you may want to give pathping a shot once you find the IP's your game is using. It can take a while to run (up to 10 minutes or so depending on your system and your route being tested), but it gives a lot of information that can be very useful to a technician if you were to open a support ticket with your ISP and/or SE.

[Compassion]

For me, it was about the same times but I live in Dallas, TX. The lag got so bad a couple weeks ago and so I started sending TWC my trace routes and it got escalated. Spoke with level 3 support where they ran a test on my line and results came back with a 9000ms latency and a 27% packet loss. A couple days later they called me back saying there were issues in the lines coming into my area and that they have resolved the issue. While it was improved, it was still laggy at about 3000ms.

I had enough of TWC and switched to Verizon FIOS. I've only had FIOS for a few days now but I can say this is the first time since playing FFXIV that I have had 0 lag moments. Honestly, it's a weird feeling to get no lag because I'm so used to it.

Anyway, initially I blamed SE and the route to the servers in Montreal but turns out after some investigation that TWC was the problem.

[Lukahn]

That's what time your neighbor gets home and starts leeching your internet.

[Demonchld]

same here TWC has been fucking up lately im waiting for them to come and fix my shit here too I live in Waikiki and I have the same damn problem.

Not only will FF crap out but my ping in vent will hit well over 20k

[Fadian]

I did a trace and I live in TN. I have comcast. I been cutting out just before I hit the Canada Data Center it seems. But I go through New York.


C:\Users\Nick>tracert 199.91.189.38

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 34 ms 36 ms 22 ms 69.254.103.1
3 10 ms 62 ms 10 ms xe-11-1-0-32767-sur02.ashgroverd.tn.nash.comcast
.net [68.85.135.253]
4 11 ms 11 ms 14 ms xe-5-0-9-0-ar01.goodslettvll.tn.nash.comcast.net
[68.86.176.61]
5 19 ms 24 ms 19 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net
[68.86.90.189]
6 34 ms 37 ms 36 ms 23.30.207.98
7 92 ms 64 ms 63 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]
8 60 ms 59 ms 59 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10
6]
9 62 ms 65 ms 61 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143.
214]
10 64 ms 72 ms 62 ms 4.69.201.69
11 61 ms 63 ms 64 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]

12 63 ms 64 ms 62 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]

13 106 ms 276 ms 230 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
14 50 ms * 118 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

15 98 ms 114 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
16 * * * Request timed out.
17 58 ms 43 ms 43 ms 192.34.76.2
18 43 ms 44 ms 43 ms 199.91.189.234
19 43 ms 43 ms 42 ms 199.91.189.38

Trace complete.

[Furlamseere]

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