To be fair to SquareEnix, Comcast is demonstrably having an absurd amount of weird problems at the boundary with NTT (on which FFXIV is hosted) right now and has been since about February 20th; the fact that the equipment there apparently had the networking equivalent of a stroke two days after the 5.2 patch is really unfortunate timing, but not necessarily connected to the patch itself. And if you're on Comcast—or a smaller provider that uses Comcast as their backbone connection—I would honestly say the chances that any sort of connectivity weirdness are related to that whole situation are a non-zero quantity.
I mean, my FC-mates who are on Comcast have had a litany of different connectivity issues to FFXIV since 5.2, and what they are seems to vary; the only consistency is that all of the affected on any given night are on Comcast, and literally everyone else in the FC is fine. I don't know whether it's on Comcast's side or NTT's side, but they've had lag/latency, dropped packets and disconnections, streams that just get arbitrarily closed after a certain time because the boundary router seems to think they're no longer needed, etc...
That said, regardless of whether it's the Comcast/NTT boundary weirdness that's affecting you or not, I can totally get that them using the same set of questions to try to get folks back online feels frustrating. But I doubt the tech support folks are finding it any more fun to be able to not provide an answer; based on watching friends who've worked tech support jobs, I would put decent odds on the guess that they don't even have the authority to try to escalate a problem to a dev to look at unless they can tick off a box somewhere that says they've offered all the stock solutions, and that the customer confirmed trying them with no success.
Edit to add: FWIW, if this is the case for you, using a gaming-focused performance VPN—which will route your traffic around the affected boundary—should actually clear the issue up. That's what several friends have done to get around the situation. If it does fix things, the issue is with your ISP (or rather, the route between your ISP and FFXIV's servers); if it does not, then the issue is on the local network (or in FFXIV's network code).



Reply With Quote

