Reporting Issues Resulting from the North American Data Center Relocation

[Hayate188]

Type of Issue/Feedback: Ping went from 160ms to 315ms
Name of your Internet Service Provider (ISP): Vivo
State/Country: Distrito Federal / Brazil
Date/Time: 05/17 / Entire Time
World Name: Behemoth
Frequency: Entire time
Traceroute records:

Rastreando a rota para 204.2.229.10 com no máximo 30 saltos

1 <1 ms <1 ms <1 ms PowerBox [192.168.25.1]
2 6 ms 6 ms 9 ms gvt-b-sr05.bsa.gvt.net.br [179.184.126.71]
3 6 ms 23 ms 5 ms 177.205.8.229.static.adsl.gvt.net.br [177.205.8.229]
4 29 ms 29 ms 29 ms 5.53.1.160
5 136 ms 142 ms 142 ms 94.142.98.159
6 176 ms 175 ms 178 ms xe6-0-6-0-grtnycpt3.net.telefonicaglobalsolutions.com [213.140.49.68]
7 247 ms 246 ms 246 ms 213.140.35.217
8 266 ms 265 ms 266 ms 5.53.3.20
9 256 ms 255 ms 256 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
10 251 ms 251 ms 251 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
11 254 ms 254 ms 254 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
12 308 ms 308 ms 316 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
13 313 ms 312 ms 312 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
14 313 ms 314 ms 314 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
15 319 ms 319 ms 320 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 315 ms * * 204.2.229.234
17 317 ms 313 ms 315 ms 204.2.229.10

[WickedAngeal]

Type of Issue/Feedback: Inconsistent connection, ranging from 180ms to 240ms, essentially all EU players who have invested time, money and friendships on the american servers since as early as 2013 are now suffering either barely playable or completely unplayable differences in their connections. A centralized server is essential and the only considerate thing to do for your European, South American, North, East and West Americans. This would provide the the essential service that we pay for for monthly. It's recommended to forward to the Japanese development team the case of RIOT's League of Legends server move FROM California to central America for the exact same reasons.

Name of your Internet Service Provider (ISP): British Telecommunications

State/Country: Co.Antrim, Northern Ireland, United Kingdom

Date/Time: After 17th May - NA Datacenter Reposition to Sacramento, CA, USA.

World Name: Aether Datacenter - Gilgamesh

Frequency: Consistent - https://puu.sh/vVvrB/a9ff832aae.png

[ShenDrakar]

Type of Issue/Feedback: Ping went from 150ms to 201ms
Name of your Internet Service Provider (ISP): Net Virtua
State/Country: Rio de Janeiro / Brazil
Date/Time: 05/17 / Entire Time
World Name: Balmung
Frequency: Entire time
Traceroute records

[Redwater159]

Type of Issue/Feedback: It's to be expected, but my ping shot up from 145-150 to 240-260, some days up to 300. I also get lag spikes here and there, and I notice that oddly enough, battle content instances (Dungeons/Trials etc.) seems to have a more prominent delay on actions and inputs. The weird thing is, if I use a routing service, my ping actually goes down to 190-200. I'm not a super tech savvy person, but it seems like the biggest issue since the move is routing, more so than distance alone.

Name of your Internet Service Provider (ISP): Saudi Telecom Company (STC)

State/Country: Riyadh, Saudi Arabia.

Date/Time: Since the relocation of the data centers.

World Name: Jenova.

Frequency: Constant.

Tracert Records

Tracing route to 204.2.229.81 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.100.1
2 52 ms 3 ms 3 ms 37.104.128.1
3 4 ms 3 ms 4 ms 84-235-86-42.saudi.net.sa [84.235.86.42]
4 4 ms 3 ms 5 ms 84-235-94-137.saudi.net.sa [84.235.94.137]
5 19 ms 19 ms 19 ms 84-235-123-224.saudi.net.sa [84.235.123.224]
6 69 ms 68 ms 68 ms hu0-3-0-0.ccr21.mrs01.atlas.cogentco.com [149.14.124.97]
7 79 ms 79 ms 79 ms be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
8 79 ms 79 ms 79 ms be3183.ccr31.par04.atlas.cogentco.com [154.54.38.66]
9 79 ms 78 ms 78 ms ae-6.r04.parsfr01.fr.bb.gin.ntt.net [130.117.14.166]
10 86 ms 86 ms 85 ms ae-2.r25.londen12.uk.bb.gin.ntt.net [129.250.6.13]
11 * * 85 ms ae-1.r24.londen12.uk.bb.gin.ntt.net [129.250.2.26]
12 156 ms 156 ms 156 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
13 * 229 ms * ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 230 ms 231 ms 230 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 248 ms 237 ms * ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 241 ms 240 ms 241 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
17 243 ms 245 ms 246 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 242 ms 242 ms 241 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 242 ms 242 ms 241 ms 204.2.229.234
20 242 ms 242 ms 242 ms 204.2.229.81

Trace complete.

[MayuKranjcar]

Type of Issue/Feedback: Latency went way higher after server move, from 170 to 280.
Name of your Internet Service Provider (ISP): Oi Velox
State/Country: Rio Grande do Sul/Brazil
Date/Time: Since migration of NA datacenters
World Name: Behemoth
Frequency: Every time (Sometimes getting major package loss [receiving going from 200 to 4000])
Traceroute records: https://pastebin.com/vwBEZKFp

[Balserion]

Type of Issue/Feedback: Ping goes up from 130 to 230 ~ 240
Name of your Internet Service Provider (ISP): NET Virtua
State/Country: São Paulo / Brazil
Date/Time: Since datacenters realocation.
World Name: Behemoth
Frequency: Full time

[ThanosViserio]

Type of Issue/Feedback: increase in latency, before migration: 165ms; after migration: 295ms
Name of your Internet Service Provider (ISP): VIVO Fibra
State/Country: São Paulo/Brazil
Date/Time: started just after the migration
World Name: Brynhildr
Frequency: all the time
Traceroute records (optional): https://pastebin.com/NY5vE802

[Legewiel]

Thank you for looking into that, I really appreciate it! ^^

Type of Issue/Feedback: latency went way higher after server move, from 160~180 to 215~250
Name of your Internet Service Provider (ISP): I have two ISPs OI Velox and West
State/Country: Rio de Janeiro/Brazil
Date/Time: Right after the server change to Sacramento
World Name: Behemoth
Frequency: All the Time
Additional Info: It's funny cause on OI Velox the packages goes to New York and have to cross the entire State to arrive in Sacramento, on West it goes through Miami. I were able to reduce my latency to 160~170 by paying yet another service called (NoPing), but unfortunately I didn't find a way to do a traceroute inside it to see which nodes it uses =(

Traceroute to Behemoth IP:
ISP: OI Velox

  1     1 ms    <1 ms    <1 ms  10.0.0.252 
  2    28 ms    27 ms    27 ms  179-192-74-1.user.veloxzone.com.br [179.192.74.1] 
  3    29 ms    29 ms    29 ms  200.164.11.74 
  4   145 ms   151 ms   129 ms  xe-11-0-0.0-bot-rj-rotn-j01.telemar.net.br [200.164.40.72] 
  5     *        *        *     Esgotado o tempo limite do pedido.
  6   153 ms   153 ms   143 ms  100.122.17.173 
  7   173 ms   137 ms   132 ms  ix-xe-10-1-3-1-0.tcore1.NTO-New-York.as6453.net [209.58.26.65] 
  8   143 ms   144 ms   141 ms  if-ae-9-2.tcore1.N75-New-York.as6453.net [63.243.128.122] 
  9   143 ms   130 ms   129 ms  ae-8.r07.nycmny01.us.bb.gin.ntt.net [129.250.9.113] 
 10   155 ms   168 ms   156 ms  ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180] 
 11   219 ms   205 ms   206 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13] 
 12   217 ms   218 ms   205 ms  ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54] 
 13   224 ms   213 ms   210 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124] 
 14   215 ms   227 ms   217 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119] 
 15   217 ms   226 ms   218 ms  ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33] 
 16   220 ms   217 ms   229 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 
 17   231 ms   219 ms   227 ms  204.2.229.234 
 18   218 ms   228 ms   227 ms  204.2.229.96

ISP: WEST

  1     1 ms    <1 ms     1 ms  10.0.0.253 
  2     5 ms     3 ms     2 ms  abel.cbf.west.net.br [186.237.43.39] 
  3     8 ms    13 ms     7 ms  46.43.237.186.in-addr.arpa [186.237.43.46] 
  4     7 ms     6 ms     6 ms  49.43.237.186.in-addr.arpa [186.237.43.49] 
  5     8 ms     9 ms     *     186.219.21.101.nqt.com.br [186.219.21.101] 
  6   125 ms   122 ms   125 ms  sl-st51-mia-.sprintlink.net [160.81.69.49] 
  7   125 ms   122 ms   126 ms  144.232.14.217 
  8   125 ms   121 ms   122 ms  ae-13.a01.miamfl02.us.bb.gin.ntt.net [129.250.9.57] 
  9   211 ms   209 ms     *     ae-5.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.166] 
 10   126 ms   123 ms   125 ms  ae-4.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.184] 
 11   146 ms   148 ms   153 ms  ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86] 
 12   212 ms   216 ms   212 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237] 
 13   220 ms   220 ms   217 ms  ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27] 
 14   217 ms   215 ms   213 ms  ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31] 
 15   217 ms   217 ms   221 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 
 16     *      214 ms   214 ms  204.2.229.234 
 17   214 ms   217 ms   217 ms  204.2.229.96

[SakuraHanna]

Type of Issue: Increase in latency 150 ms to 300ms
ISP: VIVO
State/Country:São Paulo/Brazil
date/time: all the time
World Name:Behemoth
Frequency: all the time

[Aethaeryn]

Type of Issue/Feedback: 40ms before to 120-130ms now. People hundreds of miles further from the server have better latency (people in Montreal say they get 85-95, and I'm in western NY). In dungeons and without a tunneling service, I have frequent spikes that result in skills not firing off or being very delayed. With WTFast, I drop to around 100ms average and have almost no spikes at all, so I guess the extra thousand miles with the weird routing is likely the culprit.

Name of your Internet Service Provider (ISP): Time Warner Cable / Charter Spectrum

State/Country: New York

Date/Time: Right after datacenter move.

World Name: Cactuar

Frequency: Constant.

Traceroute:

Tracing route to 204.2.229.84 over a maximum of 30 hops

  1     2 ms     9 ms     1 ms  192.168.1.1
  2    19 ms    19 ms    19 ms  142.254.215.29
  3   126 ms    37 ms    29 ms  agg61.lkwnnyad01h.northeast.rr.com [24.58.217.89]
  4    17 ms    19 ms    18 ms  agg38.lkwnnyad02r.northeast.rr.com [24.58.38.2] 
  5    25 ms    33 ms    33 ms  be29.albynyyf01r.northeast.rr.com [24.58.32.58] 
  6    37 ms    37 ms    45 ms  bu-ether36.nycmny837aw-bcr00.tbone.rr.com [107.14.19.100]
  7    26 ms    32 ms    30 ms  205.197.232.13
  8    32 ms    44 ms    39 ms  207.88.14.150.ptr.us.xo.net [207.88.14.150]
  9    36 ms    38 ms    37 ms  216.156.16.131.ptr.us.xo.net [216.156.16.131]
 10    35 ms    39 ms    37 ms  206.111.13.193.ptr.us.xo.net [206.111.13.193]
 11    36 ms    39 ms    39 ms  ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
 12   103 ms   120 ms    99 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
 13   114 ms   109 ms   109 ms  ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
 14   110 ms   114 ms   119 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 15   128 ms   129 ms   129 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
 16   115 ms   124 ms   124 ms  ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
 17   120 ms   124 ms   113 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 18   123 ms   125 ms     *     204.2.229.234
 19   127 ms   124 ms   120 ms  204.2.229.84

Trace complete.