![final fantasy xiv lodestone maddi kitten final fantasy xiv lodestone maddi kitten](https://img2.finalfantasyxiv.com/f/8924ac7800cec03b5843d9453ca2bb56_e2bb3f9679fec6d4836fcf8abcc3eeacfl0_640x873.jpg)
The load balancers for ffxiv are located at the same data center as the servera that they serve. To your point about load balancers, that doesn't particularly matter to the end user. Just based on that, I don't think SE polices icmp aggressively. I get no loss when pinging Primal on VPN at 1400 bytes, but almost 10 percent while pinging without a VPN, even during peak hours. Frontier is experiencing a bad hop in the path to the servers since Wednesday, which VPNs allow me to avoid. Ping to Primal has been an extremely reliable indicator for me of when I need to leverage my VPN before and during early access. While your points are correct in general, neither of them really apply to FFXIV per the below. I will address these two points as a networking expert who has been having ISP issues since Wednesday (far before peak times started). It sucks to be on the receiving end of the results, but I think knowing how it works at least lets people have a better understanding on why it is not fixed quickly. For people more intrested in this sort of things, you can look up linear and circular economics as well as project management. Obviously this can be way more complicated if we were to map out all the ingrediants that go into each thing and how they get to their points. all the way down to the obtaining of the ingrediants Each time something is shipped, each time something is assembled in manufactured. You can then work better to say how does that get to ignoring a few steps, but there are a lot of places along the way there this could be delayed. Let's say a company were to place an order for 10 sandwiches. Take a peanut butter and jelly sandwitch. I think the easiest way to make it understandable for people is to use a sandwich analogy. Many large companies are on the other side of it and have cleared out excessive inventory and are only making parts to order, because of decrease in demand and they must continue meeting the needs of their stockholders or venture captal supplies who restrict excessive spending to cut overall losses. To make make matters worse, many companies no longer have stock on shelves because there was a hugh production lull in 2020 that is still rippling through. So in order to get all the parts for a system, it requires a lot of work involving multiple vendors to all go through. Hugh Tariffs on certain technology has been increasing the back and forth. This is not directed at anyone in particular, but more commentary on why SE cannot just throw more servers at the problem, and it is not isolated to SE.Īcross the world due to changes in logistics and employees working, logistics and manufacturing and refine has been greatly affected. The other 50% seems to just be SE's queue hiccuping and booting for no rhyme or reason, and then the horrific programming choice to close the whole damn application when it can't connect to a server lol.Įither way, this is because of SE's lack of infrastructure upgrades over the past few years, even before the pandemic.Īlso, servers are indeed available just more expensive, if SE truly wanted they could have gotten some in time or a bit after release, but the price was higher than they estimate the cost of disgruntled players having login issues, and comped game time.
![final fantasy xiv lodestone maddi kitten final fantasy xiv lodestone maddi kitten](https://img2.finalfantasyxiv.com/f/5fcd678a086b579104ad6421d69226f7_c76848359d0b4d2f37aefbb9903ed97bfl0_640x873.jpg)
Not 100% certain, but it seems to be in the likely ballpark given my networking experience.
![final fantasy xiv lodestone maddi kitten final fantasy xiv lodestone maddi kitten](https://img2.finalfantasyxiv.com/f/a1859c0fff2caef14f40e37711049f6e_8e81e2940511f7152ba4462fe53e35b8fl0_640x873.jpg)
I believe these small latency spikes, combined with ff14's capped login queues then makes the servers respond to your delayed packet at the speed of molasses, means that it delays the packet out too long and then drops you with an error 2002. I noticed that about 50% of the time, the error 2002 was synced up to a small and what would otherwise normally be negligible latency spike. I saw someone else post about monitoring their network traffic during the queue and the errors and I decided to try it myself: