Type of Issue/Feedback: Lag after server relocation (158ms before, 270ms after)
Name of your Internet Service Provider (ISP): NET Virtua
State/Country: Pará, Brazil
Date/Time: After the server relocation.
World Name: Behemoth
Frequency: Always.
https://pastebin.com/QJdet6RT
Hello!
Type of Issue/Feedback: Ping has gone up from about 35ish before the server move to 80+ after the server move as well as constant packet loss almost to the point of making the game un-playable. I have also been suffering from multiple disconnects since the server move.
Name of your Internet Service Provider (ISP): Shaw.
State/Country: British Columbia/Canada.
Date/Time: Since the Server move.
World Name: Sargatanas.
Frequency: Constant since the transfer.
Type of Issue/Feedback: Increased Ping + Spikes and an odd tracert routing table.
Before the server move during primetime I would be around 50 - 60 ping.
After server move I'm between 100ms - 180 (without VPN)
In order to avoid the spikes, and play the game as close to normal, I have to pay for a VPN. At times I will 90k and get disconnected as well.
Name of your Internet Service Provider (ISP): Spectrum
State/Country: Florida, USA
Date/Time: After the server move.
World Name: Gilgamesh
Frequency: Constant. The disconnects happen every couple of hours or so.
Traceroute records: To Gilgamesh
To lobby server
Hi!!
Type of Issue/Feedback: Latency increase,going from 130-160 to 200-230
Name of your Internet Service Provider (ISP): Copel Telecom
State/Country: Paraná / Brazil
Date/Time: After the migration of NA datacenters
World Name: Behemoth
Frequency: most of time
Traceroute records
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.
'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
Type of Issue/Feedback: Latency where abilities are used but not recognized by the server.
Name of your Internet Service Provider (ISP):Comcast
State/Country: Florida / United States
Date/Time: Since Server Migration to California
World Name: Leviathan
Frequency: (How often does the issue occur?) All the time but worse from 7pm to 1am Est
Traceroute records
Tracing route to 204.2.229.106 over a maximum of 30 hops
1 1 ms 2 ms 3 ms My Router
2 9 ms 8 ms 12 ms XX.XXX.XX.XX
3 9 ms 10 ms 8 ms xe-7-1-5-sur01.ftcaroline.fl.jacksvil.comcast.net [68.86.169.97]
4 9 ms 10 ms 12 ms 68.87.165.209
5 20 ms 20 ms 27 ms be-33489-cr02.miami.fl.ibone.comcast.net [68.86.95.45]
6 17 ms 16 ms 16 ms hu-0-10-0-7-pe01.nota.fl.ibone.comcast.net [68.86.82.2]
7 16 ms 19 ms 16 ms 50.242.151.66
8 60 ms 88 ms 80 ms ae-7.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
9 75 ms 24 ms 39 ms ae-3.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.110]
10 54 ms 69 ms 56 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
11 124 ms 99 ms 97 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
12 101 ms 159 ms 100 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 151 ms 107 ms 102 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
14 100 ms 100 ms 222 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 229 ms 100 ms * 204.2.229.234
16 101 ms 101 ms 102 ms 204.2.229.106 <-Leviathan Server
Greetings!
- Type of Issue/Feedback:
Ping goes up from 180ms before migration, to 300ms (or a little more) after migration.
- Name of your Internet Service Provider:
Movistar (Telefónica).
- State/Country:
Santiago, Chile.
- World:
Hyperion.
- Date/Frequency:
Since migration of NA datacenters, entire time.
- Traceroute records:
Tracert Here
The clearest examples are in things like opening retainers, changing jobs, interacting with NPC, Swiftcast, Mudras, dodging AoEs, are annoying now.
Thank you. :)
Type of Issue/Feedback: Ever since the server switched datacenters my ping has been retarded, at the point it makes my game unplayable. Before it moved i had stable 105ms ping on montreal, now its above 258ms with lag spikes that go over 350ms. With a tunneling service its playable, at 1am EST i get about 120-130ms ping but it starts to lag to lag real bad around 5pm EST.
Name of your Internet Service Provider (ISP):ClaroPR
State/Country:Puerto Rico
Date/Time: It started when the servers switched datacenters.
World Name:Leviathan
Frequency: The lag seems to be less after like 1am EST and it starts to get real bad around 5pm EST.
Trace-route : After, without a vpn (what i get from my ISP)
trace to a pingzapper server on california
Even with a vpn enabled (pinzapper and mudfish) i still get massive lag spikes to the server. The game is completely unplayable without any tunneling service. I cant even dodge aoes or dps when it starts to lag. Theres no reason for my packets to be redirected to Europe before going towards the game server. Its only to the game servers, other servers from California that i tried doesn't have this issue. I really wish you guys moved the servers to a more centralized location to make everyone happy instead of the west coast.
Type of Issue/Feedback: latency went way higher after server move, from 160 to 230
Name of your Internet Service Provider (ISP): Live Tim
State/Country: Sao Paulo / Brasil
Date/Time: Entire time
World Name: Behemoth
Frequency: Entire time
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.
Hey!
Type of Issue/Feedback: latency went way higher after server move, from 140 to 230
Name of your Internet Service Provider (ISP): Live TIM
State/Country: Sao Paulo / Brazil
Date/Time: Entire time
World Name: Behemoth
Frequency: Entire time
Type of Issue/Feedback: 80ms prior to move, 120ms post move, no longer able to double weave between gcd cds on drg, and fuma clips gcd consistently, as well as unavoidable packet loss that is only minimized by vpn tunneling.
Comcast
Florida, United States of America
Since the movement of the server, Consistently at all times of the day.
Gilgamesh
24/7
The packet loss is pretty w/e since i can just use a vpn to alleviate it for the most part, but the fact i can't double weave on drg at all, and ninja has become so unenjoyable to play is just really the issue. Every fuma clips the gcd, raiton clips the gcd by what feels like almost an entire second, and even attempting to suiton, i have to reactievely wait for my mudras to update on my screen rather than just inputting the commands. So it feels as though it takes entire gcd just to cast suiton. And if i don't do it that way, Raiton will just come out instead.The only job that hasn't been affected is monk and I just lost majority of my will to even play anymore, going as far as considering unsubbing, which of course i'd rather not, but if i dont enjoy the game, im not gonna pay for the sub anymore.
I can't really give some details like some here but I like to have my voice in the manner:
https://i.gyazo.com/ce0ca834677d3ff5...3229cfb8ba.png
"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
Type of Issue/Feedback: Ping increased from 32ms to 103ms. This causes issues with playing the some jobs. As a PS4 player, I have no way of making my ping any better.
Name of your Internet Service Provider (ISP):Comcast
State/Country: MA, USA
Date/Time: After server migration to California.
World Name: Ultros
Frequency: Constant. Ping sometimes increases even more.
Traceroute records:
Tracing route to 204.2.229.9 over a maximum of 30 hops
1 20 ms 30 ms 3 ms 10.0.0.1
2 15 ms 11 ms 13 ms 96.120.70.81
3 94 ms 257 ms 16 ms ge-1-44-ur02.bristol.ct.hartford.comcast.net [68.87.180.189]
4 15 ms 16 ms 35 ms be-39-ar01.needham.ma.boston.comcast.net [69.139.221.1]
5 28 ms 21 ms 19 ms be-7015-cr02.newyork.ny.ibone.comcast.net [68.86.90.217]
6 22 ms 23 ms 18 ms hu-0-14-0-1-pe02.111eighthave.ny.ibone.comcast.net [68.86.85.42]
7 37 ms 34 ms 38 ms 50.242.151.70
8 35 ms 35 ms 35 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
9 87 ms 86 ms 169 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
10 87 ms 87 ms 92 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
11 106 ms 98 ms 102 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
12 102 ms 106 ms 104 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
13 106 ms 105 ms 108 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
14 103 ms 101 ms 105 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 102 ms 104 ms 101 ms 204.2.229.234
16 104 ms 102 ms 102 ms 204.2.229.9
Trace complete.
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)
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
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
Type of Issue/Feedback: Increase in ping times (went from 40-50ms to 150-300ms) and sudden spike in packet loss. Constantly getting disconnected as well making dungeons very difficult to even attempt.
Name of your Internet Service Provider (ISP): Cogeco
State/Country: Ontario/Canada
Date/Time: May 17th, 2017 (since the moment the server was moved)
World Name: Gilgamesh
Frequency: All the time
Trace-route :
Trace-route to Gilgamesh
Trace-route to the main servers
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
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
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):
Quote:
(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
Quote:
(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
-Went from aroun 100ms to 240 ms, permanent delays on every interaction, global cooldowns animations and procs, not able to double weave without cliping the CDs on my drg anymore, crafting with macros have is not viable now. Playing on PS4.
-(ISP):Movistar (teléfonica)
-Bogota, Colombia
-wednesday may the 17th, 7pm Est
-World Name: Behemoth
-Frequency: permanent
-Traceroute records : https://pastebin.com/46PZdcp9
Type of Issue/Feedback: Abilities and weaponskills feel amazingly unresponsive. Feels like weaponskills hit half a second or more after when they normally would. Double weaving and potions clip into the GCD. I have had instances where Fuma Shuriken clips into the GCD and sometimes just doesn't activate because it feels like my attacks are behind in a queue. Ping times went from about 15ms to 80-110ms. Also occasionally experience packet loss. Any attempt to use a VPN has either given me zero improvement or has flat out caused me to D/C in dungeons.
Name of your Internet Service Provider (ISP): Verizon Fios
State/Country: NY, USA
Date/Time: Happens all the time, any time of the day and started immediately from when the servers came back online.
World Name: Balmung
Hello.
Type of Issue/Feedback: I've been having latecy issues as weel, making it harder to correctly do rotations and sometimes mechanics. Ping went from 210 to 320, with VPN it went from 185 to 230.
Name of your Internet Service Provider (ISP):GVT Vivo
State/Country: Mato Grosso do Sul / Brazil
Date/Time: Since the migration of NA Datacenters (05/17)
World Name: Diabolos
Frequency: Entire time
Tracing route to 204.2.229.96 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms PowerBox.home [192.168.25.1]
2 5 ms 4 ms 4 ms gvt-b-se01.cpe.gvt.net.br [189.59.241.131]
3 5 ms 5 ms 4 ms gvt-b-se07.cpe.gvt.net.br [179.184.83.41]
4 41 ms 31 ms 30 ms 201.22.64.99.dynamic.dialup.gvt.net.br [201.22.64.99]
5 26 ms 26 ms 26 ms 176.52.252.180
6 133 ms 134 ms 132 ms 5.53.3.143
7 177 ms 168 ms 168 ms 213.140.35.14
8 244 ms 246 ms 238 ms 213.140.35.203
9 246 ms 246 ms 252 ms 5.53.3.18
10 246 ms 246 ms 246 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
11 253 ms 255 ms 263 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
12 257 ms 256 ms 258 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
13 309 ms 313 ms 309 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
14 314 ms 314 ms 313 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
15 313 ms 313 ms 313 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
16 314 ms 314 ms 313 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
17 313 ms 314 ms * 204.2.229.234
18 313 ms 313 ms 313 ms 204.2.229.96
Type of Issue/Feedback: Ping goes up from 130 to 230 ~ 240
Name of your Internet Service Provider (ISP): NET Virtua
State/Country: São Paulo / Brazil
Date/Time: Since datacenters realocation.
World Name: Behemoth
Frequency: Full time
- https://pastebin.com/SkDAG59V
- Ping went from 140~160 to 300+ after datacenter migration;
- Vivo
- Rio Grande do Sul/Brazil
- Since datacenter migration
- Behemoth
- Entire time
- tracert
Type of Issue/Feedback: High latency, from 210ms to 350ms
Name of your Internet Service Provider (ISP): Vivo
State/Country: São Paulo,Brazil
Date/Time: Since 05/17, right after the Data Center Relocation
World Name: Behemoth
Frequency: All the time
Traceroute records (optional):
Quote:
Rastreando a rota para 204.2.229.9 com no máximo 30 saltos
1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 * * * Esgotado o tempo limite do pedido.
3 44 ms 44 ms 46 ms 187-100-40-121.dsl.telesp.net.br [187.100.40.121]
4 44 ms 44 ms 66 ms 187-100-193-238.dsl.telesp.net.br [187.100.193.238]
5 47 ms 48 ms 51 ms 187-100-83-4.dsl.telesp.net.br [187.100.83.4]
6 49 ms 49 ms 52 ms 84.16.10.221
7 168 ms 172 ms 167 ms 94.142.98.159
8 197 ms 199 ms 201 ms 176.52.249.142
9 283 ms 283 ms 284 ms 213.140.35.205
10 284 ms 284 ms 283 ms 5.53.3.18
11 303 ms 300 ms 298 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
12 293 ms 293 ms 293 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
13 290 ms 287 ms 287 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
14 338 ms 336 ms 339 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 339 ms 340 ms 339 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
16 338 ms 338 ms 341 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
17 340 ms 344 ms 339 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 341 ms 337 ms 338 ms 204.2.229.234
19 343 ms 340 ms 340 ms 204.2.229.9
Rastreamento concluído.
- Ping goes up from 147-153ms before migration, to 201-205ms after migration.
- ISP: NET Virtua
- Rio de Janeiro / Brazil (South America)
- Since the NA servers migrated.
- Faerie (Aether)
- Frequency: Entire Time
- Tracert
Type of Issue/Feedback:
My ping before was 140-150 ms, now is 230 ms
Name of your Internet Service Provider (ISP):
Net Virtua
State/Country:
Brasília - Brazil
Date/Time:
After NA servers relocation
World Name:
Gilgamesh
Frequency:
Since the relocation
-----Trace Route-----------------------------------
1 1 ms <1 ms 1 ms 192.168.0.1
2 19 ms 8 ms 13 ms 10.30.0.1
3 22 ms 13 ms 19 ms bd060095.virtua.com.br [189.6.0.149]
4 11 ms 15 ms 12 ms embratel-T0-4-0-5-uacc03.bsa.embratel.net.br [200.213.139.9]
5 11 ms 10 ms 10 ms ebt-H0-11-0-0-tcore02.bsa.embratel.net.br [200.244.213.231]
6 140 ms 137 ms 139 ms ebt-BP16122-intl02.nyk.embratel.net.br [200.230.220.190]
7 136 ms 136 ms 136 ms ce-0-10-0-2.r08.nycmny01.us.bb.gin.ntt.net [129.250.202.185]
8 140 ms 140 ms 141 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
9 204 ms 210 ms 213 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
10 218 ms 217 ms * ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
11 224 ms 227 ms 223 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
12 237 ms 245 ms 237 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 231 ms 229 ms 242 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
14 225 ms 225 ms 225 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 237 ms * 237 ms 204.2.229.234
16 229 ms 231 ms 228 ms 204.2.229.10
Type of Issue/Feedback: Ping went from 160ms to 315ms
Name of your Internet Service Provider (ISP): Vivo
State/Country: Distrito Federal / Brazil
Date/Time: 05/17 / Entire Time
World Name: Behemoth
Frequency: Entire time
Traceroute records:
Rastreando a rota para 204.2.229.10 com no máximo 30 saltos
1 <1 ms <1 ms <1 ms PowerBox [192.168.25.1]
2 6 ms 6 ms 9 ms gvt-b-sr05.bsa.gvt.net.br [179.184.126.71]
3 6 ms 23 ms 5 ms 177.205.8.229.static.adsl.gvt.net.br [177.205.8.229]
4 29 ms 29 ms 29 ms 5.53.1.160
5 136 ms 142 ms 142 ms 94.142.98.159
6 176 ms 175 ms 178 ms xe6-0-6-0-grtnycpt3.net.telefonicaglobalsolutions.com [213.140.49.68]
7 247 ms 246 ms 246 ms 213.140.35.217
8 266 ms 265 ms 266 ms 5.53.3.20
9 256 ms 255 ms 256 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
10 251 ms 251 ms 251 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
11 254 ms 254 ms 254 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
12 308 ms 308 ms 316 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
13 313 ms 312 ms 312 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
14 313 ms 314 ms 314 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
15 319 ms 319 ms 320 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 315 ms * * 204.2.229.234
17 317 ms 313 ms 315 ms 204.2.229.10
Type of Issue/Feedback: Inconsistent connection, ranging from 180ms to 240ms, essentially all EU players who have invested time, money and friendships on the american servers since as early as 2013 are now suffering either barely playable or completely unplayable differences in their connections. A centralized server is essential and the only considerate thing to do for your European, South American, North, East and West Americans. This would provide the the essential service that we pay for for monthly. It's recommended to forward to the Japanese development team the case of RIOT's League of Legends server move FROM California to central America for the exact same reasons.
Name of your Internet Service Provider (ISP): British Telecommunications
State/Country: Co.Antrim, Northern Ireland, United Kingdom
Date/Time: After 17th May - NA Datacenter Reposition to Sacramento, CA, USA.
World Name: Aether Datacenter - Gilgamesh
Frequency: Consistent - https://puu.sh/vVvrB/a9ff832aae.png
Type of Issue/Feedback: Ping went from 150ms to 201ms
Name of your Internet Service Provider (ISP): Net Virtua
State/Country: Rio de Janeiro / Brazil
Date/Time: 05/17 / Entire Time
World Name: Balmung
Frequency: Entire time
Traceroute records
Type of Issue/Feedback: It's to be expected, but my ping shot up from 145-150 to 240-260, some days up to 300. I also get lag spikes here and there, and I notice that oddly enough, battle content instances (Dungeons/Trials etc.) seems to have a more prominent delay on actions and inputs. The weird thing is, if I use a routing service, my ping actually goes down to 190-200. I'm not a super tech savvy person, but it seems like the biggest issue since the move is routing, more so than distance alone.
Name of your Internet Service Provider (ISP): Saudi Telecom Company (STC)
State/Country: Riyadh, Saudi Arabia.
Date/Time: Since the relocation of the data centers.
World Name: Jenova.
Frequency: Constant.
Tracert Records
Quote:
Tracing route to 204.2.229.81 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.100.1
2 52 ms 3 ms 3 ms 37.104.128.1
3 4 ms 3 ms 4 ms 84-235-86-42.saudi.net.sa [84.235.86.42]
4 4 ms 3 ms 5 ms 84-235-94-137.saudi.net.sa [84.235.94.137]
5 19 ms 19 ms 19 ms 84-235-123-224.saudi.net.sa [84.235.123.224]
6 69 ms 68 ms 68 ms hu0-3-0-0.ccr21.mrs01.atlas.cogentco.com [149.14.124.97]
7 79 ms 79 ms 79 ms be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
8 79 ms 79 ms 79 ms be3183.ccr31.par04.atlas.cogentco.com [154.54.38.66]
9 79 ms 78 ms 78 ms ae-6.r04.parsfr01.fr.bb.gin.ntt.net [130.117.14.166]
10 86 ms 86 ms 85 ms ae-2.r25.londen12.uk.bb.gin.ntt.net [129.250.6.13]
11 * * 85 ms ae-1.r24.londen12.uk.bb.gin.ntt.net [129.250.2.26]
12 156 ms 156 ms 156 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
13 * 229 ms * ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 230 ms 231 ms 230 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 248 ms 237 ms * ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 241 ms 240 ms 241 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
17 243 ms 245 ms 246 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 242 ms 242 ms 241 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 242 ms 242 ms 241 ms 204.2.229.234
20 242 ms 242 ms 242 ms 204.2.229.81
Trace complete.
Type of Issue/Feedback: Latency went way higher after server move, from 170 to 280.
Name of your Internet Service Provider (ISP): Oi Velox
State/Country: Rio Grande do Sul/Brazil
Date/Time: Since migration of NA datacenters
World Name: Behemoth
Frequency: Every time (Sometimes getting major package loss [receiving going from 200 to 4000])
Traceroute records: https://pastebin.com/vwBEZKFp
Type of Issue/Feedback: Ping goes up from 130 to 230 ~ 240
Name of your Internet Service Provider (ISP): NET Virtua
State/Country: São Paulo / Brazil
Date/Time: Since datacenters realocation.
World Name: Behemoth
Frequency: Full time
Type of Issue/Feedback: increase in latency, before migration: 165ms; after migration: 295ms
Name of your Internet Service Provider (ISP): VIVO Fibra
State/Country: São Paulo/Brazil
Date/Time: started just after the migration
World Name: Brynhildr
Frequency: all the time
Traceroute records (optional): https://pastebin.com/NY5vE802
Thank you for looking into that, I really appreciate it! ^^
Type of Issue/Feedback: latency went way higher after server move, from 160~180 to 215~250
Name of your Internet Service Provider (ISP): I have two ISPs OI Velox and West
State/Country: Rio de Janeiro/Brazil
Date/Time: Right after the server change to Sacramento
World Name: Behemoth
Frequency: All the Time
Additional Info: It's funny cause on OI Velox the packages goes to New York and have to cross the entire State to arrive in Sacramento, on West it goes through Miami. I were able to reduce my latency to 160~170 by paying yet another service called (NoPing), but unfortunately I didn't find a way to do a traceroute inside it to see which nodes it uses =(
Traceroute to Behemoth IP:
ISP: OI Velox
ISP: WESTCode:1 1 ms <1 ms <1 ms 10.0.0.252
2 28 ms 27 ms 27 ms 179-192-74-1.user.veloxzone.com.br [179.192.74.1]
3 29 ms 29 ms 29 ms 200.164.11.74
4 145 ms 151 ms 129 ms xe-11-0-0.0-bot-rj-rotn-j01.telemar.net.br [200.164.40.72]
5 * * * Esgotado o tempo limite do pedido.
6 153 ms 153 ms 143 ms 100.122.17.173
7 173 ms 137 ms 132 ms ix-xe-10-1-3-1-0.tcore1.NTO-New-York.as6453.net [209.58.26.65]
8 143 ms 144 ms 141 ms if-ae-9-2.tcore1.N75-New-York.as6453.net [63.243.128.122]
9 143 ms 130 ms 129 ms ae-8.r07.nycmny01.us.bb.gin.ntt.net [129.250.9.113]
10 155 ms 168 ms 156 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
11 219 ms 205 ms 206 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
12 217 ms 218 ms 205 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
13 224 ms 213 ms 210 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
14 215 ms 227 ms 217 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
15 217 ms 226 ms 218 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
16 220 ms 217 ms 229 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
17 231 ms 219 ms 227 ms 204.2.229.234
18 218 ms 228 ms 227 ms 204.2.229.96
Code:1 1 ms <1 ms 1 ms 10.0.0.253
2 5 ms 3 ms 2 ms abel.cbf.west.net.br [186.237.43.39]
3 8 ms 13 ms 7 ms 46.43.237.186.in-addr.arpa [186.237.43.46]
4 7 ms 6 ms 6 ms 49.43.237.186.in-addr.arpa [186.237.43.49]
5 8 ms 9 ms * 186.219.21.101.nqt.com.br [186.219.21.101]
6 125 ms 122 ms 125 ms sl-st51-mia-.sprintlink.net [160.81.69.49]
7 125 ms 122 ms 126 ms 144.232.14.217
8 125 ms 121 ms 122 ms ae-13.a01.miamfl02.us.bb.gin.ntt.net [129.250.9.57]
9 211 ms 209 ms * ae-5.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.166]
10 126 ms 123 ms 125 ms ae-4.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.184]
11 146 ms 148 ms 153 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
12 212 ms 216 ms 212 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
13 220 ms 220 ms 217 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
14 217 ms 215 ms 213 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
15 217 ms 217 ms 221 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 * 214 ms 214 ms 204.2.229.234
17 214 ms 217 ms 217 ms 204.2.229.96
Type of Issue: Increase in latency 150 ms to 300ms
ISP: VIVO
State/Country:São Paulo/Brazil
date/time: all the time
World Name:Behemoth
Frequency: all the time
Type of Issue/Feedback: 40ms before to 120-130ms now. People hundreds of miles further from the server have better latency (people in Montreal say they get 85-95, and I'm in western NY). In dungeons and without a tunneling service, I have frequent spikes that result in skills not firing off or being very delayed. With WTFast, I drop to around 100ms average and have almost no spikes at all, so I guess the extra thousand miles with the weird routing is likely the culprit.
Name of your Internet Service Provider (ISP): Time Warner Cable / Charter Spectrum
State/Country: New York
Date/Time: Right after datacenter move.
World Name: Cactuar
Frequency: Constant.
Traceroute:
Code:Tracing route to 204.2.229.84 over a maximum of 30 hops
1 2 ms 9 ms 1 ms 192.168.1.1
2 19 ms 19 ms 19 ms 142.254.215.29
3 126 ms 37 ms 29 ms agg61.lkwnnyad01h.northeast.rr.com [24.58.217.89]
4 17 ms 19 ms 18 ms agg38.lkwnnyad02r.northeast.rr.com [24.58.38.2]
5 25 ms 33 ms 33 ms be29.albynyyf01r.northeast.rr.com [24.58.32.58]
6 37 ms 37 ms 45 ms bu-ether36.nycmny837aw-bcr00.tbone.rr.com [107.14.19.100]
7 26 ms 32 ms 30 ms 205.197.232.13
8 32 ms 44 ms 39 ms 207.88.14.150.ptr.us.xo.net [207.88.14.150]
9 36 ms 38 ms 37 ms 216.156.16.131.ptr.us.xo.net [216.156.16.131]
10 35 ms 39 ms 37 ms 206.111.13.193.ptr.us.xo.net [206.111.13.193]
11 36 ms 39 ms 39 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
12 103 ms 120 ms 99 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
13 114 ms 109 ms 109 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
14 110 ms 114 ms 119 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
15 128 ms 129 ms 129 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
16 115 ms 124 ms 124 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
17 120 ms 124 ms 113 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 123 ms 125 ms * 204.2.229.234
19 127 ms 124 ms 120 ms 204.2.229.84
Trace complete.