Reporting Issues Resulting from the North American Data Center Relocation

[Riko_Futatabi]

Type of Issue/Feedback: Lag spikes are constant in all locations in game. Also known as "rubber-banding". Everything will stop for a few seconds and then fast-forward to the current moment. Occasionally lasting up to 10~15 seconds and if it's longer I usually get booted to the login screen with error 90006.
Name of your Internet Service Provider (ISP): Sky
State/Country: Scotland, UK.
Date/Time: After patch 4.06a this started happening and has been constant throughout the day. Especially noticeable at the weekends, due to the increased traffic I'd assume.
World Name: Excalibur
Frequency: It's something I have to deal with constantly now.

This is just one of many trace route checks I have done. However from the many checks I noticed that from the 6th to 14th hop I will either occasionally get a sharp rise from the usual 90~180ms to over 2000ms and/or request timed out on many of these nodes.

Tracing route to 204.2.229.10 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  SkyRouter.Home [192.168.0.1]
  2     6 ms     6 ms     6 ms  97e7fe6a.skybroadband.com [151.231.254.106]
  3    18 ms    17 ms    17 ms  be365.pr2.hobir.isp.sky.com [2.120.8.0]
  4    17 ms    17 ms    17 ms  ae-3.r02.londen03.uk.bb.gin.ntt.net [83.231.221.45]
  5    17 ms    17 ms    17 ms  ae-3.r24.londen12.uk.bb.gin.ntt.net [129.250.4.23]
  6     *       83 ms    90 ms  ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
  7   158 ms   163 ms     *     ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
  8     *        *        *     Request timed out.
  9   171 ms   170 ms   171 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 10   179 ms   179 ms   179 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 11   177 ms   177 ms   177 ms  ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
 12   176 ms   176 ms   178 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 13   174 ms     *      174 ms  204.2.229.234
 14   182 ms   182 ms   182 ms  204.2.229.10

Trace complete.

This also occasionally shows that I'm getting a sharp spike in ms from the Primal Data Center.

Pinging 204.2.229.10 with 32 bytes of data:
Reply from 204.2.229.10: bytes=32 time=2181ms TTL=51
Reply from 204.2.229.10: bytes=32 time=173ms TTL=51
Reply from 204.2.229.10: bytes=32 time=172ms TTL=51
Reply from 204.2.229.10: bytes=32 time=172ms TTL=51

Ping statistics for 204.2.229.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 172ms, Maximum = 2181ms, Average = 674ms