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

[Jaxelyn]

Yeah I just noticed the odd bouncing being done to Netherlands and Spain. Hopefully Squeenix reads the forums and manages to fix this problem before servers come up.

Unfortunately, they don't have control over that and depending on the company controlling the internet, they might not even be able to complain about it.

[Mhaeric]

Yeah I just noticed the odd bouncing being done to Netherlands and Spain. Hopefully Squeenix reads the forums and manages to fix this problem before servers come up.

FWIW, from western Canada it doesn't do any odd hops. Not sure that's worth anything because we're located very close to the apparent location. My tracert from Vancouver only goes through Seattle and San Jose before arriving at Sacramento.

Tracing route to 204.2.229.9 over a maximum of 30 hops

  1    10 ms     7 ms     8 ms  192.168.0.1
  2    24 ms    20 ms    17 ms  24.86.64.1
  3    32 ms    18 ms    20 ms  rd3st-tge0-4-0-1-1.vc.shawcable.net [64.59.147.205]
  4    20 ms    25 ms    29 ms  rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
  5    18 ms    22 ms    30 ms  xe-0-6-0-19.r04.sttlwa01.us.bb.gin.ntt.net [129.250.200.193]
  6    23 ms    22 ms    31 ms  ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
  7    37 ms    44 ms    47 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
  8    62 ms    47 ms    50 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
  9    51 ms    43 ms    42 ms  ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
 10    43 ms    57 ms    47 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 11    77 ms    49 ms    48 ms  204.2.229.234
 12   152 ms    99 ms    49 ms  204.2.229.9

Trace complete.

[EdgeFayth]

[...]

From Van too, what is your ISP?

I still have packet losses with Telus, feelsbad

[Mhaeric]

From Van too, what is your ISP?

I still have packet losses with Telus, feelsbad

I'm with Shaw.

[Junkboy]

Yeah I just noticed the odd bouncing being done to Netherlands and Spain. Hopefully Squeenix reads the forums and manages to fix this problem before servers come up.

That's an ISP problem not a FF problem.

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

[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]

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.

[Sida]

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.

Not to mention, even if they were going to make such requests, there's no sense to make them before seeing where the routing settles after the move. Makes more sense to ask adjustments if needed.

edit: Sorry, I forgot logic was not allowed here ^^

[savageink]

Yeah I just noticed the odd bouncing being done to Netherlands and Spain. Hopefully Squeenix reads the forums and manages to fix this problem before servers come up.

That's all the individual nodes in the system trying to slowly correct their information. I wouldn't be surprised if the traceroute went to the International Space Station...