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
Code:
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
Code:
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