Reporting Issues Resulting from the North American Data Center Relocation

[JunseiKei]

Type of Issue/Feedback:
Lag spikes and inconsistencies, leading to a large loss to the ability of being able to double weave oGCDs and reapplying DoTs at correct times, leading to a drop in performance.

Name of your Internet Service Provider (ISP):
Time Warner Cable.

State/Country:
North Carolina, United States of America.

Date/Time:
Any and all times, but most noticable during peak hours.

World Name:
Cactuar

Frequency:
It is largely limited to instances.

Pre- migration:

Tracing route to 199.91.189.46 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 16 ms 14 ms 142.254.207.201
3 25 ms 22 ms 26 ms cpe-174-111-105-173.triad.res.rr.com [174.111.105.173]
4 22 ms 42 ms 13 ms cpe-024-025-062-106.ec.res.rr.com [24.25.62.106]
5 24 ms 22 ms 27 ms 24.93.67.202
6 26 ms 30 ms 31 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
7 28 ms 24 ms 24 ms 0.ae2.pr0.atl20.tbone.rr.com [107.14.19.11]
8 3199 ms 2137 ms 1911 ms twc-telus.pr0.chi10.tbone.rr.com [66.109.9.70]
9 40 ms 45 ms 46 ms ae-2-12.bear1.Montreal2.Level3.net [4.69.203.129]
10 45 ms 42 ms 43 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
11 * * * Request timed out.
12 45 ms 42 ms 97 ms 192.34.76.2
13 45 ms 44 ms 62 ms 199.91.189.234
14 58 ms 42 ms 43 ms 199.91.189.46

Trace complete.

Post migration:

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 52 ms 14 ms 142.254.207.201
3 574 ms 28 ms 32 ms cpe-174-111-105-169.triad.res.rr.com [174.111.105.169]
4 19 ms 18 ms 15 ms cpe-024-025-062-106.ec.res.rr.com [24.25.62.106]
5 19 ms 38 ms 22 ms 24.93.67.202
6 29 ms 30 ms 30 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
7 23 ms 28 ms 28 ms 205.197.180.41
8 27 ms 26 ms 23 ms 207.88.13.52.ptr.us.xo.net [207.88.13.52]
9 25 ms 29 ms 23 ms cir1.atlanta6-ga.us.xo.net [207.88.13.49]
10 26 ms 29 ms 24 ms 67.111.23.95.ptr.us.xo.net [67.111.23.95]
11 95 ms 92 ms 93 ms ae-2.r03.atlnga05.us.bb.gin.ntt.net [129.250.4.221]
12 28 ms 25 ms 27 ms ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
13 45 ms 46 ms 48 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
14 85 ms 88 ms 86 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
15 90 ms 92 ms 89 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
16 87 ms 95 ms 88 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
17 86 ms 88 ms 104 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 92 ms * * 204.2.229.234
19 101 ms 89 ms 103 ms 204.2.229.9

Trace complete.

Application pre and post:
Most inconsistencies, latencies and issues I was able to bypass using Pingzapper. However, post migration, I've found the rerouting service to do little to nothing to improve the gameplay's experience. I found I'm no longer able to double weave oGCDs on BRD and sometimes have to clip DoTs as high as 4 seconds to ensure I do not suffer a complete drop and even larger DPS loss. It is incredibly frustating to find yourself unable to play a class to a degree you were previously able to do.

[Rosettias]

An official response to this issue would be fantastic. Especially since as of late it seems the instabilities have only been getting worse.

[Akross]

An official response to this issue would be fantastic. Especially since as of late it seems the instabilities have only been getting worse.

Yes please!

[Takamorisan]

Where is the official statement on this SE?

[Kyouki]

Only 2 weeks until the early access... 10 days until our credit cards will be charged? I want an answer before that happens SE! I don't wanna pay for an expansion that i wont be able to enjoy!

[dlgc]

Only 2 weeks until the early access... 10 days until our credit cards will be charged? I want an answer before that happens SE! I don't wanna pay for an expansion that i wont be able to enjoy!

I share the same sentiment.

Cheers,
D.

[ArtesiaWrynne]

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.

[Zhemos]

is SE even aware of the constant packet loss coming from 204.2.229.234 for east coast people?

[Hestzhyen]

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.

[Mature]

And update on how things are getting on would be ideal by now. Specifically being 2 weeks already. Is like if my internet at home goes down or have some difficulties the internet provider will make sure I receive full attention. They wouldn't be going on quiet for weeks and weeks.