Game has become unplayable due to latency since the 18th

[Chap_]

While I do appreciate the reply, you paste the same thing into everyones post. EVERYONE is having this issue on this forum. I understand you say its out of SE control but when a good chunk of the FFXIV population is experiencing these issues, clearly SE needs to take control. No other game has these issues.

[Raist]

While I do appreciate the reply, you paste the same thing into everyones post. EVERYONE is having this issue on this forum. I understand you say its out of SE control but when a good chunk of the FFXIV population is experiencing these issues, clearly SE needs to take control. No other game has these issues.

Not true. Many other games have reported these EXACT same issues for nearly 20 years. It happens off and on, but if you did a little googling you will find issues cropping up for many games and see some common names keep showing up---Level3, TATA (AS6453), Cogent, GTT/TiNet/SPA, XO, and a few others. It will also be bound to some popular companies as well--like EA and Blizzard. TWC has had several runs on it's forums in the past year for WoW, Diablo3, GW2, LotR, LoL... just to name a few. And if it wasn't something funky on TWC's end, it was most frequently pointing at Level3 or TATA, occasionally Cogent.

Go ahead and google this phrase: "WoW high latency and disconnects" and notice how many hits you get--north of 20,000. Notice how many were fairly recent. You may also notice that while you type it auto-fill may try to point you to a query with THIS year in it. FFXIV is NOT some special snowflake with this issue.

Here is a link, just in case you can't be arsed with actually doing the query your self:
https://www.google.com/?gws_rd=ssl#q...%20disconnects
The top hit is a link to the exact page from Blizzard I posted earlier...updated Jan. 27, 2015. Take some time to read posts linked directly from that query. You will see some going back as far as 2011 that point the finger at specific ISP's that were having issues---and it wasn't always Blizzard or Microsoft at fault, but you will see it being discussed how it is the ISP's involved along the route.

Than there are all the filings at the FCC from both TATA and Level3 about ISP's not operating under fair practices, the Comcast/Netflix scandal... all the things that have led up to the great Net Neutrality debate... there is basically a big pissing contest amongst the ISP's. More specifically, our ISP's not wanting to expend the resources upstream from our modems to properly support all the bandwidth they've been selling to us locally.

And... yes... I do post it a lot, because I have a lot of experience with the issue. A lot of experience resolving the issue through my ISP I might add. If you truly are aware of all my postings on the matter, that should be readily apparent... as I and others have attested to the fact that going through our ISP improved the situation for many, and there are others that have asserted that when they can't make headway with their ISP they improve things by using a VPN. In either scenario, it affirms that there are routing issues in play--because that is what we are changing that is showing improvement.

As for the traces you recently posted just after the post I am replying to, there appears to be an issue at/around the exchange point from GTT/TiNet into Ormuco's network. That is the routing partner YOUR ISP has assigned to you for getting into Ormuco. It is a group that has been seen having issues frequently in the past. Haven't done a dig on your ISP yet, but they should have an agreement with at least one of the 4 other ISP's Ormuco peers with. If they are not willing to try to address any potential issues with the the GTT group, they can at least try to alter your routing to get around that. We have very recently seen more evidence of issues with specific ISP's. In just the past few days, there were posts about people not getting on at all with their ISP, but got on with a VPN. Others reported they got back on after resetting their modems and getting assigned new IP addresses (effectively, they forced a DHCP lease renewal--probably changed their gateway also). It was just confirmed there are outages tied to Charter that are currently causing problems as well. These all support the notion there are problems in route to the servers that our ISP's need to get involved with to address properly.

Edit:
Ok, just looked up an ASN for fuse.net, and they have peering with many other ISP's---one of them is Cogent, who Ormuco peers directly with. This was a lookup based on one of their name servers, so there is at least one potential alternate route that can be taken:

AS3257 Tinet SpA
AS2828 XO Communications
AS174 Cogent Communications
AS6939 Hurricane Electric, Inc.
AS30023 CyrusOne LLC
AS5580 TripartZ B.V.
AS9002 RETN Limited

***I did a second look up on your gateway IP, and it was in the same subnet so it returns the same ASN, so the IP4 peer list does apply to your connection as well.

If you look further into their peering arrangements, you will see that in a bit of a round-about way they can also get to TATA (AS6453), as well as Level3 (AS3459, AS3356)--two other ISP's that Ormuco peers with directly. FUSE.net also peers directly with Hurricane, which for some regions could open up a host of other paths into several of the 5 peers that Ormuco uses. So your ISP does in fact have options for helping to resolve an alternate path for you if they aren't going to work with GTT/TiNet on your behalf--even though they should because they have entered into a peering arrangement with them and that is who your ISP has put you with to get to Ormuco.



Source for all of this info: http://bgp.he.net/AS6181#_asinfo

Edit2:
EEP! Just noticed your ISP looks to be tied in with Cincinnati Bell. While they don't seem to get as many reports as others in Ohio (AT&T and TWC are a MESS)... Ohio itself has been fraught with issues for many ISP's for some time now. Infrastructure problems abound throughout the region, more specifically to the north and east. Unfortunately that is likely where you are getting routed through.