-
Lag
http://forum.square-enix.com/ffxiv/t...ag-disconnects
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 9 ms 10 ms 10 ms 96.120.24.33
3 9 ms 9 ms 17 ms te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
4 9 ms 9 ms 10 ms 162.151.37.113
5 10 ms 12 ms 13 ms be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
6 12 ms 13 ms 12 ms be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
7 13 ms 12 ms 22 ms be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
8 13 ms 17 ms 12 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
9 12 ms 11 ms 14 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
10 75 ms 73 ms 82 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
11 19 ms 22 ms 13 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
12 76 ms 152 ms 146 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 115 ms 114 ms 138 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
14 183 ms 189 ms 190 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
15 151 ms 140 ms 136 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 * 84 ms 80 ms 204.2.229.234
17 77 ms 71 ms 85 ms 204.2.229.97
Trace complete.
PLEASE DO NOT tell me to contact my ISP when this is on Square Enix. Sweaping my thread into the "seperate support" forum to lock it away and telling me to contact my ISP is upsetting. I have already. I've done on more occasions then I ever needed to.
This issue with NTT has not gone away and thus continues to effect your service EVERYDAY. "Not the datacenters fault" is a poor excuse of an investigation when you don't consider your own ISP into the factor.
The ultimate issue is this:
Your ISP, your fault. Not mine.
My ISP as seen with my tracert is clean all the way up to your network. I tire of your team's inconclusive tech support.
NJ and Sacramento! THERE ARE YOUR NODES. PINPOINTED!
-
I would also like to chime in and add that the "sanca" nodes are problematic too. Honestly I'm just figuring they are too cheap to spend the money to properly investigate the problem. They don't even bother responding to threads properly about this NTT subject.
ae-5.a00.lsanca20.us.bb.gin.ntt.net
ae-3.r01.lsanca20.us.bb.gin.ntt.net
ae-8.r23.lsanca07.us.bb.gin.ntt.net
ae-12.r22.snjsca04.us.bb.gin.ntt.net
ae-19.r01.snjsca04.us.bb.gin.ntt.net
ae-4.r00.scrmca02.us.bb.gin.ntt.net
xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net
A good place to start. In before they mention contacting your isp for some reason, telling you to open ports, or just ignore them again as per the usual.
-
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 10 ms 10 ms 96.120.24.33
3 9 ms 10 ms 11 ms te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
4 8 ms 9 ms 9 ms 162.151.37.113
5 10 ms 11 ms 16 ms be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
6 12 ms 12 ms 12 ms be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
7 12 ms 12 ms 12 ms be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
8 12 ms 12 ms 12 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
9 18 ms 14 ms 19 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
10 179 ms 185 ms 180 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
11 11 ms 11 ms 13 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
12 180 ms 180 ms * ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 183 ms 182 ms 194 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
14 181 ms 182 ms 184 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
15 * 184 ms 180 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 179 ms 184 ms 179 ms 204.2.229.234
17 175 ms 178 ms 190 ms 204.2.229.97
Trace complete.
-
I'm getting similar lag/DCs tonight and tracert shows the similar NTT problematic hops.
-
Last night was having bad lag as well. No other sites or applications were affected. Additionally it's been ongoing in Eureka where the R fluctuates from 0 to over 30,000 at times.