TDS customer also seeing ping jump once I hit 129.250.2.7
TDS customer also seeing ping jump once I hit 129.250.2.7
Tracing route to 204.2.29.122 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms RT-AC88U-14C8 [192.168.1.1]
2 12 ms 12 ms 18 ms 072-177-000-001.res.spectrum.com [72.177.0.1]
3 8 ms 9 ms 14 ms lag-60.hcr01ausutxla.netops.charter.com [24.27.12.85]
4 14 ms 8 ms 7 ms lag-21.ausutxla01r.netops.charter.com [24.28.90.72]
5 13 ms 15 ms 17 ms lag-22.rcr01dllatx37.netops.charter.com [24.175.41.46]
6 19 ms 19 ms 15 ms lag-24.dllstx976iw-bcr00.netops.charter.com [66.109.1.216]
7 37 ms 15 ms 16 ms lag-0.pr3.dfw10.netops.charter.com [66.109.5.121]
8 14 ms 30 ms 21 ms ae3.cr7-dal3.ip4.gtt.net [208.116.212.9]
9 19 ms 18 ms 16 ms ae0.cr11-dal3.ip4.gtt.net [89.149.139.201]
10 31 ms 24 ms 29 ms as2914.cr11-dal3.ip4.gtt.net [69.174.23.138]
11 15 ms 16 ms 17 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
12 52 ms 56 ms 46 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
13 158 ms 167 ms 159 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
14 163 ms * 167 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
15 172 ms 158 ms 157 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
16 * * * Request timed out.
17 166 ms 163 ms 160 ms 204.2.29.122
Lol yikes
Getting ~200 ms latency from Florida on Spectrum for Aether and Crystal DC. Really difficult in extreme or savage content to play on this ping, was around 40ms yesterday. No idea why Spectrum is having issues today all of a sudden.
It's not Spectrum, it's NTT. Their nodes are having issues and they're just pointing fingers at ISPs to try to misdirect peoples' blame.
Sure glad we had that Data Center upgrade.![]()
Tracing route to 204.2.29.122 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 8 ms 22 ms 10.30.96.1
3 14 ms 10 ms 36 ms 100.122.142.84
4 11 ms 8 ms 11 ms 100.122.141.96
5 23 ms 21 ms 20 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
6 25 ms 21 ms 21 ms dls-b23-link.ip.twelve99.net [62.115.14.38]
7 23 ms 22 ms 21 ms ntt-ic-325660.ip.twelve99-cust.net [62.115.156.249]
8 23 ms 19 ms 21 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
9 64 ms 68 ms 51 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
10 186 ms 169 ms 170 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 168 ms 164 ms 163 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 168 ms 169 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 165 ms * * 204.2.29.241
14 164 ms 164 ms 166 ms 204.2.29.122
Experiencing the same thing now (this is the first time I've had this problem at all in all of this)
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 10 ms lag-44.dtr01dntntx.netops.charter.com [159.111.145.106]
4 10 ms 24 ms 11 ms lag-31.rcr01ftwptxzp.netops.charter.com [96.34.113.254]
5 18 ms 14 ms 20 ms lag-806.bbr01dllstx.netops.charter.com [96.34.2.32]
6 27 ms 22 ms 16 ms lag-801.prr01dllstx.netops.charter.com [96.34.3.69]
7 18 ms 13 ms 14 ms dls-b23-link.ip.twelve99.net [62.115.180.82]
8 17 ms 15 ms 23 ms ntt-ic-325660.ip.twelve99-cust.net [62.115.156.249]
9 * 42 ms * ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 44 ms 55 ms 40 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 165 ms 183 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 149 ms 149 ms 152 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 154 ms * 152 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * 151 ms 204.2.29.241
15 * 156 ms 154 ms 204.2.29.122
Been experiencing this since just today.
Having the same issues in my household starting today.
Spectrum, not that it matters according to what's being posted in this thread about NTT.
Yep. Same issue here over on Primal. ALL INSTANCES HAVE BECOME UNPLAYABLE. All because of crippling lag and NTT. Seriously, they need to get this big fix because it's starting to cause major problems.
6/14 Update: My connection is back to normal, knock-on-wood. 60ms~, minimal packet loss.
Cox Internet user from Louisiana here also getting bogged down by the Sacramento NTT node
Tracing route to 204.2.29.122 over a maximum of 30 hops
1 2 ms 2 ms 2 ms
2 22 ms 12 ms 9 ms
3 33 ms 39 ms 15 ms 100.122.142.162
4 24 ms 33 ms 38 ms 100.122.141.74
5 24 ms 63 ms 27 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
6 21 ms 21 ms 22 ms dls-b23-link.ip.twelve99.net [62.115.14.38]
7 21 ms 20 ms 38 ms ntt-ic-325660.ip.twelve99-cust.net [62.115.156.249]
8 * 20 ms 24 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
9 * 47 ms 48 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
10 165 ms 165 ms 163 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 168 ms * 197 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 185 ms 192 ms 163 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * * * Request timed out.
14 184 ms 167 ms 166 ms 204.2.29.122
Don't try using BLM for anything with connection issues like this, hope NTT gets their gear in check soon.
Last edited by TyranHarasvelg; 06-15-2023 at 04:54 AM.
Mhm, doing my reclears, a lot of people are dropping out because of the insane lag. Spectrum, Charter and even a Cox member just now. Square and NTT have to resolve this. I don't even know if any VPN can help this time around .
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.