Constant Lag Spikes

[Autarkis]

ISP's throttle P2P traffic. FFXIV's data gets classed as P2P traffic and gets throttled.

Square Enix needs to ensure their traffic is not throttled.

There is nothing a user can do, nothing at all. It's all Square Enix, and frankly appears they do not care.

I'm not subbing to this game unless its fixed before my free time runs out.

[Marishi-Ten]

ISP's throttle P2P traffic. FFXIV's data gets classed as P2P traffic and gets throttled.

Square Enix needs to ensure their traffic is not throttled.

There is nothing a user can do, nothing at all. It's all Square Enix, and frankly appears they do not care.

I'm not subbing to this game unless its fixed before my free time runs out.

This isn't entirely accurate.

First, not all ISP's throttle P2P clients. This depends on the ISP and their own internal policies and firewalls. Contacting the ISP and requesting they whitelist the remote host ports and/or IP's will stop the throttling. ISP's can perform this function. Getting them to do it may be another matter entirely.

Second, This is not a client ISP issue. This is a remote node/port overload issue (numerous trace routes from this thread alone confirm the bottle neck occurs on a remote host hop).

Third, there are multiple avenues that users can take. Contact the rack/fiber provider that Square rents from and log tickets. Contact your ISP and request that you be rerouted around the hops having issues. Be vocal about the issue. These backbones rely on traffic being routed though them. If traffic slows, they lose money. If they lose money, they will address the issue.

[Berani]

ISP's throttle P2P traffic. FFXIV's data gets classed as P2P traffic and gets throttled.

Square Enix needs to ensure their traffic is not throttled.

There is nothing a user can do, nothing at all. It's all Square Enix, and frankly appears they do not care.

I'm not subbing to this game unless its fixed before my free time runs out.

Well, no.

Because once I started having this issue just this week, I called my cable company (Cox) and specifically asked if Final Fantasy XIV or any other MMO using a P2P style patcher is throttled.

The tech support team put me through to a supervisor, who checked the full list of all throttled services: Final Fantasy XIV is not on it.

So your theory just got thrown out the window.

As a service, they also reset my modem and sent a tech out to check the wiring. Nothing wrong. And the ONLY program on my computer that suffers this issue is FF: ARR.

So yes, the problem is indeed on Squeenix's end and not the client's in most cases. It's absolutely ABSURD to state that every ISP worldwide suddenly classed it P2P at the same time.

[Max_Ohm]

This may be an issue with SE, but it may also not be. I have a very strong feeling that it's a combination of a few factors.

The game has hit a pretty huge amount of subscribers and simultaneous connections to their servers which must be routed through internet backbone servers in and around the NA datacenter area. Many of us have been researching this, and have found that the lag is caused due to high ping, packet loss, and/or timeouts while routing data through these servers (not ffxiv servers btw - Cogent, TATA etc.. are known offenders).

A couple things happened to start off this lag with me, namely the first big maintenance that opened up the servers to more players, and the subsequent massive increase of players using each ffxiv server simultaneously. From what I've been able to gather, it seems like SE changed the shaping of either the type of data they send, or amount, and it's simply overloading the backbone servers used to connect us to SE's servers.

Naturally they will not be saying much or anything about the problem to us as:
A: It's only affecting a non majority portion of players
B: They likely don't have a solution yet

I've come to the conclusion that we will simply have to wait this out, and hope that SE manages to get the issues figured out in a reasonable time frame. Which sucks, because if it's not fixed by the time my free time is over, I'll likely not continue to play until it is fixed. And that is unfortunate, because I love playing this game when it works.

[whycantiusebetaforumname]

I have been having issues lately im on ps3 and I get unusual errors like not having my game registered launching errors huge lag spikes in game during peak hrs but when the launcher has an error like the latest one I got was 303 unable to verify update it kills my ps3 internet connection for 10 minutes to an hour its really sporadic but aalso frequent

[ntall1]

It would be nice if SE would stop the speculation by the players by acknowledging that this is even an issue. What I find more shocking than the issue itself is the fact that its gone on so long without even so much as a mention.

[Eleeciam]

still happening

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.



Tracing route to 199.91.189.30 over a maximum of 30 hops


3 38 ms 39 ms 30 ms 76.126.40.1
4 27 ms 34 ms 34 ms ge-1-46-ur01.fairfield.ca.sfba.comcast.net [68.8
5.190.5]
5 17 ms 14 ms 26 ms te-1-6-0-10-ar01.sfsutro.ca.sfba.comcast.net [68
.85.154.186]
6 16 ms 22 ms 15 ms he-1-5-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.90.93]
7 15 ms 19 ms 15 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.86.122]
8 17 ms 16 ms 27 ms ix-2-3-0-0.tcore1.PDI-PaloAlto.as6453.net [66.19
8.127.17]
9 92 ms * 90 ms if-2-2.tcore2.PDI-PaloAlto.as6453.net [66.198.12
7.2]
10 90 ms 89 ms 91 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
11 96 ms 90 ms 92 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
12 98 ms 6 ms 91 ms 66.198.96.50
13 91 ms 91 ms 90 ms 192.34.76.2
14 89 ms 89 ms 98 ms 199.91.189.234
15 90 ms 90 ms 98 ms 199.91.189.30

Trace complete.



Tracing route to 199.91.189.30 over a maximum of 30 hops

3 32 ms 34 ms 22 ms 76.126.40.1
4 12 ms 27 ms 19 ms ge-1-46-ur01.fairfield.ca.sfba.comcast.net [68.8
5.190.5]
5 41 ms 16 ms 15 ms te-1-6-0-10-ar01.sfsutro.ca.sfba.comcast.net [68
.85.154.186]
6 34 ms 28 ms 18 ms he-1-5-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.90.93]
7 34 ms 17 ms 51 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.86.122]
8 30 ms 18 ms 27 ms ix-2-3-0-0.tcore1.PDI-PaloAlto.as6453.net [66.19
8.127.17]
9 91 ms 92 ms * if-2-2.tcore2.PDI-PaloAlto.as6453.net [66.198.12
7.2]
10 90 ms 98 ms 100 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
11 97 ms 115 ms 225 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
12 95 ms 89 ms 88 ms 66.198.96.50
13 90 ms 91 ms 96 ms 192.34.76.2
14 90 ms 95 ms 100 ms 199.91.189.234
15 101 ms 111 ms 87 ms 199.91.189.30

Trace complete.



Tracing route to 199.91.189.30 over a maximum of 30 hops


3 41 ms 28 ms 20 ms 76.126.40.1
4 11 ms 35 ms 10 ms ge-1-46-ur01.fairfield.ca.sfba.comcast.net [68.8
5.190.5]
5 11 ms 15 ms 16 ms te-1-6-0-10-ar01.sfsutro.ca.sfba.comcast.net [68
.85.154.186]
6 14 ms 19 ms 15 ms he-1-5-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.90.93]
7 16 ms 17 ms 27 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.86.122]
8 27 ms 20 ms 18 ms ix-2-3-0-0.tcore1.PDI-PaloAlto.as6453.net [66.19
8.127.17]
9 * * * Request timed out.
10 95 ms 91 ms 97 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
11 94 ms 87 ms 98 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
12 102 ms 96 ms 89 ms 66.198.96.50
13 102 ms 96 ms 90 ms 192.34.76.2
14 90 ms 99 ms 95 ms 199.91.189.234
15 97 ms 88 ms 94 ms 199.91.189.30

Trace complete.