Square quit blaming 2002 on the user's internet connection and take responsibilty

[DarkDepravity]

I am genuinely not trolling. I am sorry that my post made you think so. I actually tried to formulate my sentences in a way that will not provoke emotional response and reach the rational mind, but I failed.

I used to have 2002 error every half an hour or so, and had to restart the client. But they seem to either fix the problem or significantly reduce the probability of it happening: for several days now I was able to join 2000-5000 person queue and start playing without single 2002 error.

Please at least try to diagnose problem on your end:
1. Reboot all network equipment
2. Try wired connection instead of Wi-Fi. If switching to wired connection will not cause 2002 errors, then at least you will know where the issue is and will be able to search for ways to fix it.
3. Try using different Internet provider. I would try tethered Internet connection through a phone. The 2002 experience may be actually worse though, since wireless network protocols are inherently less stable.

The aggregated data thus far suggests an issue on the NTT backbone between several of their nodes in the US, one candidate being TX - CA (sacramento), so a different internet provider might indeed remedy the issue, just not for the reasons you assume. The traffic could potentially take a different route and thus not hit all the problematic NTT nodes. But it might also result in the precisely same thing depending on what routing agreements the ISPs have. Those who have VPN providers could try to find a different egress point. Personally I have been using PIAs California node today, and while the last stretch is NTT, I have about halved the # of NTT nodes I go via, and it has been rock stable, so it supports the general data available.



You can argue back and forth at what point it is no longer SEs responsibility, but considering the data thus far suggests the culprit being NTT and SE seeming to have an agreement with NTT. This is definitively in SEs court.


Edit: the downside for SE of having a 30+ years old franchise, literally generations of people with an interest in the franchise have had more than enough time to build up a lot of tech knowledge, also relating to issues such as these.



You are listing the (very good) 1st line suggestions for improving,but this is highly likely to be a 3rd line issue on the infrastructure end. The reason it works for a lot of people without a hitch is most likely because their ISPs routing agreements take different routes.