2002 Terrible Server Lag. SE please fix this and don't blame it on the users

[Mizukaru]

Just another 2002 page + the terrible lag issue that came with their prestigious emergency maintenance. Please fix this Asap.

[Raist]

Not always a problem at the end points (your client or SE's server). A very large portion of our issues are due in part (if not entirely) to issues with the routing your ISP's have concocted.

Run some traces to your game server (can find it by running resmon from your run/search box and watching what ffxiv connects to when you are logged fully into the game) as well as some other common sites like google, netflix, yahoo, TwitchTV, etc. to see if you spot highly erratic response times (or intermittent timeouts) along your routes. If you see them, forward the reports to your ISP's Tier3 support techs--they are the ones that know what to look for based on what shows up in those tracerts, and who to contact to fix your routing.

Your ISP has the service agreements with the people responsible for such third party segments where we keep seeing the problems (will show up with other ISP's domain names like level3, cogent, i-web, telia, TATA's as6453). SE is basically powerless to do anything about problems that occur outside of their internal network or on Ormuco or JP-NIC segments. At best, they can try to contact those 3rd parties on your behalf, but they don't have any enforceable service agreements with them... but your ISP does.

[Mizukaru]

Not always a problem at the end points (your client or SE's server). A very large portion of our issues are due in part (if not entirely) to issues with the routing your ISP's have concocted.

Run some traces to your game server (can find it by running resmon from your run/search box and watching what ffxiv connects to when you are logged fully into the game) as well as some other common sites like google, netflix, yahoo, TwitchTV, etc. to see if you spot highly erratic response times (or intermittent timeouts) along your routes. If you see them, forward the reports to your ISP's Tier3 support techs--they are the ones that know what to look for based on what shows up in those tracerts, and who to contact to fix your routing.

Your ISP has the service agreements with the people responsible for such third party segments where we keep seeing the problems (will show up with other ISP's domain names like level3, cogent, i-web, telia, TATA's as6453). SE is basically powerless to do anything about problems that occur outside of their internal network or on Ormuco or JP-NIC segments. At best, they can try to contact those 3rd parties on your behalf, but they don't have any enforceable service agreements with them... but your ISP does.

As much as I'd like to take this advice, as i mentioned in another thread, this issue is not based of the players ISP.
Reason 1: Players who have never had a problem with their internet till Emergency maintenance.
Reason 2: If this was ISP, why has over 20 ISP's coincidentally had the same issue within the past day from the emergency Maint.
Reason 3: The ping to Montreal (NA server) is that of what it is supposed to be with minimal packets lost. This was tested with other server hosts, 3 different Connection tester programs, and with and without battleping activated. However, when using an IP ping transfer to the IP address of the server/servers, it was indeed having issues through battleping / no battle ping. This leads to one conclusion: Using even professional proxy hosts / standard provider cause the same issue, but cause no issues with anything else (other games, downloads, daily internet life) This is purely SE's error.

[Raist]

As much as I'd like to take this advice, as i mentioned in another thread, this issue is not based of the players ISP.
Reason 1: Players who have never had a problem with their internet till Emergency maintenance.
Reason 2: If this was ISP, why has over 20 ISP's coincidentally had the same issue within the past day from the emergency Maint.
Reason 3: The ping to Montreal (NA server) is that of what it is supposed to be with minimal packets lost. This was tested with other server hosts, 3 different Connection tester programs, and with and without battleping activated. However, when using an IP ping transfer to the IP address of the server/servers, it was indeed having issues through battleping / no battle ping. This leads to one conclusion: Using even professional proxy hosts / standard provider cause the same issue, but cause no issues with anything else (other games, downloads, daily internet life) This is purely SE's error.

It all depends on the specific route being taken. Even with a VPN or proxy, you can still be hit by problems at a bad headend (like a 14 year old CMTS... grossly out of speck-- a jab at Time Warner Cable) or an overloaded backbone like the small handful feeding into Montreal from the US (/poke TATA, /slap Level3, /doubt Cogent).

This is a confirmed reality... and not just in the scope of FFXIV. It has held true for lots of games for nearly 20 years. Sudden spikes in traffic flow simply don't get adjusted to in a timely fashion because the analytics used to maintain/develop the routes are not able to keep up with the pace of the changes. It may take a full quarter or longer for some routes to be adjusted in some cases. But, if we get enough people proactive enough, it can lead to provisioning of new routes or at the very least to having them switch to a different route they already own. It has happened time and time again for a vast array of web services including but not limited to Blizzard Games and other game developers. In some cases, it has spurred some ISP's to enter into direct peering agreements specifically to support just ONE web service. For a somewhat recent example, you can find articles about this occuring last summer between Twitch.tv and Time Warner. It basically happened because the users identified an issue in route and enough people complained about it to their ISP. JustinTV has had similar issues addressed too if I remember right.

[Mizukaru]

mind replying to my questions on http://forum.square-enix.com/ffxiv/t...61#post2066061 I'm trying to figure out the steps i need to take to fix this.

[Zell]

I contacted Cogent Communications and told them about their ip address/hop 38.122.42.34. The operator said they are aware of the problem with the line and they are currently trying to fix it. They couldn't give me a time estimate as to how long it would take. All they said was that there were people on site, trying to isolate the line, and fix it asap.

[nicolasm]

I have the same problem since the last patch. Yesterday 10 times lost connection. When I trace the route to Montreal, I have several lost pakets.