Only thing you can do is vote with your feet/wallet. I went from a year of flawless play to five days of straight unplayabilty.
So I turned off my renewing subscription. I have 42 days left on my account. That's their countdown to fix it.
-
05-23-2018, 10:36 AMGaealiege
-
05-23-2018, 12:20 PMrulerofsaturn
I live in Sacramento, California and during prime time my connection to Japanese servers in FF11 is better. The server is in the same city as me and I want it back in Canada because at least I can play consistently. The issue is with the NTT nodes and has been for nearly a year. At this point I dread doing anything on ff14 when I get home because I don't know how bad the lag or packet loss will be.
I have been hopeful that at some point the issue will be resolved(or at least mitigated), but given last weeks response that seems unlikely. Since the service I am getting is too poor to use adequately I have canceled my automatic renew. My boyfriend has also done the same. -
05-23-2018, 12:36 PMdark494
We got tired of posting tracert after tracert in the other thread since they moved the servers 1 year ago. It's always been bad and it's always been NTT's fault and SE has consistently refused to do anything about it. They chose this partnership with NTT and they're going to reap what they've sowed. This cycle just never ends.
Consider my subscription cancelled. -
05-23-2018, 01:37 PMZeonx
Just a second opinion my cousin had same thing with NTT but he decided to change all cords and had the internet company come out and change the ones on outside due to they were outdated from back in the 80's I suggest you check the cords they might be out of date and picking up noise.
new cords are better and seems to got rid of his issue.
also note the guys who came out found out another company had installed a noise filter on the end of his cord running to his out which lowers the noise so that others dont get messed up but lowers quality of your internet and signal.
it was this orange tag and that orange filter they removed it and everything went back to normal. -
05-23-2018, 01:42 PMKerwinI did that a little over a year ago and have had many techs out here since then as well as over the phone customer support. Both my ISP and I are in agreement that NTT is to blame for this connectivity issue and they have informed me that there is nothing they can do. Though thanks for your input, this problem lies with Square Enix.Quote:
Originally Posted by Zeonx
-
05-23-2018, 01:43 PMZeonxyou see that orange tag he had that and that orange thing on the end that screws on messes with your internet it blocks signals so that others don't get messed up.Quote:
Originally Posted by Kerwin
they removed it off his and it fixed it. thing is he had to push them to come and fix it and it was messed up for months.
sometimes it can be under the road on main line and yes he lives right near where the servers are and was getting drops from NTT but after that thing was removed it seem to fix it.
http://i.imgur.com/wFFlMNB.jpg -
05-24-2018, 07:20 AMdark494It's absolutely NOT this. It has nothing to do with this recurring problem.Quote:
Originally Posted by Zeonx
-
05-24-2018, 11:56 AMKerwin
As of 10:00pm CST. Again. Every night.
Guess what? I was forced to leave the new lighthouse 24 man raid because of this again! Thank you for ruining the experience! Thank you for fixing this problem! :mad:Code:Tracing route to 204.2.229.97 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.0.0.1
2 10 ms 9 ms 10 ms 96.120.24.33
3 9 ms 11 ms 12 ms te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
4 8 ms 8 ms 16 ms 162.151.37.113
5 12 ms 12 ms 9 ms be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
6 11 ms 12 ms 11 ms be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
7 14 ms 12 ms 14 ms be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
8 15 ms 17 ms 14 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
9 12 ms 12 ms 12 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
10 187 ms 181 ms 181 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
11 12 ms 16 ms 19 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
12 * 183 ms 187 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 184 ms 197 ms 187 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
14 189 ms 185 ms 200 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
15 192 ms 187 ms 178 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 * * 191 ms 204.2.229.234
17 180 ms 183 ms 187 ms 204.2.229.97
Trace complete.
-
05-24-2018, 04:32 PMArtuir
I took this 10 minute snapshot while doing the new 24-man raid, but this problem has been happening for several months now.
https://i.imgur.com/YCZ7kxJ.png - a 10 minute snapshot taken using Pingplotter. Red bars = no data sent to or recieved from game servers (and as you can see from the bar graph on top, that all starts when the data hits NTT servers)
ISPs will not fix this routing issue. Us customers cannot fix this. This requires some work from your end, SE. Anyone blaming anything other than NTT servers directly has no idea what we're talking about. -
05-24-2018, 06:38 PMMesarthim
That's just depressing. I'm affected too but since I play from hawaii I always have around 100 ping anyway. It must really suck if you live near the servers as the impact is much more severe.
Seriously just what is it going to take for a real reply from Square Enix? And I'm not talking about the unhelpful moderator responses telling us to up open ports up or talk to our ISPs (no offense forum employees).