Reporting Issues Resulting from the North American Data Center Relocation

[maTyaR]

Gilgamesh
Bell Canada
Ontario

Tracing route to 204.2.229.87 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 4 ms 4 ms 10.11.2.41
3 4 ms 4 ms 4 ms 10.178.206.62
4 5 ms 5 ms 5 ms 10.178.206.63
5 20 ms 23 ms 23 ms tcore3-toronto47_2-8-0-0.net.bell.ca [64.230.107
.32]
6 20 ms 19 ms 19 ms tcore3-chicagocp_hundredgige0-3-0-0.net.bell.ca
[64.230.79.167]
7 19 ms 19 ms 19 ms bx6-chicagodt_0-6-0-0.net.bell.ca [64.230.79.85]

8 19 ms 19 ms 20 ms verio-peering.net.bell.ca [64.230.186.218]
9 79 ms 79 ms 79 ms ae-9.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.2
17]
10 19 ms 20 ms 19 ms ae-1.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.7
]
11 77 ms 79 ms 94 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.1
7]
12 78 ms 78 ms 78 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.
27]
13 80 ms 79 ms 79 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
1]
14 81 ms 81 ms 81 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
15 80 ms 80 ms 79 ms 204.2.229.234
16 79 ms 79 ms 79 ms 204.2.229.87

Trace complete.

For a player who was next to the Montreal server, I can tell the differences between the previous and this new terrible location. RTT Hiccups from time to time in raid where applying GCD/oGCDs DO NOT EXECUTE PROPERLY (delays).

This is for the FFXIV employees to read:

The relocation is the most stupid decision ever. Players have already gotten use to the gameplay from the get-go with that specific latency (RTT), and moving the datacenter to the opposite side of the country will only show more disappointment from the players as they are no longer accustomed to their original responsiveness/feel to the game they play.

It was most likely a decision made by the upper-brackets of SE, but they DO NOT know how to maintain a happy, player-based community.

You've ruined my original gameplay and forced upon to adjusting to your ill-advised decisions (I wouldn't be complaining if the servers were in a Central location AS IT WOULD HAVE SATURATED NA LATENCY PROPERLY).

Watch fellas, it will take about 1-2 years to see an an official change or maybe even a statement, -.-

[Jozu]

Ok... I don't know if it fixed itself or what but my latency is now between 130ms-135ms (was 220ms+)

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms [192.168.1.1]
2 4 ms 3 ms 4 ms 192.168.0.1
3 * * * Request timed out.
4 19 ms 17 ms 16 ms 10.2.1.49
5 14 ms 22 ms 17 ms 10.65.17.5
6 15 ms 30 ms 19 ms 24.139.179.85
7 97 ms 81 ms 81 ms 63.245.70.140
8 81 ms 85 ms 78 ms 213.46.182.13
9 * * * Request timed out.
10 82 ms 83 ms 84 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
11 127 ms 126 ms 129 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 130 ms 128 ms 124 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 132 ms 131 ms 130 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
14 135 ms 131 ms 135 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 137 ms 128 ms 133 ms 204.2.229.234
16 130 ms 133 ms 134 ms 204.2.229.10

Trace complete.

Just to confirm it isn't just me,can anyone from South,Central America or Puerto Rico post their tracert results?