NTT Chicago Packet Loss

[WindDrake]

Tracert says it all.

Tracing route to 204.2.229.86 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 96.120.26.133
3 9 ms 9 ms 11 ms 96.110.155.169
4 12 ms 11 ms 11 ms 162.151.184.65
5 14 ms 15 ms 14 ms be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
6 13 ms 15 ms 12 ms be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
7 12 ms 20 ms 13 ms be-1302-cs03.350ecermak.il.ibone.comcast.net [96.110.36.105]
8 12 ms 11 ms 13 ms 96.110.37.26
9 21 ms 14 ms 14 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
10 144 ms 144 ms 127 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
11 11 ms 12 ms 13 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
12 103 ms 102 ms 93 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 126 ms 126 ms 113 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
14 92 ms 108 ms 100 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 139 ms 148 ms 137 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 88 ms 91 ms * 204.2.229.234
17 136 ms 125 ms 122 ms 204.2.229.86

Trace complete.

This is the same issue that cropped up a few weeks ago and lasted a couple of days. Repeated tracert show packetloss between ae-26 and ae-3 inside NTT's Chicago infrastructure.

[Jarrell]

Same issue. I am a Comcast customer in the AZ state area. As of this evening, I encounter unplayable lag spikes of 2-20 seconds, to full on 90006 disconnects in numerous zones (Copied Factory, Gyr Abania, Crystarium). Up until today, I have had zero latency issues.

Please see Tracerts below. First is direct (local IP redacted). Second is via VPN proxy to New Jersey, third is New York, and Fourth is Toronto, CA (less than 200 miles from your data center). All have reasonable latency until entering the NTT network.

AZ to 204.2.229.86

1 12 ms 10 ms 20 ms xxx.xxx.xxx.xxx
2 21 ms 10 ms 8 ms po-301-1204-rur02.snyder.az.pima.comcast.net [68.87.172.201]
3 11 ms 11 ms 10 ms be-6-ar02.pimaco.az.pima.comcast.net [162.151.153.157]
4 24 ms 30 ms 21 ms be-33653-cr02.losangeles.ca.ibone.comcast.net [68.86.93.117]
5 21 ms 21 ms 24 ms be-11599-pe01.losangeles.ca.ibone.comcast.net [68.86.84.194]
6 23 ms 21 ms 21 ms 50.242.151.62
7 43 ms 41 ms 43 ms ae-13.r01.lsanca07.us.bb.gin.ntt.net [129.250.2.187]
8 104 ms * 131 ms ae-3.r23.lsanca07.us.bb.gin.ntt.net [129.250.4.106]
9 88 ms 94 ms 93 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 104 ms 94 ms 100 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 81 ms 87 ms 105 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 44 ms 39 ms 38 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 85 ms 84 ms 75 ms 204.2.229.234
14 54 ms 43 ms 35 ms 204.2.229.86

NJ to 204.2.229.86

1 79 ms 87 ms 79 ms 10.81.0.1 (high local latency is due to VPN from AZ to NJ)
2 113 ms 87 ms 97 ms 23.226.128.241.static.quadranet.com [23.226.128.241]
3 78 ms 87 ms 77 ms 23.226.129.250.static.quadranet.com [23.226.129.250]
4 79 ms 78 ms * 38.142.118.169
5 79 ms 79 ms 78 ms 154.24.66.217
6 80 ms 79 ms 79 ms be2390.rcr23.jfk01.atlas.cogentco.com [154.54.80.189]
7 97 ms 79 ms 79 ms be2896.ccr41.jfk02.atlas.cogentco.com [154.54.84.201]
8 81 ms 80 ms 80 ms be3495.ccr31.jfk10.atlas.cogentco.com [66.28.4.182]
9 80 ms 79 ms 78 ms ae-13.r01.nycmny17.us.bb.gin.ntt.net [129.250.8.145]
10 * * * Request timed out.
11 104 ms 114 ms 102 ms ae-1.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
12 95 ms 102 ms 97 ms ae-4.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.163]
13 151 ms 149 ms 150 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
14 157 ms 158 ms 164 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
15 155 ms * 155 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
16 153 ms 154 ms 154 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
17 155 ms 152 ms * 204.2.229.234
18 154 ms 154 ms 153 ms 204.2.229.86


NY to 204.2.229.86

1 77 ms 80 ms 77 ms 10.24.0.1 (high local latency is due to VPN from AZ to NY)
2 80 ms 79 ms 88 ms 209.95.50.3.static.midphase.com [209.95.50.3]
3 79 ms 80 ms 78 ms 185.7.225.180.static.100tb.com [185.7.225.180]
4 81 ms 81 ms 82 ms be4450.rcr21.b007023-2.jfk05.atlas.cogentco.com [38.104.74.45]
5 79 ms 78 ms 97 ms be2809.ccr31.jfk05.atlas.cogentco.com [154.54.81.201]
6 79 ms 79 ms 80 ms be2073.ccr31.jfk10.atlas.cogentco.com [154.54.0.230]
7 82 ms 80 ms 81 ms ae-13.r01.nycmny17.us.bb.gin.ntt.net [129.250.8.145]
8 * * * Request timed out.
9 105 ms 98 ms 109 ms ae-1.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
10 101 ms 96 ms 98 ms ae-4.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.163]
11 153 ms 151 ms 150 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 155 ms 154 ms 156 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 154 ms 155 ms 154 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 156 ms 154 ms 156 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 154 ms * 153 ms 204.2.229.234
16 172 ms 153 ms 154 ms 204.2.229.86

Toronto, CA to 204.2.229.86

1 78 ms 76 ms 78 ms 10.81.0.1 (high local latency is due to VPN from AZ to Toronto, CA)
2 79 ms 79 ms 78 ms 184.75.220.177
3 80 ms 79 ms 78 ms te0-0-1-17.222.ccr32.yyz02.atlas.cogentco.com [38.88.240.133]
4 88 ms 85 ms 85 ms be2994.ccr22.cle04.atlas.cogentco.com [154.54.31.233]
5 93 ms 95 ms 92 ms be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
6 93 ms 95 ms 93 ms be2766.ccr41.ord03.atlas.cogentco.com [154.54.46.178]
7 94 ms 94 ms 94 ms ae-11.r08.chcgil09.us.bb.gin.ntt.net [129.250.9.121]
8 107 ms 93 ms 93 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
9 152 ms 152 ms 150 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 155 ms 152 ms 153 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 154 ms 155 ms 153 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 156 ms 154 ms 156 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * 155 ms 154 ms 204.2.229.234
14 171 ms 154 ms 155 ms 204.2.229.86


External inquiries into NTT networks such as mentioned in linked reddit thread are met with canned unhelpful answers by NTT staff: https://www.reddit.com/r/ffxiv/comme...ng_south_east/

Please advise.

[Carmesi]

Having the same issue out of Seattle. A few people in my FC are having the same lag issues.

Tracing route to 204.2.229.11 over a maximum of 30 hops

1 5 ms 1 ms 1 ms xxx.xxx.xxx.xxx
2 11 ms 19 ms 17 ms 96.120.102.177
3 19 ms 28 ms 18 ms 96.110.251.21
4 15 ms 18 ms 19 ms po-2-rur02.federalway.wa.seattle.comcast.net [69.139.163.106]
5 24 ms 28 ms 28 ms be-38-ar01.seattle.wa.seattle.comcast.net [69.139.164.65]
6 23 ms 12 ms 15 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
7 20 ms 30 ms 27 ms be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]
8 * 160 ms 133 ms ae-31.a00.sttlwa01.us.bb.gin.ntt.net [129.250.66.149]
9 159 ms 158 ms 158 ms ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
10 134 ms * 146 ms ae-5.r23.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
11 * 147 ms 158 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
12 160 ms 161 ms 169 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 169 ms 159 ms 158 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 163 ms 159 ms 158 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * 168 ms 157 ms 204.2.229.234
16 157 ms 158 ms 160 ms 204.2.229.11

Trace complete.

This is one of the cleaner transmissions in the past few hours. When things are running smoothly, I see anywhere from 40-60ms at most on all hops. As it stands, my connection is too unreliable to be able to do anything but solo content.

[Rarrum]

I'm seeing the same thing on trace route from seattle area comcast. 204.2.229.234 is sometimes dropping things. Caused some pretty bizarre on and off lag in PotD on Aether this evening.. I had to abandon my plans to do a solo run for the day.

[Einmimiria]

Good afternoon and thank you for posting on the Final Fantasy XIV Technical Support Forums.

I apologize for the delay in our response.

The troubleshooting we provide for connection related issues involve only your home network. If you are experiencing routing issues along your way to the server, this troubleshooting will not directly affect the error you are experiencing.

In this case, I'd recommend contacting your ISP and making a report with them.

Thank you for visiting the Final Fantasy XIV Technical Support Forums.