Square, your NA/EU data centre has serious issues...

[Appleh4x]

Really? When Odin is up looks like the whole playerbase crashes in the zone, doesn't it? Or do you know also how SE manages the connections?

Learn to read, man. This time I'll bold the part you missed: "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."

[Appleh4x]

Ignoring the fact you used a Wiki as a source because the definition is mostly correct (example it can affect existing connections, not just new connections), you're misunderstanding it:

1. Typical is not equal to Always
2. When you do a traceroute every line is a new node and any one of those can have a problem which affect your connection to the target machine. SE is only the last node one on that list so if node before them has a problem...

Except SE explicitly stated that the congestion was on their server. You all have very selective reading habits, don't you?

[ZohnoReecho]

Learn to read, man. This time I'll bold the part you missed: "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."

You try to understand what you read. Throughput doesn't mean the server and the last connection. If it lags it does for everyone.

[Appleh4x]

You try to understand what you read. Throughput doesn't mean the server and the last connection.

Throughput means all the data going through the node, you seem to be lost now.

[ZohnoReecho]

Throughput means all the data going through the node, you seem to be lost now.

Exactly, so it means everyone through that node. Why should you lag and someone else not? At school they never made the street example with the cars? Or what happens when you put too much liquid into a funnel? Do you know why it's called bottleneck when there aren't too many resources?

[Appleh4x]

Exactly, so it means everyone through that node. Why should you lag and someone else not? At school they never made the street road example? Or what happens when you put too much liquid into a funnel? Do you know why it's called bottleneck?

You aren't getting how this works, are you? The type of congestion control used by SE's server is limiting certain ranges of incoming transmissions in order to maintain a higher QOS for the other people connected. It's called congestion control. Do I know their algorithm? No, I didn't set up their server.

[worldofneil]

Except SE explicitly stated that the congestion was on their server. You all have very selective reading habits, don't you?

And other people have pointed out to you that 90k errors are not always server congestion, it's a generic connection issue error. I quite liked the example one guy gave you where his home WiFi disconnected and he got a 90k error.

Regarding the email, it's an automated email and they didn't even put your name on it, assuming your name isn't actually "Customer" of course. It's just a quick way for them to get rid of a lot of tickets by telling the people to do the iconic "Try turning it off and on again" in the hope that by the time you try again later, your ISP/route/whatever will be cleared up.

Perhaps they're smarter than me and they know that with some people there's nothing they can tell them that'll change their mind (that it's not their fault) so they're just not even going to bother trying. Must go now as I have made myself late, but if you reply to me specifically on anything I'll do my best to reply later.

[Ramsay_Trollton]

I unplugged my router and got a 90k error. SCREW YOU, SQUARE.

[Appleh4x]

And other people have pointed out to you that 90k errors are not always server congestion, it's a generic connection issue error. I quite liked the example one guy gave you where his home WiFi disconnected and he got a 90k error.

Regarding the email, it's an automated email and they didn't even put your name on it, assuming your name isn't actually "Customer" of course. It's just a quick way for them to get rid of a lot of tickets by telling the people to do the iconic "Try turning it off and on again" in the hope that by the time you try again later, your ISP/route/whatever will be cleared up.

Perhaps they're smarter than me and they know that with some people there's nothing they can tell them that'll change their mind (that it's not their fault) so they're just not even going to bother trying. Must go now as I have made myself late, but if you reply to me specifically on anything I'll do my best to reply later.

The people who have wifi issues aren't the people complaining here, to be more specific I'm addressing all the people confident in their home connections. Your arrogant dismissal of this problem is akin to someone complaining about a defective tv that doesn't turn on because of a faulty mainboard, and you saying that some people's don't turn on because they aren't plugged in so the problem must be with the consumer.

[ZohnoReecho]

You aren't getting how this works, are you? The type of congestion control used by SE's server is limiting certain ranges of incoming transmissions in order to maintain a higher QOS for the other people connected. It's called congestion control. Do I know their algorithm? No, I didn't set up their server.

Ya their congestion control is called 1017 with a manual control of character creation limit. Great QOS algorithm.