Reporting Issues Resulting from the North American Data Center Relocation

[StaticMew]

Type of Issue/Feedback: Much slower overall. No real issue with 90ks or disconnects of any kind, just a lot slower responses. Ping jumped from 50 to 130+. Not unplayable by any stretch, but it does feel limiting in what I can do. Also, I'm getting lower ping to the EU DC than I am to NA. California is probably the single worst place that it could have gone for myself personally.
Name of your Internet Service Provider (ISP): Bell
State/Country: Newfoundland, Canada
Date/Time: Since the move. Started around 120 ping after the move, but has increased to 135 since.
World Name: Gilgamesh
Frequency: Constant
Traceroute records:

For NA:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 15 ms 41 ms 9 ms loop0.17w.ba05.mtpr.nf.aliant.net [142.163.63.6]

3 7 ms 7 ms 3 ms be14-181.dr01.mtpr.nf.aliant.net [142.166.242.165]
4 6 ms 4 ms 3 ms be8.dr01.stjh.nf.aliant.net [142.166.185.89]
5 26 ms 26 ms 24 ms be5.cr01.drmo.ns.aliant.net [142.166.181.121]
6 23 ms 25 ms 25 ms et-5-1-0-50.cr02.drmo.ns.aliant.net [142.166.218.66]
7 30 ms 29 ms 33 ms ae4.cr02.stjh.nb.aliant.net [142.166.129.65]
8 43 ms 47 ms 45 ms ae0.bx01.toro.on.aliant.net [207.231.227.53]
9 45 ms 46 ms 47 ms ae52.edge1.Toronto2.Level3.net [4.31.208.9]
10 * * * Request timed out.
11 53 ms 51 ms 50 ms NTT-level3-90G.NewYork1.Level3.net [4.68.110.74]

12 49 ms 48 ms 50 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
13 118 ms 117 ms 117 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 112 ms 114 ms 110 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 130 ms 131 ms 131 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 135 ms 135 ms 136 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
17 136 ms 135 ms 136 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
18 137 ms 134 ms 135 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 * 135 ms 135 ms 204.2.229.234
20 132 ms 132 ms 136 ms 204.2.229.10

For EU, out of curiosity:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 3 ms 3 ms 4 ms loop0.17w.ba05.mtpr.nf.aliant.net [142.163.63.6]
3 5 ms 4 ms 4 ms be14-181.dr01.mtpr.nf.aliant.net [142.166.242.165]
4 4 ms 9 ms 7 ms be8.dr01.stjh.nf.aliant.net [142.166.185.89]
5 27 ms 25 ms 25 ms be5.cr01.drmo.ns.aliant.net [142.166.181.121]
6 23 ms 25 ms 26 ms et-5-1-0-50.cr02.drmo.ns.aliant.net [142.166.218.66]
7 27 ms 30 ms 28 ms ae4.cr02.stjh.nb.aliant.net [142.166.129.65]
8 47 ms 46 ms 46 ms ae0.bx01.toro.on.aliant.net [207.231.227.53]
9 46 ms 46 ms 46 ms bx2-torontoxn_ae3 [184.150.187.56]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 47 ms 46 ms 47 ms ae55.bar2.Toronto1.Level3.net [4.28.138.45]
15 125 ms 124 ms 126 ms ae-1-3107.edge5.Frankfurt1.Level3.net [4.69.163.18]
16 127 ms 135 ms 128 ms 212.162.4.98
17 129 ms 128 ms 127 ms 195.82.60.29
18 132 ms 131 ms 132 ms 195.82.61.14
19 132 ms 131 ms 131 ms 195.82.50.234
20 129 ms 131 ms 127 ms 195.82.50.9

[Oglaf]

Problem: Higher ping since server relocation, ping higher than EU servers.
Name of your Internet Service Provider (ISP): VIVO
Ticket or reference number from your ISP: Will not investigate since the problem is not at their end.
State/Country: SP/Brazil
Date/Time: Started May 17, 2017 after the server move.
Frequency: All the time. Latency used to be 160-180 and now is consistently 300+, I get better pings from EU servers (around 220-240).
Content: Impacts all activities.
Which in-game World were you playing on when the issue occurred?: Exodus.
Traceroute records: See below.

Trace route:
Tracing route to 204.2.229.109 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms openrg.home [192.168.1.1]
3 * * * Request timed out.
4 4 ms 10 ms 7 ms 187-100-39-217.dsl.telesp.net.br [187.100.39.217]
5 8 ms 9 ms 9 ms 201-0-5-73.dsl.telesp.net.br [201.0.5.73]
6 17 ms 11 ms 8 ms 187-100-35-21.dsl.telesp.net.br [187.100.35.21]
7 9 ms 8 ms 9 ms 84.16.6.102
8 121 ms 127 ms 127 ms 5.53.3.143
9 159 ms 156 ms 166 ms 213.140.35.14
10 241 ms 253 ms 247 ms 213.140.33.104
11 236 ms 235 ms 235 ms 213.140.35.1
12 266 ms 270 ms 277 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
13 278 ms 277 ms 271 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
14 248 ms 245 ms 245 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
15 297 ms 294 ms 294 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
16 294 ms 294 ms 294 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
17 301 ms 294 ms 294 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 301 ms 304 ms 294 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 296 ms 294 ms 294 ms 204.2.229.234
20 300 ms 294 ms 294 ms 204.2.229.109

Trace complete.

I tested VPN programs like Kill Ping and it solved the problem, which makes me 100% sure that the problem is with the route AFTER it reaches USA servers.