Reporting Issues Resulting from the North American Data Center Relocation

[Kallistra]

Type of Issue/Feedback: Ping has increased from roughly 32ish to a consistent 105ms average
Name of your Internet Service Provider (ISP): Optimum
State/Country: New York (City)
Date/Time: After the server move
World Name: Gilgamesh
Frequency: 24/7
Traceroute records: Here you go

I am concerned about this move. When SE announced the servers were moving out of Montreal, I was okay with it. Even when they said a "Slight ping increase," I didn't mind, for I thought it would be only by about 10-20, maybe 30ms at most. If an increase like that means West Coast players get a decrease in ping, I'd be fine with it. Instead, East Coast players got over double their ping, while West Coast players got the old East Coast ping. This ultimately doesn't solve any problems. My own issue is that Double Weaving on jobs such as Bard, Machinist, Dragoon, and Ninja is impossible. Warrior is hit or miss. Dark Knight, my main Alexander Savage job, is a pain to play now (rest in peace, Low Blows + Dark Passenger.)

Despite this, I don't think ANOTHER server move is the solution. I don't think another server move is necessary. Two proposed options - rework the battle system to make Double Weaving feel fluid and natural regardless of ping, or add in an East Coast data center, bring the NA Data center count up to 3. Or send Primal/Aether to the East Coast.

I hope Square Enix makes the right decision here. I love FFXIV. I really do. But it just got a lot harder to play my favorite jobs.

[DesiFire]

'ello

- Type of Issue/Feedback: Severe rubber-banding, long freezes/lag, enemy models not loading (EX: Levi's head wouldn't load, but tail would), ping spikes, & packet loss. Everything will freeze for anywhere from 5-60 seconds then suddenly people rubber band and all actions happen at once.
- Name of your Internet Service Provider (ISP): Comcast
- State/Country: Indiana, USA
- Date/Time: Every day since migration. Most noticable after 10:00PM EST and into the later hours.
- World Name: Gilgamesh
- Frequency: Each day at night/early morning.
- Traceroute records:

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 8 ms 11 ms 10 ms
3 11 ms 119 ms 13 ms Te0-1-0-1-sur02.mishawaka.in.sbend.comcast.net [162.151.90.33]
4 10 ms 19 ms 11 ms te-0-7-0-6-sur01.mishawaka.in.sbend.comcast.net [162.151.36.45]
5 13 ms 14 ms 16 ms 68.85.176.157
6 13 ms 15 ms 15 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 13 ms 16 ms 17 ms hu-0-11-0-5-pe03.350ecermak.il.ibone.comcast.net [68.86.86.22]
8 15 ms 19 ms 15 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 70 ms 70 ms 69 ms ae-4.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
10 16 ms 14 ms 14 ms ae-1.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.7]
11 66 ms 65 ms 70 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 78 ms 69 ms 69 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 152 ms 69 ms 70 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
14 71 ms 70 ms 70 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 70 ms * 72 ms 204.2.229.234
16 68 ms 69 ms 69 ms 204.2.229.9

[DeMolay145]

Good evening.

Type of Issue/Feedback: Ping after migration is nearly 300ms. Dodging skills require some sort of prediction, which shouldn't happen. Also, some skills (like mudras, TFC, etc) are being hard to cast because they clip so hard I fail the cast them and end losing dps and missing the correct rotation.

Name of your Internet Service Provider (ISP): VIVO GVT.

State/Country: Colatina, Espírito Santo. Brazil.

Date/Time: Since migration of NA datacenters.

World Name: Behemoth

Frequency: Constant and so far no fluctuations.

Traceroute records:

2 8 ms 8 ms 7 ms gvt-rc01.grs.gvt.net.br [179.185.128.182]
3 8 ms 7 ms 15 ms 201.22.67.131.dynamic.adsl.gvt.net.br [201.22.67.131]
4 21 ms 20 ms 20 ms gvt-te-0-0-0-13.rt02.rjo.gvt.net.br [177.205.9.50]
5 49 ms 52 ms 52 ms 201.22.76.202.dynamic.dialup.gvt.net.br [201.22.76.202]
6 53 ms 53 ms 53 ms 216.184.112.210
7 128 ms 132 ms 132 ms 94.142.98.153
8 151 ms 151 ms 151 ms 176.52.255.1
9 233 ms 233 ms 233 ms 213.140.35.221
10 245 ms 243 ms 245 ms 5.53.6.182
11 247 ms 247 ms 247 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
12 236 ms 234 ms 233 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
13 233 ms 232 ms 233 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
14 290 ms 285 ms 285 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 294 ms 295 ms 294 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 289 ms 291 ms 288 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
17 290 ms 289 ms 289 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 * 289 ms 289 ms 204.2.229.234
19 289 ms 291 ms 288 ms 204.2.229.9

Also, as member "Barius" correctly observed, this is happening in all South America with ISPs related to the company named Telefónica in South America and Spain. Tracert hops pre and post migration leads to Spain, the difference now on the +120ms average is the jumps it now makes on Spain, France, Spain, Netherlands. All of em with ms increment. Pre migration it was only Spain and with no ms increment hops inside this country.

[Hamada]

I can't really give some details like some here but I like to have my voice in the manner:


"with WTFast I was able do a wildfire rotation without any clipping. Not only did I see it not clip but it was quite clear when I had 2 sec left on wildfire letting me to pull down gauss and put in an extra ws" With my normal speed I clipped an ocd and even though I did fit everything in the wildfire, it blew up after the last ws, meaning I could not put in a gauss off ws like I could with WTFast. 70 ping to 120 ping is very noticeable with this game and makes the statement 'no discernable difference in gameplay' a false one. To me that means the game needs to be coded better. I am not paying 9.99 on top of my sub and overpriced retainers over game shortcomings, please improve the coding"

http://forum.square-enix.com/ffxiv/t...=1#post4146412

It is a snip from that thread. Basically it is saying going from 78 ms to 120 ms reflects different results in rotation while yoshi-p said there should be no impact as long as it is 200 ms and under. The coding always had a slow response even at 35 ms, but now as you see people having increased pings notice it way more.
(editing some things out for privacy)

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 1 ms 1 ms ***
2 15 ms 16 ms 16 ms d*******.com [*****]
3 19 ms 18 ms 24 ms dynamic*******[******]
4 51 ms 27 ms 32 ms user*******logy.net [*********
5 19 ms 21 ms 22 ms **********y.net [*******]
6 32 ms 23 ms 26 ms static*******.net [*****]
7 20 ms 29 ms 28 ms dynam******.net [*****]
8 36 ms 44 ms 44 ms static********.net [*****]
9 50 ms 37 ms 40 ms dynamic-*******.net [******]
10 39 ms 37 ms 42 ms ae-53.r08.nycmny01.us.bb.gin.ntt.net [129.250.194.81]
11 39 ms 202 ms 52 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
12 98 ms 125 ms 89 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
13 96 ms 99 ms 88 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
14 110 ms 116 ms 125 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
15 115 ms 121 ms 124 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
16 115 ms 117 ms 130 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
17 197 ms 123 ms 126 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 115 ms 112 ms 111 ms 204.2.229.234
19 123 ms 109 ms 118 ms 204.2.229.9

[Soulshadow]

Type of Issue/Feedback: Disconnects & High Packet Loss
Name of your Internet Service Provider (ISP): Optimum Online
State/Country: NY / USA
Date/Time: All the time since the server move
World Name: Midgardsormr
Frequency: Constant
Traceroute records: https://pastebin.com/mpxxSf4g (Results using PingPlotter Pro)

[JoZeppeli]

Type of Issue/Feedback: Huge ping changes after NA Realocation, from 210 to 230+
Name of your Internet Service Provider (ISP): Vivo Telecom
State/Country: São Paulo/ Brazil
Date/Time: Since datacenters realocation.
World Name: Behemoth
Frequency: Full time

[Galfarion]

Type of Issue/Feedback: latency went way higher after server move, from 160 to 300
Name of your Internet Service Provider (ISP):GVT Vivo
State/Country: Minas gerais / Brasil
Date/Time: Since migration of NA datacenters (05/17)
World Name: Behemoth
Frequency: Entire time

[HarleySykes]

ISP - Fibertel
ticket number - TBD
country - Argentina
date - since server move
frequency - constant
content - all
world - exodus
tracert -

Tracing route to 204.2.229.109 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 12 ms 15 ms 14 ms 93-161-89-200.fibertel.com.ar [200.89.161.93]
7 17 ms 15 ms 15 ms 1-165-89-200.fibertel.com.ar [200.89.165.1]
8 9 ms 11 ms 11 ms 250-165-89-200.fibertel.com.ar [200.89.165.250]
9 9 ms 10 ms 13 ms ae6.baires5.bai.seabone.net [185.70.203.32]
10 37 ms 39 ms 38 ms ae7.sanpaolo8.spa.seabone.net [195.22.219.17]
11 37 ms 37 ms 37 ms ntt-verio.sanpaolo8.spa.seabone.net [149.3.181.65]
12 157 ms 151 ms 151 ms ae-4.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.227]
13 201 ms 196 ms 198 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 197 ms 198 ms 199 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 224 ms 225 ms 226 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 225 ms 225 ms 225 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
17 230 ms 229 ms 231 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 233 ms 233 ms 232 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 235 ms 235 ms 234 ms 204.2.229.234
20 237 ms 236 ms 237 ms 204.2.229.109

[Voltres]

Type of Issue/Feedback: latency went way higher after server move, from 120 to 220 while using VPN service for the best route. I'm paying extra to still get a bad connection. Subscription cancelled while this is not resolved.

Name of your Internet Service Provider (ISP): Vivo Fibra
State/Country: Sao Paulo / Brazil
Date/Time: Entire time
World Name: Behemoth
Frequency: Entire time

[Eryna]

Thanks Zhexos!

Type of Issue/Feedback: High latency, from 160 ms to 290 ms
Name of your Internet Service Provider (ISP): Vivo
State/Country: São Paulo, Brazil
Date/Time: Since relocation
World Name: Brynhildr
Frequency: All the time
Traceroute records (optional):

(Before maintenance)

Rastreando a rota para 199.91.189.93 com no máximo 30 saltos

1 <1 ms <1 ms <1 ms mymodem [192.168.1.1]
2 * * * Esgotado o tempo limite do pedido.
3 3 ms 3 ms 3 ms 187-100-40-77.dsl.telesp.net.br [187.100.40.77]
4 3 ms 2 ms 3 ms 200-100-2-197.dsl.telesp.net.br [200.100.2.197]
5 3 ms 5 ms 4 ms 187-100-44-141.dsl.telesp.net.br [187.100.44.141]
6 5 ms 5 ms 5 ms 84.16.10.162
7 121 ms 121 ms 121 ms 94.142.98.177
8 * * * Esgotado o tempo limite do pedido.
9 161 ms 161 ms 161 ms ae-2-12.bear1.Montreal2.Level3.net [4.69.203.129]
10 154 ms 154 ms 154 ms ormuco-comm.car2.montreal2.level3.net [4.59.178.74]
11 * * * Esgotado o tempo limite do pedido.
12 160 ms 159 ms 159 ms 192.34.76.2
13 155 ms 154 ms 154 ms 199.91.189.234
14 166 ms 154 ms 160 ms 199.91.189.93

(After maintenance)

Rastreando a rota para 204.2.229.106 com no máximo 30 saltos

1 <1 ms <1 ms <1 ms mymodem [192.168.1.1]
2 * * * Esgotado o tempo limite do pedido.
3 2 ms 2 ms 3 ms 187-100-189-80.dsl.telesp.net.br [187.100.189.80]
4 9 ms 2 ms 3 ms 187-100-80-26.dsl.telesp.net.br [187.100.80.26]
5 3 ms 3 ms 3 ms 187-100-39-33.dsl.telesp.net.br [187.100.39.33]
6 4 ms 4 ms 4 ms 5.53.1.30
7 118 ms 118 ms 118 ms 5.53.3.143
8 147 ms 147 ms 147 ms 5.53.4.26
9 224 ms 224 ms 224 ms 213.140.33.104
10 241 ms 241 ms 241 ms 213.140.35.1
11 231 ms 232 ms 232 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
12 233 ms 234 ms 232 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
13 236 ms 236 ms 236 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
14 287 ms 287 ms 287 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 292 ms 291 ms 291 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
16 291 ms 291 ms 291 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
17 291 ms 290 ms 290 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 291 ms * * 204.2.229.234
19 291 ms 291 ms 291 ms 204.2.229.106