As of this moment it seems SOMEONE is trying to fix the routing problem. At least the routing isn't going to amsterdam, so we lost 100 or so milliseconds. A few days ago the latency here was like 340ms, now it's 217. It's going somewhere.

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 2 ms <1 ms <1 ms 192.168.0.1
2 <1 ms 1 ms <1 ms 172.16.199.10
3 <1 ms 1 ms <1 ms 172.16.199.9
4 1 ms 1 ms <1 ms 172.16.200.1
5 3 ms * 1 ms 128-193-186-82.andradas-net.com.br [186.193.128.82]
6 5 ms * 4 ms 187-50-36-1.customer.tdatabrasil.net.br [187.50.36.1]
7 7 ms 7 ms * 187-100-83-12.dsl.telesp.net.br [187.100.83.12]
8 19 ms 17 ms 17 ms 5.53.1.30
9 125 ms 123 ms 121 ms 5.53.3.143
10 154 ms 155 ms 152 ms 94.142.126.161
11 159 ms 158 ms 159 ms ae-11.r07.nycmny01.us.bb.gin.ntt.net [129.250.9.1]
12 151 ms 150 ms 150 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
13 217 ms 219 ms 215 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 217 ms 214 ms 217 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 213 ms 213 ms 211 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 219 ms 218 ms 218 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
17 219 ms 217 ms 217 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 219 ms 217 ms 217 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 219 ms 218 ms * 204.2.229.234
20 217 ms 216 ms 217 ms 204.2.229.9