[Data Center USA] Ping increased. Report your changes here.

[Uzephi]

Looks like SE managed to make the worst possible decision and the servers are indeed in CA. Good job guys.

Your fall is my gain? I went from 190+ to under 40. Kinda like it.

[thorkellthetall]

Your fall is my gain? I went from 90+ to under 40. Kinda like it.

Nerd, you still have to play with everyone else. Your party member's performance suffers as well. The entire NA region did not also move to CA.

[Sekkei]

This is going to be an interesting situation then. Put on your helmets for the European fallout, I guess? Oh dear :x

[Mekhana]

It does seem like there has been an improvement maybe its because there's nobody online right now haha

[SirFujimoto]

Comparing

neolobby02.ffxiv.com - 204.2.229.9

to

Aether: 199.91.189.74

Looks like I went from 43ms to 96ms :/

Although the trace completed significantly faster when testing the CA ip.

[Rokke]

110ms -> 36ms
bless u cali

[Mhaeric]

Okay, now that the servers are live, I've confirmed Balmung's IP to be 204.2.229.82 and here's my results from a ping and tracert which appears to confirm Sacramento:

C:\Users\#####>ping 204.2.229.82

Pinging 204.2.229.82 with 32 bytes of data:
Reply from 204.2.229.82: bytes=32 time=49ms TTL=53
Reply from 204.2.229.82: bytes=32 time=46ms TTL=53
Reply from 204.2.229.82: bytes=32 time=39ms TTL=53
Reply from 204.2.229.82: bytes=32 time=49ms TTL=53

Ping statistics for 204.2.229.82:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 49ms, Average = 45ms

C:\Users\#####>tracert 204.2.229.82

Tracing route to 204.2.229.82 over a maximum of 30 hops

  1     3 ms    10 ms     8 ms  192.168.0.1
  2    19 ms    14 ms    19 ms  24.86.64.1
  3    16 ms    29 ms    63 ms  rd3st-tge0-4-0-1-1.vc.shawcable.net [64.59.147.205]
  4   104 ms    19 ms    24 ms  rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
  5    23 ms    26 ms    29 ms  xe-0-5-0-17.r04.sttlwa01.us.bb.gin.ntt.net [129.250.197.17]
  6    19 ms    26 ms    20 ms  ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
  7    46 ms     *       40 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
  8    46 ms    41 ms    48 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
  9    47 ms    38 ms    44 ms  ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
 10    48 ms    40 ms    47 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 11    43 ms   171 ms   129 ms  204.2.229.234
 12    50 ms    49 ms    49 ms  204.2.229.82

Trace complete.

So, I went from ~90 ping from Montreal to ~45 ping from Sacramento.

[anryo]

And just saying it one more time. People who got a better connection now are people who went from 90 to 70 or from 90 to 40. This will not make any difference on your game, srsly. Anything under 100 is basically the same shit. But I can assure you that people that went from 150 to 250+ are totally screwed up. And if you guys think its funny, dont forget that everyone uses DF too. So enjoy lots of dps eating 100% more AoE.

[MeoTwister5]

I'm getting 170-180 from what used to be 200+. Western Pacific region.

I like it.

[Ryuko]

I'm on the East Coast (NYC)... was at a 20ish ms ping before the change, now at a 78ms ping. First thing I did upon logging in was queue up for Titan Ex with my buddies. There is a noticeable latency increase, but not enough for the game to be unplayable. In the grand scheme of things, 78ms isn't *that* bad. However, I've been 'spoiled' in that I always knew I had a *lot* of time to get out of AoEs due to my low latency. I knew exactly how greedy I could be without needing to move immediately. Now, with the higher latency, I'm going to have to retrain my brain to know how much time I have to cast or get out. I played around with the latency on landslide -- first, moving immediately, then slowly extending my time in it to the point where I knew I'd previously be able to get out (after finishing a cast). I got hit the final time. So, many of us will need to retrain our brains -- but it's definitely not unplayable, at least on my end. I think now is the best time they could have done this... it will give those of us with noticeable ping changes some time to adjust our brains and muscle memory before facing any serious content in Stormblood.