All the lag, network issues are server side [CONFIRMED]

[Medura]

90k is a whole other issue, it has little to do with the lag most people experience.

[Brises]

They admitted to the game being more popular than expected, but not actually congestion. Server congestion directly causes packet loss, timeouts, refused connections... basically all the issues described. The 90k error once logged in is a timeout, and 90k before logging in is a refused connection, and the lag is the mass packet loss.

I believe when they say servers are running at max capacity, character creation has been blocked, the lobby server has been closed at times due to too many concurrent connections, and have now had two phases of adding more servers. And Yoshi P constantly apologizing for server problems. I think that means they are saying server congestion.

[Raist]

They admitted to the game being more popular than expected, but not actually congestion. Server congestion directly causes packet loss, timeouts, refused connections... basically all the issues described. The 90k error once logged in is a timeout, and 90k before logging in is a refused connection, and the lag is the mass packet loss.

What the...???!!! What rock have you been living under? Haven't admitted to Congestion problems? The Notice section on the Lodestone has posts specifically addressing it.
http://na.finalfantasyxiv.com/lodest...ac432b3e55a9ba
http://na.finalfantasyxiv.com/lodest...77fc01eaf49bf5
http://na.finalfantasyxiv.com/lodest...bf87957cdd329f
http://na.finalfantasyxiv.com/lodest...1e2dffa67cccc8

All for of them are from 9/12, and even state Congestion in the title of the post.

There's another on 8/30, again... it's in the title of the post:
http://na.finalfantasyxiv.com/lodest...7ef1e00d43f6a7

08/30/2013 11:32 AM
FINAL FANTASY XIV Congestion (Aug. 30)
Currently, due to the heavy traffic, players may experience the following issues.

- An issue wherein the game launcher screen may take some time to display.
- An issue wherein a lobby error may appear at the start screen.
- An issue wherein the World name may not appear correctly on the World selection screen.

If you encounter any of these issues, please wait and try again at a later time.

We apologize for any inconvenience this may cause and thank you for your cooperation.

And that's just what I found with a couple mouse clicks... good grief.

[Appleh4x]

ITT no one who understands the consequences of an overloaded server. http://www.linfo.org/congestion.html When you limit the bandwidth coming in it gives you the 90ks and lag, they are definitely related and if you can't see that you shouldn't be posting in a tech support forum acting like you know how anything on how a network functions.

[Raist]

ITT no one who understands the consequences of an overloaded server. http://www.linfo.org/congestion.html When you limit the bandwidth coming in it gives you the 90ks and lag, they are definitely related and if you can't see that you shouldn't be posting in a tech support forum acting like you know how anything on how a network functions.

Did you even read the document you linked to?

Network Congestion Definition



Network congestion is the situation in which an increase in data transmissions results in a proportionately smaller increase, or even a reduction, in throughput.

Throughput is the amount of data that passes through the network per unit of time, such as the number of packets per second. Packets are the fundamental unit of data transmission on the Internet and all other TCP/IP (transmission control protocol/Internet protocol) networks, including most LANs (local area networks).

Congestion results from applications sending more data than the network devices (e.g., routers and switches) can accommodate, thus causing the buffers on such devices to fill up and possibly overflow. A buffer is a portion of a device's memory that is set aside as a temporary holding place for data that is being sent to or received from another device. This can result in delayed or lost packets, thus causing applications to retransmit the data, thereby adding more traffic and further increasing the congestion.

Congestive collapse is the situation in which the congestion becomes so great that throughput drops to a low level and thus little useful communication occurs. It can be a stable state with the same intrinsic load level that would by itself not produce congestion. This is because it is caused by the aggressive retransmission used by various network protocols to compensate for the the packet loss that occurs as a result of congestion, a retransmission that continues even after the load is reduced to a level that would not have induced congestion by itself.

Network congestion is somewhat analogous to road congestion. One technique that has been used with some success to deal with road congestion is metering, in which the rate of vehicles entering a road or area is restricted by signals. Many economists advocate pricing (i.e., charging to use the roads, with higher prices when congested) as a more efficient congestion reduction technique. Such congestion pricing has become much easier to put into practice in recent years as a result of advances in electronics technology.

However, there are also some important differences. For example, it can be much easier and less costly to increase capacity in communications networks than in road networks. Also, communications network traffic can be compressed in many cases, whereas road traffic cannot. In addition, communications network traffic can often be rerouted at essentially zero cost (when alternative routes exist), whereas large costs (particularly in terms of lost time) can be incurred from rerouting road traffic.

Various techniques have likewise been developed in attempt to minimize congestion collapse in communications networks. In addition to increasing capacity and data compression, they include protocols for informing transmitting devices about the current levels of network congestion and having them reroute or delay their transmissions according to congestion levels.

Notice that congestion can happen at any given point in the route---this document clearly points that out. This is what we have been getting at in all these other threads you keep "poo-pooing" in. We are seeing signs that there is ALSO periodic congestion in the routing. Fixing things at the endpoint does NOTHING.... N O T H I N G to alleviate congestion at a router that is not connecting to that endpoint, but somewhere in between.

The very document you just linked to even talks about mitigating congestion in routing---the very thing we've been trying to investigate. It even goes so far as to talk about the practice of rerouting to mitigate congestion.

[Gonzothegreat198]

ITT no one who understands the consequences of an overloaded server. http://www.linfo.org/congestion.html When you limit the bandwidth coming in it gives you the 90ks and lag, they are definitely related and if you can't see that you shouldn't be posting in a tech support forum acting like you know how anything on how a network functions.

Here's another point you are getting confused over. You seem to think that just because an overloaded server can cause a 90k error and lag, that means all 90k errors and lag are being produced because of an overloaded server. This is wrong. An overloaded server (the illness) can produce 90k errors and lag (symptoms), but sometimes the symptoms you are seeing, in this 90k and lag, don't always indicate the same illness.

One symptom of Asthma is shortness of breath, however just because you have the symptom shortness of breath, does not mean you have asthma.

[Appleh4x]

Did you even read the document you linked to?



Notice that congestion can happen at any given point in the route---this document clearly points that out. This is what we have been getting at in all these other threads you keep "poo-pooing" in. We are seeing signs that there is ALSO periodic congestion in the routing. Fixing things at the endpoint does NOTHING.... N O T H I N G to alleviate congestion at a router that is not connecting to that endpoint, but somewhere in between.

The very document you just linked to even talks about mitigating congestion in routing---the very thing we've been trying to investigate. It even goes so far as to talk about the practice of rerouting to mitigate congestion.

Except for the FACT that Se said it was congestion on their own server causing issues.

[Raist]

Except for the FACT that Se said it was congestion on their own server causing issues.

That copy/paste email you got was pertaining to the hard 90000 error disconnects. How many times does that distinction have to be made?

If you are receiving an Error 90000 when attempting to access FINAL FANTASY XIV: A Realm Reborn, please try again later. This error simply means that the server is congested and you will need to keep trying until you are able to login. We apologize for any inconvenience this may cause you.

In order to experience the latency/lag, you have to first connect and get in the game.

[djrdo]

So after requesting a refund for the subscription I paid for this month because I haven't been able to play this is the message I received from SE support:

"Dear Customer,

Regarding your request for account support. Please find your answer below.

If you are receiving an Error 90000 when attempting to access FINAL FANTASY XIV: A Realm Reborn, please try again later. This error simply means that the server is congested and you will need to keep trying until you are able to login. We apologize for any inconvenience this may cause you.

Thank you for contacting the SQUARE ENIX Support Center."

Take that you white knight "gurus" of supposed throttling knowledge.

Oh and here is a wikipedia quote from their Network Congestion article: "In data networking and queueing theory, network congestion occurs when a link or node is carrying so much data that its quality of service deteriorates. Typical effects include queueing delay, packet loss or the blocking of new connections. A consequence of these latter two is that incremental increases in offered load lead either only to small increases in network throughput, or to an actual reduction in network throughput."

So that is ALL OF THE ISSUES DESCRIBED.

have u tryed forwarding your ports... some gateways pick this game up as a p2p when its not... or do u just whine about ur issues and not try and fix them

[Gonzothegreat198]

That copy/paste email you got was pertaining to the hard 90000 error disconnects. How many times does that distinction have to be made?



In order to experience the latency/lag, you have to first connect and get in the game.

Nice point I missed that. Yah if you're getting 90k'd before you even get into the game that is not even close to what everyone else is talking about. Hell even my 90k's don't fall under that heading.

Oh btw, you do understand the fact that Server Congestion =/= Network Congestion 100% of the time.

Point in case, during open beta, early access and launch the reason the servers were congestion was due to server capacity, ie the servers themselve were not physically and/or logically large enough to handle the population. Server capacity is a hardware issue, hell they are still having capacity issues in regards to the server because they neglected to separate the NA and EU datacenters. Personally, what I think they should do is get on the Red Phone and call Blizzard to get an emergency consult on how to properly setup and maintain datacenters. Now I'm not saying that Blizzard is perfect, but come on, not splitting NA and EU to their own datacenters? Really?