90ks, 10105, 2002, and lag...

[Raist]

I don't intend on fixing what is not my fault though. SE should be doing something about all this. Yes, we can try everything in our power to help fix it. But, it is ultimately SE's side.

How is it SE's responsibility to fix issues that are falling within the scope of our ISP's or even our own local networks? Vanicent's issue apparently involved local hardware....clearly not SE's responsibility to address.

Again... need to actually investigate what is going on with the specific sessions you are using to connect to the FFXIV services. We have repeatedly been able to identify known issues along the route that can and should be addressed by either the ISP managing the hardware involved, or by our ISP's arranging an alternate path (or in many cases as a quick fix when they don't cooperate, a VPN may skirt around some if not all of the bad segments).

It can, does , and HAS been proven to work in the past.

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  LPTSRV [10.10.100.1]
  2    36 ms    30 ms    28 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    26 ms    28 ms    30 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    14 ms    12 ms    13 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    26 ms    26 ms    26 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    32 ms    29 ms    34 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    30 ms    31 ms    31 ms  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8    37 ms    42 ms    54 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    54 ms    52 ms    55 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    53 ms    54 ms    55 ms  64.86.85.1
 11    53 ms    54 ms    52 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    53 ms    55 ms    52 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    57 ms    55 ms    55 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    54 ms    55 ms    55 ms  66.198.96.50
 15    51 ms    54 ms    54 ms  192.34.76.2
 16    52 ms    52 ms    53 ms  199.91.189.234
 17    54 ms    55 ms    55 ms  199.91.189.74

Trace complete.

When my route is clean, my gameplay is clean. Is it SE's responsibility to address the odd hiccups I get at hop 1 when others in the house are streaming video to the Roku's? Is it SE's responsibility to address the high utilization in Conway and Columbia that continually inject anywhere from 20 to 50ms extra lag (hops 2 and 3). Is it SE's responsibility to address any over utilization that may occur anywhere along the 7 or so hops where TATA is part of the equation (the AS6453 hops...that is the ISP that my ISP is currently assigning for peering to get to Ormuco-Montreal)? Is it SE that is responsible for catching problems in the Raleigh-Durham/Charlotte segments within Time Warner's network and getting my route changed to Atlanta, switcing my peering partner to Cogent? No....that all falls under the scope of my ISP and their peering partners to manage.

[Vanicent]

How is it SE's responsibility to fix issues that are falling within the scope of our ISP's or even our own local networks? Vanicent's issue apparently involved local hardware....clearly not SE's responsibility to address.

I have to admit, that was something I'd considered from the start as a second-to-last resort. I was surprised that it worked, and it wasn't a fluke as I've used both Steam and Final Fantasy XIV at least twice each since, but glad as I know I can try it again if necessary.
Also, just for information, my router is one of the original Virgin Media "SuperHubs", which I'd never had a major problem with until this firmware update, but to be fair, it was solvable.