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

[Mhaeric]

That's an ISP problem not a FF problem.

I believe it is something that a game company can request changes to in order to accommodate better routing, however. That said, and I'm not an expert by any means, in this case I suspect it is just a case of it being that the best routes haven't been established yet since it's a new traffic pattern. I'd give it a day to settle.

[magnanimousCynic]

I live in Central Indiana and my CMD is currently showing about 80 ping average, sometimes going to 70 or 90. No idea what it was before since I play on PS4 and didn't bother to check beforehand.

[Sekkei]

I'm not IT knowledgeable or anywhere close to it but while the servers have been down for the move I was poking Google, which was not being helpful at all as usual, to see which coast was more beneficial to put a data center for a game, especially of 14's size and traffic. General upkeep focused and not on if the ping is bad for people halfway across the globe. The closest thing to an answer I could find after many different wording attempts was http://resource.onlinetech.com/the-b...n-does-matter/ which looked like a reasonable placement choice to me. SE's choice to put their game wherever they want in the end but I figured that the cooler climate thing and less disasters would be a winner to not have a Montreal repeat of problems with the servers, even if that was traffic based issues. Meh. To each their own I guess

[Awful]

My girlfriend lives in Canada and she just watched her ping go from 100 to 480.

I live in Sydney Nova Scotia I'll check my ping and see if anythings changed hope Sellie gets better internet for SB .

Edit: I play on wireless but I have fiber op so I'll see if I tanked any xD

[Mekhana]

That's an ISP problem not a FF problem.

Really? Why can I connect to Blizzard at 100ms then? The server's next door.

Also, for safe keeping.

Old tracert:

  1    <1 ms    <1 ms    <1 ms  PowerBox.home [192.168.25.1]
  2     6 ms     6 ms     5 ms  179.184.126.196.static.adsl.gvt.net.br [179.184.126.196]
  3     6 ms     6 ms     6 ms  201.22.65.103.dynamic.dialup.gvt.net.br [201.22.65.103]
  4    20 ms    15 ms    15 ms  201.22.64.99.dynamic.dialup.gvt.net.br [201.22.64.99]
  5    15 ms    15 ms    15 ms  5.53.1.164
  6   127 ms   128 ms   127 ms  94.142.98.157
  7     *        *        *     Request timed out.
  8   175 ms   175 ms   175 ms  ae-2-12.bear1.Montreal2.Level3.net [4.69.203.129]
  9   171 ms   170 ms   170 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 10     *        *        *     Request timed out.
 11   164 ms   164 ms   164 ms  192.34.76.2
 12   170 ms   170 ms   171 ms  199.91.189.234
 13   165 ms   175 ms   170 ms  199.91.189.25

New tracert:

1    <1 ms    <1 ms    <1 ms  PowerBox.home [192.168.25.1]
  2     6 ms     5 ms     5 ms  179.184.126.196.static.adsl.gvt.net.br [179.184.126.196]
  3     6 ms     6 ms     7 ms  201.22.65.105.dynamic.dialup.gvt.net.br [201.22.65.105]
  4    38 ms    19 ms    23 ms  201.22.64.97.dynamic.dialup.gvt.net.br [201.22.64.97]
  5    23 ms    18 ms    18 ms  grtsanem4-7-0-5-4.net.telefonicaglobalsolutions.com [216.184.112.120]
  6   135 ms   136 ms   136 ms  94.142.98.83
  7   168 ms   168 ms   176 ms  84.16.15.192
  8   249 ms   249 ms   249 ms  213.140.35.217
  9   257 ms   256 ms   256 ms  5.53.3.20
 10   261 ms   261 ms   261 ms  ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
 11   264 ms   263 ms   265 ms  ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
 12   257 ms   261 ms   258 ms  ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
 13   304 ms   304 ms   304 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
 14   309 ms   308 ms   308 ms  ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
 15   309 ms   308 ms   308 ms  ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
 16   312 ms   312 ms   312 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 17   309 ms   309 ms   309 ms  204.2.229.234
 18   308 ms   309 ms   309 ms  204.2.229.9

[Mhaeric]

I don't think they've actually ever upgraded anything since they got internet up there in the early 2000's.

This is definitely the cause then. The fact that she was already getting a 100ms ping even while only being just a hop and a skip away further confirms it. That sucks for her.

[Mhaeric]

Really? Why can I connect to Blizzard at 100ms then? The server's next door.

Because Square Enix isn't responsible for where things get routed between you and their data centre. They can request that changes be made, but they're not the ones that have the control over it.

[Kethic]

They're definitely changing stuff- now I'm getting routed through Texas and the connection's getting dropped there. Wish I had huge tub of popcorn while waiting to see how this plays out... also neolobby2.ffxiv.com is listed as 92.242.140.21. Wish my networking courses had spent less time on the theoretical and more on the practical- this stuff is fascinating.

I'm going to laugh if the neolobbyXX IPs we've been pinging and tracert'ing were pre-prod IPs, not production IPs.

[Jaxelyn]

I'm going to laugh if the neolobbyXX IPs we've been pinging and tracert'ing were pre-prod IPs, not production IPs.

Technically, they do have an office in Cali also... if they parked those domains at their office first and are changing before servers go up, I think SE should get a prize for trolling

[Hestzhyen]

I'm going to laugh if the neolobbyXX IPs we've been pinging and tracert'ing were pre-prod IPs, not production IPs.

Apparently it's neolobby02, not neolobby2. Someone corrected my mistake and the former address is working- still resolved out in Sacramento. I'd love it to be a huge misunderstanding though.