Regarding Reports on Recent Connection Problems with the NA Data Center

[Riko_Futatabi]

First time checking it with a VPN during peak time. It's pretty awful!

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             10.254.49.1 -    0 |  126 |  126 |    0 |    0 |    0 |    0 |
|                            10.254.254.1 -    0 |  126 |  126 |  146 |  147 |  194 |  147 |
|                           10.255.251.10 -    0 |  126 |  126 |  147 |  148 |  200 |  147 |
|                              23.92.24.2 -    0 |  126 |  126 |  147 |  149 |  205 |  153 |
|                          173.230.159.10 -    0 |  126 |  126 |  147 |  150 |  238 |  149 |
|ce-0-18-0-1.r02.snjsca04.us.bb.gin.ntt.net -    0 |  126 |  126 |  148 |  151 |  197 |  150 |
|     ae-3.r00.scrmca02.us.bb.gin.ntt.net -    0 |  126 |  126 |  152 |  154 |  200 |  152 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net -    0 |  126 |  126 |  152 |  154 |  209 |  157 |
|                           204.2.229.234 -   40 |   51 |   31 |  152 |  161 |  295 |  156 |
|                            204.2.229.10 -    0 |  126 |  126 |  151 |  153 |  210 |  152 |
|________________________________________________|______|______|______|______|______|______|

40% packet loss! o.O

[gumas]

just tried a new char in ultros (NA) and typhon (JP), same result, was doing normal quest and got booted with 90002 error.

i know the moderator wont see this anyway, but at least AT LEAST could you give us news or update or anything regarding this error? even if the answer is "sorry currently we cant fix this blablabla" is fine, its better than leaving us in the dark!

what make some people mad is how the SE are so unresponsive, you guys fast with "please give us net info/tracert whatever" when someone got problem with it but, for some reason after we give you our info you guys just... gone, nothing nada.

then suddenly "because the previous post has given no update regarding blablabal we treat this problem as SOLVED"

like... really?

[Thaeryden]

I liked this part of the update in the OP: "If you wish to make detailed reports about your connection difficulties, we recommend contacting your local ISP directly to try to improve your connection with the upstream ISP."

I contacted Comcast, you know what they said? "Thank you for sharing with us your concerns, and although we do strive to improve performance within our networks, it is unfortunate that the service provider in question is not part of our network. That being said, we will pass this and any pertinent information on to our support teams but in any event it is unlikely that we will be able to do anything to help resolve this issue." etc etc etc.

I wonder if the FCC ever concerns itself with issues like this? More data besides our/FFXIV gaming data has to go through NTT, right? If the FCC will light a fire under my ISP's behind because of poor internet connections to a single residential customer... why ~wouldn't~ the FCC focus on something with the potential to affect hundreds of thousands of users (if not millions) ? It's just a thought.

[Veliena]

@ Thaeryden, I was told basically the same thing by my isp. Its not their network so they can't do anything about it. Everyone on this thread shows the same thing, NTT is the problem, how can this problem not be dealt with by now?

[Kerwin]

@ Thaeryden, I was told basically the same thing by my isp. Its not their network so they can't do anything about it. Everyone on this thread shows the same thing, NTT is the problem, how can this problem not be dealt with by now?

We are considered a minority that is expendable in the companies eyes. At least that's how I feel.

[Callinon]

We are considered a minority that is expendable in the companies eyes. At least that's how I feel.

There are actually more NA players than there are JP. You'd think that would at least make them concerned about losing 40% of their global population. Guess not though.

[Utsuho_Zomori]

I've been having large quantities of 90007 errors specifically that started on Tuesday and has continued the last several days. Usually disconnects were few and far between with a 90002 or 90006, but the last few days its been almost exclusively 90007 errors very frequently. It's really starting to get on my nerves considering its been canceling queue's I've been in for 20+ minutes multiple times, and destroyed 300k+ in materials over the last few days when trying to craft and DCing in the middle of something that uses an ala mhigan alchemic.

doing a tracert gave me this:

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

1 2 ms 3 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 15 ms 7 ms 7 ms 47.199.160.1
3 10 ms 10 ms 9 ms 172.99.45.74
4 13 ms 13 ms 13 ms ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
5 12 ms 15 ms 15 ms ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
6 * 15 ms 12 ms lag-101.ear3.Miami2.Level3.net [4.15.156.29]
7 14 ms 13 ms 13 ms NTT-level3-80G.Miami.Level3.net [4.68.127.54]
8 92 ms 90 ms 90 ms ae-7.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
9 12 ms 15 ms 14 ms ae-3.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.110]
10 40 ms 37 ms 38 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
11 89 ms 89 ms 87 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
12 151 ms 91 ms 90 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 91 ms 92 ms 90 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 92 ms 91 ms 93 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 120 ms 119 ms 111 ms 204.2.229.234
16 92 ms 89 ms 92 ms 204.2.229.9

Trace complete.

I've done it multiple times and that 6th node almost always has an asterisk on the first ping but IDK if that's a reason for concern. The oddest part is the disconnects aren't coupled with lag. Almost every 90007 error was extremely abrupt where whatever I was doing beforehand was going perfectly fine with my average latency. I've pressed actions like tri-disaster that have executed less than half a second before a sudden black screen with 90007 error, and when I reconnect in I see my DoTs up on the target. I've tried Using Mudfish as a VPN for FFXIV but that didn't seem to stop or even decrease the 90007 errors at all.

One thing I must mention is that last week (4-5 days before last Tuesday when the issues started) my SSD failed and I had to get a new SSD and re-install everything including windows 10 and FFXIV. I did fully update Windows 10, but I've realized I haven't updated my Nvidia drivers for my gtx 1070. I just did that and will edit this post if that seems to fix the problem, though I don't have much hope of it doing so.

[gumas]

another day another 90002 error

patch 4.3 is coming closer... i want to play but the 90002.... ugh

[gumas]

*update*

- make a new char in ultros server (NA) and i still get 90002 error
- make another char in garuda server (same jp region but different servee) also getting 90002 error
- use vpn mudfish, still getting 90002 error (mudfish set to elemental server, node setting = auto)
- turn off firewall, still 90002 error
- delete ff14 and fresh install, still 90002 error
- format my pc and fresh install (again) ff14, 90002 error
- internet explorer setting according to mod suggestion, still 90002 error

All of that with testing with other online game (i use wow, bdo, secret world, even counter strike, all in 2 hours play more or less) and NONE of it give me anything close to network problem, not even a lag spike.

The only thing i havent try yet is...
1. bring my friend laptop/pc with ff14 installed and try playing from his laptop/pc using my current isp
2. change my isp

If method 2 still get me 90002 error, then the problem is from you SE period full stop

I'll post again in a week

[Callinon]

90002 isn't a network error, it's a client error.

I had the same problem for a long time and what I discovered was that my CPU was actually missing a cycle every now and then which threw off my system clock by fractions of a second. Apparently that's enough for the client to 90002 you because it thinks you're speed hacking or something, I don't know what it thinks it's doing. The FFXIV client is SUPER paranoid about any kind of system clock issues. The way to test for this is to try the game on a different computer on the same network.