Yes I have to echo everybody's sentiment here in that it would be nice to hear something before the expansion early access. I'm still holding off on buying it till I see some sort of improvement or response in regards to this issue because there isn't much reason for me to buy it when I will not be able to raid with my static anyways due to being completely unable to play much of the time. And yes, the issue is literally only getting worse for me and not better. Another trace route to show along with a bit of my info again.
Location: Pennsylvania, USA
Internet Provider: RCN Cable
Traceroute: https://gyazo.com/89dadf4410be8ded8e3af666ac1e8d2a
And just copy paste of the text:
Tracing route to 204.2.229.9 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 9 ms 8 ms bdl1.drf-ubr1.atw-drf.pa.cable.rcn.net [10.19.0.
1]
3 9 ms 10 ms 12 ms bdle5-sub201.aggr2.atw.pa.rcn.net [208.58.240.19
5]
4 11 ms 10 ms 11 ms tge0-1-0-3.core2.phdl.pa.rcn.net [207.172.19.140
]
5 12 ms 10 ms 12 ms bdle2.aggr1.phdl.pa.rcn.net [207.172.15.38]
6 11 ms 10 ms 12 ms ae51.bar2.Philadelphia1.Level3.net [4.16.126.149
]
7 * * * Request timed out.
8 55 ms 15 ms 13 ms NTT-level3-90G.NewYork1.Level3.net [4.68.110.74]
9 15 ms 14 ms 19 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.6
1]
10 89 ms 76 ms 74 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.1
3]
11 75 ms 78 ms 77 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.5
4]
12 96 ms 88 ms 89 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.1
24]
13 111 ms 116 ms 95 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.
175]
14 138 ms 93 ms 92 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
1]
15 113 ms 96 ms 92 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
16 93 ms 93 ms 94 ms 204.2.229.234
17 92 ms 93 ms 95 ms 204.2.229.9
Trace complete.
Ridiculous ping spikes and inconsistancy. And this happens every single day, sometimes for extremely long periods. I really wanna enjoy Stormblood but I'm not gonna waste money on something I can't actually enjoy. I really hope something is done or at least acknowledge what is happening and that work is being done to fix it or if it can't be helped at the very least.
is SE even aware of the constant packet loss coming from 204.2.229.234 for east coast people?
Not to be excessively sarcastic, but I wonder if they're aware that we're still waiting for them to reply to their own official thread. Come on, SE, we're paying customers. You can at least give us lip service and say you're still looking into it or something.
|
![]() |
![]() |
![]() |
|
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.