no.. I read it, that's why I tried providing an analogy you might be able to grasp since you don't seem to be digesting how things work on the internet. I'm not just blowing smoke here. This information has been posted here time and time again...and people have posted back that they found issues and got it resolved. For whatever reason you are just not seeing the logic and insist on blaming SE for the problem without even considering any other possibility for what may be at fault here. Let's see if we can simplify it even further for you.
Ever been in an accident that rendered your car undrivable? Or maybe there was a mechanical failure, dead battery, or you got a flat tire? You had to first identify the problem, than go through the process necessary to get it fixed before you could drive it again.
Ever suffered a power outage because of a bad storm or maybe an accident took out a telephone pole or a transformer simply blew because it was old and worn out? You either had to contact the power company to report the outage, and/or had to wait for someone to inspect/repair the downed line/pole before your power was restored.
The same exact principles apply to the internet. When you have 17 potential points of failure on your path to the server, any one of those can go tits up at any given moment, for a host of sometimes bizarre reasons. When you have millions of people cramming themselves into narrow corridors on the internet, sh!t happens with absolutely no warning sometimes. Though, some of it is somewhat predictable... like when March Madness is in full effect, or the World Cup, or any other major entertainment event is pending you can expect all that extra streaming bandwidth to wreak havoc in specific corridors. Then there are these script jockies like Lizard Squad and Anonymous that like to launch attacks on servers to make statements, often announcing them publicly (they were monkeying with PSN last week, btw). You can also have a major storm system moving through an area so you might expect some communication disruptions throughout that region. Ever see the power companies bring in extra trucks and techs when hurricanes and tornadoes are in season?
It's kind of the same thing here--your ISP may simply need to get more proactive in detecting and managing the congestion. It is a fairly simple thing to check for...either you can do it yourself or your ISP should be willing to check it for you. All you need is a valid IP for the service you are having issues with, and run some traces and such to see if there's anything out of sorts along the route. They may even be able to simply monitor your router/modem to capture where you are connecting while playing and take things from there. They have tools to detect and repair these kinds of problems, but you need to bring in the right people (Tier3), and if you can provide decent information (like a trace report) it helps support your case and prods them in to action much faster. Here's an article from Blizzard about doing some of this basic testing for their games:
https://us.battle.net/support/en/art...g-a-traceroute
There are many more articles like this out there... because it is a known problem that is frequently checked when these issues come up. I just like to post that one because it also provides server addresses for their games that you can also run tests against for a comparison. You can get the IP of your world service by running netstat or resmon once you are logged fully into the game, or you can test against the lobby servers by their DNS names (note that some of the lobby servers may change once the EU servers go online):
Canada
neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com
Japan
neolobby01.ffxiv.com
neolobby03.ffxiv.com
neolobby05.ffxiv.com
Frontier server that the launcher connects to:
frontier.ffxiv.com
Patch/version manager:
patch-gamever.ffxiv.com
Secure login server:
secure.square-enix.com
All of those addresses are embedded in the executable files, and if your ISP monitors your connections throughout login and gameplay, they should see you hitting some of those. Or, you could just provide them the list up front to do testing against if you aren't willing to do any of the legwork to prod them along. Unfortunately, some of them have a very laissez-faire approach to their customer service and you need to push them to take action. Generating some of these reports and submitting them is often an effective way to push them into taking action--but you may need to demand to speak to a supervisor or to get transferred specifically to Tier3 support before you get someone actually willing to look at the data.
The points are, there are known issues with congestion across the internet that can just crop up seemingly out of nowhere at any given time. Sometimes, they just refuse to clear up on their own and you need to bring it to someone's attention to get it resolved in a more timely fashion. There are simple tests that can be run either by yourself or your ISP to confirm it. And yes... these things ARE the responsibility of your ISP to detect and correct for you--and not SE. In fact, in much of these cases, SE is virtually powerless to do anything about it. You are the the one with the binding agreement with your ISP, who in turn has the binding agreements with their routing partners. You need to hold the ISP accountable to test and maintain the stability of the service you are paying them to provide you, not SE.
Now, if you've gone through the motions and confirmed your route to the server is stable enough, then you can move on to the less common problems. Local security, changes in your system that may have injected a new problem (not uncommon for Windows or other software updates to cause problems...Microsoft, McAfee, Avast, AVG...many companies suffer this problem), a failing router that just can't effectively manage two other people streaming to a set-top box while you are playing, corrupted data because your game crashed unexpectedly (could apply server-side as well), and so and so and so forth. You may in fact find everything is fine leading up to the server, in which case you would need to open a formal ticket with SE at the support portal for a proper investigation. This is a user-to-user support forum, and not for requesting support directly from SE (read the sticky welcoming you to this forum for clarification on that point). We are simply players trying to help other players understand and rectify issues based on our past experiences.
But you are just digging in the heals and dumping everything on SE and not willing to entertain the possibility that it might be something else at fault. Things that are far more commonly found to be the sources of instability. If you aren't willing to take the time to try to flush out the more common problems, then you may simply be SOL until it magically resolves itself somewhere down the line because someone else eventually took their time to track down a potential source for the problem and got the proper people to look into things.
The choice is yours... try to do something about it yourself, or sit on your duff and wait it out.