90K, Error 2002, Lag, Square Enix Please do Something.

[lordparanoia]

I opened a topic one week ago, and still received no reply.
I'm still having this issue:
- when I try to login sometimes i have error 2002 or error 90k before to login.
- when I'm playing I have MANY 90k errors and spike lags.

This game is actual unplayable.
I contacted my IP and I have:
17 Mb download
Ping 20
Upload 0.8 mb

I haven't problems with my IP, th eproblem is confined to Final Fantasy XIV: A Realm Reborn.

I honestly don't get why nobody seems to be able to do something.
I don't want to look unpatient or rude but I don't pay to play a game that crashes every 5 minutes.

[Raist]

If it were a DDoS, it would be affecting large numbers of people en mass, which it is not. It is more likely an issue along your route to the servers. In most cases, we see problems "isolated" to traffic coming through specific corridors or even a specific carrier along the routes. Lately, one of the more common carriers/regions we are seeing the issues are along Level3 segments coming through/around the North East of the US. This is something your ISP can and should investigate on your behalf, since it is their policies that are ultimately determining which route you take to get to Ormuco (SE's ISP).

Need to push to get in contact with your ISP's Tier3 support team (you typically are only dealing with tiers 1 and 2 when talking to the help desk or local technicians that come check your lines). This is typically an issue that exists beyond your local connection and it thus outside of their ability to properly address--why you need Tier3 (sometimes referred to as Engineering). If you cannot/aren't willing to do some of the legwork to gather trace/ping data for submission to both some of the SE servers and other online servers to draw a comparison between the quality of routes or to demonstrate the packet losses that are taking place, at least provide them some known addresses they can use for testing. I will post the registered DNS names for the 6 lobby servers...this will help them identify at least 2 of the 4 subnets that are used by the client (the other two are only for a couple addresses, but they are in the same location and hosted by the same companies, so the ASN's will remain constant):

Lobby Servers in Canada (currently for NA/EU):
neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com

Lobby Servers in Japan:
neolobby01.ffxiv.com
neolobby03.ffxiv.com
neolobby05.ffxiv.com

[Rachel_falcon]

I am having this exact same issue, I spoke to my ISP and they said the problem was with the game, the game have become so laggy and unresponsive, with the 9000 error so often it have become unplayable, glad to see im not the only one.

[Raist]

I am having this exact same issue, I spoke to my ISP and they said the problem was with the game, the game have become so laggy and unresponsive, with the 9000 error so often it have become unplayable, glad to see im not the only one.

DId you talk to anyone higher up than the team that answered the phone? That sounds like a typical Tier1 response. They veryfiy that your local connections to their localized network segments are good...but not anything beyond that path. Here is a sort of visual to demonstrate what I am talking about:

 0  G75VXLAP [10.10.100.10]
 1  LPTSRV [10.10.100.1]
 2  cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
 3  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
 4  24.31.196.212
 5  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
 6  bu-ether44.atlngamq46w-bcr00.tbone.rr.com [107.14.19.46]
 7  107.14.19.11
 8  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
 9  be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
10  be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
11  be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
12  be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
13  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
14  38.122.42.34
15  192.34.76.10
16  199.91.189.242
17  199.91.189.74

That is the route I get assigned by Time Warner to get to my lobby server. Notice the different names at the ends of the hops that resolve a DNS name. Those are managed by different companies...who Time Warner has entered into agreements with to route me to other people's networks. The guys that answer the phones or come look at your lines typically can't do anything past hop 2 on that list, at best hop 3. ANYTHING that occurs beyond that point must be handled by a higher department. The guys that for certain can look into such issues and request the needed escalation are Tier3 (in some organizations, Tier2 may be able to...but for certain, it is always Tier3 or higher that has the tools and authority needed).

[Rachel_falcon]

After a few more phone calls they said that there was nothing that could be done, even after being transferred multiple times, I was told that the problem was not with them. after reading these forums its clear this is a problem that lots of people seem to be having. I'm just hoping its fixed with the patch 2.5

[Raist]

After a few more phone calls they said that there was nothing that could be done, even after being transferred multiple times, I was told that the problem was not with them. after reading these forums its clear this is a problem that lots of people seem to be having. I'm just hoping its fixed with the patch 2.5

And most the time we find problems are along their routes... might want to run some traces yourself. It's pretty easy to spot. And if they refuse to help over the phone, take it to their forums/twitter/facepook/email if you have to. There is always a higher tier you can go to to get help.. all the way up to the admins of the top tier providers your ISP is partnering with.