New server location made unplayable for south american players

[BernAlmasy]

Some official response would be nice.

Yes, would like to know if theyre doing something about the routes or just fuck it. so i could make a decision myself

[Azell]

I was all over this forum yesterday trying to make SA voices heard, but after i calmed down i realized that there is nothing to be done but talk to your isp. The fact that the servers are there is set in stone, they are not going to move. If your isp is routing you through some weird place its not SE fault. Call your isp and talk about this issue, the more complains the better. I'm in the same boat, but using vpn makes a little better, from 210 to 150(used to be 100-90), i am trully sad because i always raided on high performance groups, now i'll have to adapt a lot and hope my group doesnt feel the difference lol

[Ehrgein]

As someone who battled left and right when the level3 issue was at hand (to put it in perspective, I had 2 minute spikes and around 500 ping when I didn't had those spikes), of course the issue was only with FF XIV so I changed my isp. Now this same thing again, so frustrating. Believe me, your ISP won't do shit even if it's 10, 20, 40 or 50 cases because it's not their problem. Once it leaves your country it's pretty much hands clean for them, believe me I've tried. This is on SE and no one else, they are the only ones who can do anything about it.

That being said, will most likely unsub if they don't give us a solution prior to stormblood, which will most likely not happen.
Left WoW for this, sigh.

[Bariaus]

Another affected:

- Chile (centric Santiago)
- ISP Movistar / Telefónica
- Brynhildr NA

Values before migration versus values post migration

To sum this whole problem :

The only ones benefited for this were the people living on and near West Coast, and Australians by a few ms less. The rest of the US and Canada are slightly affected with 50ms avg more. EU and Central/South America are heavily affected, with Europe edging the 200ms limit. South America have a couple ISPs that are routing through Europe, and these ones are generating a leap from 150-180 to 300ms. Before the migration - and as you can see in my tracerts - there weren't any jumps on Europe, at least for my ISP (and it seems the others affected too). You can't play this game with 300ms.

If you're more interested to see where are those strange hops that pumps the ms up, you can google IP geolocation and put those IPs there.


Mods, anything to say about this issue? Thanks. And no, I don't wanna leave a game that I like and that I dedicated almost 4 years.

[filexcl]

Another affected:

- Chile (centric Santiago)
- ISP Movistar / Telefónica
- Brynhildr NA

Values before migration versus values post migration

To sum this whole problem :

The only ones benefited for this were the people living on and near West Coast, and Australians by a few ms less. The rest of the US and Canada are slightly affected with 50ms avg more. EU and Central/South America are heavily affected, with Europe edging the 200ms limit. South America have a couple ISPs that are routing through Europe, and these ones are generating a leap from 150-180 to 300ms. Before the migration - and as you can see in my tracerts - there weren't any jumps on Europe, at least for my ISP (and it seems the others affected too). You can't play this game with 300ms.

If you're more interested to see where are those strange hops that pumps the ms up, you can google IP geolocation and put those IPs there.


Mods, anything to say about this issue? Thanks. And no, I don't wanna leave a game that I like and that I dedicated almost 4 years.

Chile and movistar / telefonica is bad badd.

[Shurrikhan]

Hasn't the server moved as far south as it would have moved west away from you? I suspect the route has more to do with the difference... I don't know what the deal is, but it seems that almost every ISP takes horrible routes to XIV servers, now no less than before.

[Lorielthy]

Country: Brasil - Rio de Janeiro
ISP: Vivo (GVT) / Telefonica
Latency: 180 Before changing Server Location / 290 ~ 320 Now
Server: Behemoth - Primal

I have contacted my ISP but they just took note of the problem and I don't have any idea if this is a good signal. Probably not. For random reasons, I'm pinging to Amsterdan before reaching Sacramento.

Rastreando a rota para 204.2.229.24 com no máximo 30 saltos
2 7 ms 7 ms 7 ms gvt-b-se03.rjo.gvt.net.br [179.184.126.63]
3 8 ms 9 ms 8 ms 177.205.8.23.static.adsl.gvt.net.br [177.205.8.23]
4 9 ms 10 ms 7 ms gvt-te-0-0-0-11.rt02.rjo.gvt.net.br [177.205.9.46]
5 47 ms 49 ms 44 ms 201.22.76.202.dynamic.dialup.gvt.net.br [201.22.76.202]
6 44 ms 45 ms 45 ms grafortw2-1-3-0.net.telefonicaglobalsolutions.com [216.184.112.208]
7 113 ms 128 ms 113 ms 94.142.127.50
8 152 ms 153 ms 153 ms 94.142.126.205
9 229 ms * 229 ms 5.53.6.150
10 235 ms 235 ms 235 ms 213.140.35.119
11 233 ms 234 ms 233 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
12 234 ms 234 ms 234 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
13 237 ms 237 ms 238 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
14 284 ms 285 ms 285 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 289 ms 289 ms 289 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 284 ms 284 ms 284 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
17 284 ms 284 ms 285 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 290 ms 290 ms * 204.2.229.234
19 283 ms 284 ms 284 ms 204.2.229.24
Rastreamento concluído.

[BernAlmasy]

Hasn't the server moved as far south as it would have moved west away from you? I suspect the route has more to do with the difference... I don't know what the deal is, but it seems that almost every ISP takes horrible routes to XIV servers, now no less than before.

looks like a lot of ppl from south america is getting their route towards europe, and then to california. wich doesnt make much sense. its being weird. i contacted my ISP, but they blaming SE, and SE will blame the ISP probably. im just hoping i dont need to quit the game

[HarleySykes]

the tracert is

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 17 ms 14 ms 16 ms 93-161-89-200.fibertel.com.ar [200.89.161.93]
7 16 ms 14 ms 15 ms 1-165-89-200.fibertel.com.ar [200.89.165.1]
8 11 ms 11 ms 11 ms 250-165-89-200.fibertel.com.ar [200.89.165.250]
9 10 ms 9 ms 9 ms ae6.baires5.bai.seabone.net [185.70.203.32]
10 37 ms 37 ms 37 ms ae7.sanpaolo8.spa.seabone.net [195.22.219.17]
11 37 ms 37 ms 38 ms ntt-verio.sanpaolo8.spa.seabone.net [149.3.181.65]
12 152 ms 159 ms 151 ms ae-4.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.227]
13 206 ms 195 ms 196 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 197 ms 197 ms 197 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 224 ms 224 ms 224 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 224 ms 226 ms 225 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
17 230 ms 231 ms 231 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 233 ms 234 ms 234 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 234 ms 235 ms 234 ms 204.2.229.234
20 237 ms 237 ms 236 ms 204.2.229.109

the problem is in Sao Paulo, we're being redirected to New York, then to Seattle AND THEN to cali, someone needs to fix this garbage routing ASAP

[Judge_Xero]

http://www.us.ntt.net/about/network-map.cfm

Here is the NTT Routing Map. There does seem to be a lot of unnecessary hops for a lot of people. Hopefully that gets addressed. As you can see, even though the servers are in Sacramento the available routing options for NTT is pretty optimal for the majority of players.

Other than optimizing routing within the NTT network I don't see it getting significantly better for people in awkward places of the world (South America, North Eastern Canada) without having a second NA Data Center in New York. This is simply due to the size of North America compared to the JP and EU Data center locations.

the problem is in Sao Paulo, we're being redirected to New York, then to Seattle AND THEN to cali, someone needs to fix this garbage routing ASAP

TBH that is probably the most ideal routing by looking at the map. The only way it could get better is if Sao Paulo connected directly to Washington.
It could connect and be routed through Miami but it would also create more hops and potential for packet loss. With only a difference of maybe 20ms ping.