Need to trace to the Canadian server. There should be at least 2 connections opened by FFXIV--that one is to Japan, and typically those are not causing problems for those having issues with the NA/EU servers that are in Canada.

As mentioned earlier, the 124 address is the JP one that spends most of it's time idle for those on the NA servers. The problems seem to be with the more active session to the CA server. So far, the ones I have seen posted have started with 199, but that's been for NA users--EU might be in a different subnet. Considering you are coming through the Louisiana area, I'm guessing you are in the US, or at least hiting a NA server? If so, look for another session being used by FFXIV that starts with 199 and trace to that IP and open a support ticket with your ISP (and optionally SE), forwarding that trace to them. If the other FFXIV session doesn't start with 199, but something other than 124 or 202 (another JP block, houses SE's DNS servers among other things)--try tracing to that one instead.

It might be helpful to include the name of the group that manages the bad segments if you can. You may see these show up: cogentco, i-web, or as6453. The first two are the actual names of the providers, the last is used by TATA for a lot of their hops. Probably 90% or more of the time, it winds up being one of those three companies that is having issues--Cogent, i-Web, or TATA. Sometimes the i-Web hops won't say i-web though, as well as some of the TATA won't say as6453--but cogentco is pretty consistent for Cogent Communications. You can search on the IP address at www.arin.net and get the name of the group if you want to include it in your support request, as well as lots of other information. Makes it a bit easier to keep up with who keeps showing up when you make note of those common names, so you may know at a glance if they've done something different with your routing after you submit a ticket.

People can "poo-poo" on this as much as they want, but it CAN actually bring about a change in your routing-hopefully for the better as a whole. Back when TWC was partnered with RR, I had a direct email and phone to tech's in both Myrtle Beach and Columbia, and when I found failing segments in Virginia and Nova Scotia that were affecting my FFXI connections (separate instances, years ago), they switched my DHCP and DNS on my modem and routed me differently. Ever since they started homing me out of Charlotte a few years back, I haven't had any need to have it redone. I'm sometimes getting a little more latency then when I was on a closer network for my 4th hop, but it has had fewer problems with packet loss and such.