Reporting Issues Resulting from the North American Data Center Relocation

Rather Severe Lag

Type of Issue/Feedback: Severe lag, resulting in lost Hearts and/or Enochian, rubberbanding and other general lag-related issues along with occasional disconnects. Traceroutes seem fine up until I hit ntt.net at which point they go to 110ms or more. My route seems to go to NYC > Seattle Washington > San Jose California > Sacramento

Name of your Internet Service Provider (ISP): WideOpenWest
State/Country:Ohio
Date/Time: Late June. Tends to occur more during evening and overnight hours.
World Name: Zalera
Frequency: Very often and for extended periods
Traceroute record:

Code:

Tracing route to 204.2.229.9 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms RT-AC3200-B9D0 [192.168.1.1] 2 8 ms 9 ms 9 ms d28-23-1-194.dim.wideopenwest.com [23.28.194.1] 3 13 ms 13 ms 15 ms dynamic-76-73-195-133.knology.net [76.73.195.133] 4 13 ms 12 ms * user-24-214-131-152.knology.net [24.214.131.152] 5 27 ms 28 ms 26 ms dynamic-75-76-35-85.knology.net [75.76.35.85] 6 27 ms 24 ms 25 ms dynamic-75-76-35-105.knology.net [75.76.35.105] 7 134 ms 135 ms 122 ms ae-53.r08.nycmny01.us.bb.gin.ntt.net [129.250.194.81] 8 129 ms 115 ms 109 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61] 9 175 ms 175 ms 184 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13] 10 181 ms 179 ms 169 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54] 11 201 ms 191 ms 181 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124] 12 199 ms * * ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] 13 * 194 ms 200 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33] 14 184 ms 189 ms 195 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 15 189 ms 192 ms * 204.2.229.234 16 219 ms 196 ms 205 ms 204.2.229.9

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, -.-

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?

Lag, Disconnection from server

Type of Issue/Feedback: Game freezes (lag) all the time, can't play anymore. It is almost impossible to finish a Dungeon, it keeps disconnecting from the server, lag it's to high.
Name of your Internet Service Provider (ISP): Fibertel.
State/Country: Buenos Aires, Argentina.
Date/Time: Last month (July, August)
World Name: Adamantoise.
Frequency: Almost all the time, it happens not only for me, my other 2 friends that play in the same server, same country, since the servers change it's unplayable. :mad:

anyone else having trouble connecting to Aether data center at the moment?

all I'm getting is stormblood video that keeps repeating and won't go to character login screen.

- 90002 for days, ping going from 25 to 3000+ over a course of millisecond before disconnecting
- Shaw
- BC, Canada
- about a week, worse each day
- Excalibur
- EVERYDAY

i guess SE just doesn't want me playing, while shaw steals everything in the meantime

Quote:

Originally Posted by Akross

Hello,

- Type of Issue/Feedback: Ping goes up from 160ms before migration, to 300ms after migration.
- Name of your Internet Service Provider (ISP): Telefónica del Sur
- State/Country: Chillán, Chile.
- World Name: Lamia
- Frequency: All the time
- Since migration of NA datacenters. Constant and so far no fluctuations.

Quote:

Traza a 204.2.229.9 sobre caminos de 30 saltos como máximo.

1 4 ms 3 ms 4 ms 192.168.0.1
2 57 ms 58 ms 61 ms 192.168.2.1
3 17 ms 14 ms 22 ms 10.30.64.1
4 19 ms 18 ms 9 ms reverso.190.211.0.operaciones.gtdinternet.com [190.211.0.1]
5 15 ms 16 ms 17 ms 192.168.4.53
6 31 ms 21 ms 24 ms 192.168.4.54
7 * * * Tiempo de espera agotado para esta solicitud.
8 25 ms 26 ms 26 ms 5.53.1.101
9 113 ms 111 ms 122 ms 5.53.3.165
10 165 ms 152 ms 144 ms 5.53.5.200
11 218 ms 219 ms 214 ms 94.142.117.239
12 284 ms 317 ms 297 ms 5.53.3.20
13 271 ms 273 ms 276 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
14 243 ms 235 ms 239 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
15 254 ms 237 ms 244 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
16 304 ms 300 ms 307 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
17 297 ms 298 ms 297 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
18 289 ms 291 ms 296 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
19 300 ms 297 ms 295 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
20 300 ms * 297 ms 204.2.229.234
21 291 ms 294 ms 296 ms 204.2.229.9

Observation: As you may see in other posts, this is a South America problem with ISPs of the Telefónica Company. Tracert goes to amsterdam before going to US server.

After that comment, ping improved from 300 to 200, but now again is hight

Quote:

Traza a 204.2.229.10 sobre caminos de 30 saltos como máximo.

1 1 ms 1 ms 1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 192.168.1.1
3 1 ms 1 ms 1 ms 192.168.2.1
4 9 ms 6 ms 6 ms 10.1.1.1
5 7 ms 12 ms 16 ms reverso.190.211.0.operaciones.gtdinternet.com [1
90.211.0.1]
6 12 ms 13 ms 10 ms 192.168.4.53
7 12 ms 10 ms 12 ms 192.168.4.54
8 * * * Tiempo de espera agotado para esta solicitud.
9 172 ms 164 ms 162 ms mia2.be1.100.scl2.gtdinternet.com.63.196.190.in-
addr.arpa [190.196.63.134]
10 * 163 ms 163 ms 7-2-9.ear4.miami2.level3.net [4.15.159.161]
11 * * * Tiempo de espera agotado para esta solicitud.
12 170 ms 170 ms 171 ms ntt-level3-80g.miami.level3.net [4.68.127.54]
13 223 ms 224 ms 225 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.4
0]
14 178 ms 168 ms 164 ms ae-4.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.1
84]
15 195 ms 201 ms 199 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.8
6]
16 248 ms 250 ms 247 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.
237]
17 264 ms 266 ms 259 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.
27]
18 262 ms 262 ms 260 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
1]
19 263 ms 263 ms 266 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
20 283 ms 256 ms 257 ms 204.2.229.234
21 260 ms 259 ms 259 ms 204.2.229.10

Come on SE it's been over 3 Months. can we please have an update

As of this moment it seems SOMEONE is trying to fix the routing problem. At least the routing isn't going to amsterdam, so we lost 100 or so milliseconds. A few days ago the latency here was like 340ms, now it's 217. It's going somewhere.

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 2 ms <1 ms <1 ms 192.168.0.1
2 <1 ms 1 ms <1 ms 172.16.199.10
3 <1 ms 1 ms <1 ms 172.16.199.9
4 1 ms 1 ms <1 ms 172.16.200.1
5 3 ms * 1 ms 128-193-186-82.andradas-net.com.br [186.193.128.82]
6 5 ms * 4 ms 187-50-36-1.customer.tdatabrasil.net.br [187.50.36.1]
7 7 ms 7 ms * 187-100-83-12.dsl.telesp.net.br [187.100.83.12]
8 19 ms 17 ms 17 ms 5.53.1.30
9 125 ms 123 ms 121 ms 5.53.3.143
10 154 ms 155 ms 152 ms 94.142.126.161
11 159 ms 158 ms 159 ms ae-11.r07.nycmny01.us.bb.gin.ntt.net [129.250.9.1]
12 151 ms 150 ms 150 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
13 217 ms 219 ms 215 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 217 ms 214 ms 217 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 213 ms 213 ms 211 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 219 ms 218 ms 218 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
17 219 ms 217 ms 217 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 219 ms 217 ms 217 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 219 ms 218 ms * 204.2.229.234
20 217 ms 216 ms 217 ms 204.2.229.9