Reporting Issues Resulting from the North American Data Center Relocation

[Fourbestintoner]

The routing to califonia is just beyond awful, they should have moved them to Chicago, best structure all of the US, low ping for everyone, but they wanted to save money.

[dark494]

It is especially bad right now. I don't know exactly what server/hop it is that's just before the lobby server itself, but whatever is at 204.2.229.234 is currently suffering about a 40%+ packet loss rate right now.

Target Name: 204.2.229.9
         IP: 204.2.229.9
  Date/Time: 9/13/2017 6:06:14 PM - 9/13/2017 6:16:14 PM

Hop  Sent  PL%    Min     Max    Avg  Host Name / [IP]
  1   241    0   0.10    2.42   0.47  192.168.1.1 [192.168.1.1]
  2   241    0   4.88   81.60  17.92  96.120.101.65 [96.120.101.65]
  3   241    0   3.97   61.56  18.00  po-113-rur101.bellevue.wa.seattle.comcast.net [162.151.209.133]
  4   241    1   4.45   47.95  18.88  po-2-rur102.bellevue.wa.seattle.comcast.net [69.139.160.26]
  5   241    1   5.81   49.01  19.92  69.139.164.77 [69.139.164.77]
  6   241    1   7.06   46.01  21.88  be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
  7   241    2   4.90   53.67  20.59  be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]
  8   241    1   8.02   86.53  22.97  ae-31.a00.sttlwa01.us.bb.gin.ntt.net [129.250.66.149]
  9   241    0  33.87  155.92  92.46  ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
 10   241    1   5.23   71.12  23.10  ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
 11   241    1  26.02  128.02  65.80  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 12   241    0  28.59  110.87  60.13  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
 13   241    1  31.17  120.40  68.85  ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
 14   241    0  27.91  140.20  74.92  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 15   241   41  33.35  154.00  88.37  204.2.229.234 [204.2.229.234]
 16   241    2  32.23  137.19  73.66  204.2.229.9 [204.2.229.9]

[Cenewulf]

Type of Issue/Feedback:Constant 90001 and 90002
Name of your Internet Service Provider (ISP): Xfinity
State/Country: Oregon USA
Date/Time: Today 9/14/2017 as of this morning
World Name: Lamia
Frequency: A few hours now straight

[shinoobu]

Type of Issue/Feedback: latency went way higher after server move, from ~130 to ~200
Name of your Internet Service Provider (ISP): Net Virtua
State/Country: Sao Paulo / Brasil
Date/Time: Entire time
World Name: Behemoth
Frequency: Entire time

[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

[Zarkovitch]

Hello!
my current issue is package loss on 204.2.229.234 i am losing 15-23% package
Provider: Acanac
Country:Canada,Quebec
Date/Time:23/09/2017
Frequency: on the week on evening/night

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host Loss % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 455 | 455 | 0 | 0 | 10 | 0 |
| 10.246.208.65 - 0 | 455 | 455 | 3 | 8 | 28 | 8 |
| 10.170.192.53 - 0 | 455 | 455 | 4 | 9 | 29 | 9 |
| 206-80-244-169.cpe.distributel.net - 0 | 455 | 455 | 4 | 9 | 32 | 9 |
| 204.101.4.85 - 0 | 455 | 455 | 14 | 20 | 63 | 19 |
| tcore3-montreal02_1-14-0-0.net.bell.ca - 0 | 455 | 455 | 18 | 21 | 40 | 20 |
|tcore3-newyorkaa_hundredgige0-5-0-0.net.bell.ca - 0 | 455 | 455 | 15 | 21 | 40 | 23 |
|bx7-newyork83_hundredgige0-6-0-0.net.bell.ca - 0 | 455 | 455 | 16 | 20 | 39 | 20 |
| ae-49.a01.nycmny01.us.bb.gin.ntt.net - 0 | 455 | 455 | 16 | 22 | 64 | 20 |
| ae-8.r08.nycmny01.us.bb.gin.ntt.net - 0 | 455 | 455 | 96 | 98 | 110 | 96 |
| ae-3.r24.nycmny01.us.bb.gin.ntt.net - 0 | 455 | 455 | 15 | 20 | 38 | 18 |
| ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 0 | 455 | 455 | 75 | 81 | 165 | 79 |
| ae-0.r21.sttlwa01.us.bb.gin.ntt.net - 0 | 455 | 455 | 75 | 84 | 173 | 82 |
| ae-3.r23.snjsca04.us.bb.gin.ntt.net - 0 | 455 | 455 | 87 | 91 | 104 | 91 |
| ae-45.r01.snjsca04.us.bb.gin.ntt.net - 0 | 455 | 455 | 92 | 96 | 108 | 95 |
| ae-1.r00.scrmca02.us.bb.gin.ntt.net - 0 | 455 | 455 | 91 | 96 | 111 | 96 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 455 | 455 | 91 | 96 | 118 | 96 |
| 204.2.229.234 - 21 | 248 | 196 | 0 | 95 | 101 | 95 |
| 204.2.229.10 - 0 | 455 | 455 | 90 | 95 | 109 | 99 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[Rilora]

Type of Issue/Feedback: Frequent disconnects (90007)
Name of your Internet Service Provider (ISP): Spectrum
State/Country: Northern Kentucky
Date/Time: Ever sense server move / Stormblood release
World Name: Malborough
Frequency: Every 10 minutes to 1 hour
Traceroute records: Latest one:

Tracing route to 204.2.229.100 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    13 ms    11 ms    10 ms  142.254.147.45
  3    23 ms    30 ms   132 ms  ae63.flrnky1502h.midwest.rr.com [74.128.7.37]
  4    20 ms    20 ms    21 ms  be31.lsvmkyzo01r.midwest.rr.com [65.29.27.164]
  5    25 ms    27 ms    28 ms  be24.clmkohpe01r.midwest.rr.com [65.189.140.162]
  6    38 ms    36 ms    36 ms  bu-ether15.chctilwc00w-bcr00.tbone.rr.com [66.109.6.68]
  7    42 ms    36 ms    37 ms  bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
  8    34 ms    32 ms    32 ms  0.ae2.pr1.chi10.tbone.rr.com [107.14.17.196]
  9    32 ms    33 ms    31 ms  ix-ae-27-0.tcore2.CT8-Chicago.as6453.net [64.86.79.97]
 10    32 ms    31 ms    32 ms  if-ae-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.2]
 11    43 ms    36 ms    40 ms  64.86.78.18
 12   152 ms   100 ms    93 ms  ae-11.r05.chcgil09.us.bb.gin.ntt.net [129.250.3.144]
 13    32 ms    47 ms    33 ms  ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
 14    88 ms    88 ms    90 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 15   105 ms    92 ms    92 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 16    91 ms    92 ms    92 ms  ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
 17   158 ms    94 ms    97 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 18    91 ms    91 ms     *     204.2.229.234
 19    93 ms    93 ms    98 ms  204.2.229.100

[Myric]

I keep having high ping in game. When I ping the servers outside of the game, the ping rate is low, however it will hit 180 in the game when I pull up network monitoring in windows. I live 45 minutes away from Sacramento, it should be fast! I'll post my tracert

Tracing route to 204.2.229.88 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 172.16.200.1
2 11 ms 30 ms 9 ms 96.120.14.157
3 9 ms 14 ms 9 ms xe-11-1-2-sur01.yubacity.ca.ccal.comcast.net [162.151.3.193]
4 10 ms 10 ms 10 ms ae-15-ar01.sacramento.ca.ccal.comcast.net [162.151.40.53]
5 15 ms 15 ms 15 ms be-33667-cr01.9greatoaks.ca.ibone.comcast.net [68.86.93.25]
6 14 ms 14 ms 15 ms hu-0-16-0-0-pe03.11greatoaks.ca.ibone.comcast.net [68.86.86.242]
7 13 ms 13 ms 14 ms ae-13.a02.snjsca04.us.bb.gin.ntt.net [129.250.66.33]
8 14 ms 13 ms 14 ms ae-9.r01.snjsca04.us.bb.gin.ntt.net [129.250.2.2]
9 19 ms 18 ms 18 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
10 17 ms 18 ms 18 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
11 17 ms * 19 ms 204.2.229.234
12 * 19 ms 18 ms 204.2.229.88

[Bariaus]

...

Dude. You're having 2x ms avg., what are you talking about. Also, Windows Network Monitor is bs. Been using a VPN which shows me the real ms tracking, while the thing you're using is showing a completely different thing.

[NinuSkeith]

Type of Issue/Feedback: Lag, disconnects (90006)
Name of your Internet Service Provider (ISP): Spectrum (Formerly Oceanic Time Warner Cable)
State/Country: Honolulu, Hawaii
Date/Time: For the last ten days
World Name: Sargantanas
Frequency: Varies, but generally hits in the evening (8:30-10pm HST)
Traceroute:

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 9 ms 8 ms 8 ms 142.254.190.133
3 31 ms 21 ms 22 ms xe-0-0-8.hnllhikm01h.hawaii.rr.com [24.25.229.49]
4 10 ms 11 ms 11 ms agg32.milnhixd01r.hawaii.rr.com [72.129.46.54]
5 62 ms 62 ms 63 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0]
6 63 ms 69 ms 63 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.3.230]
7 57 ms 57 ms 57 ms ae2.lsancarc0yw-bpr01.tbone.rr.com [66.109.1.41]

8 59 ms 58 ms 59 ms ix-ae-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]
9 60 ms 57 ms 57 ms if-ae-2-2.tcore2.LVW-Los-Angeles.as6453.net [66.110.59.2]
10 97 ms 74 ms 78 ms 64.86.252.134
11 84 ms * 82 ms ae-19.r00.lsanca07.us.bb.gin.ntt.net [129.250.3.235]
12 73 ms 66 ms 64 ms ae-2.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.237]
13 * 76 ms * ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
14 78 ms * * ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
15 186 ms 175 ms 175 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
16 * 92 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
17 80 ms * * 204.2.229.234
18 * 77 ms 78 ms 204.2.229.9

Trace complete.

It's pretty clear that the issue is on the ISP. Maybe Square can start making angry phone calls to whoever owns the network infrastructure around there?