Having really bad lag and packet and connection loss since 2.38 but has increased in severity lately.

Here's a ping test of the JP data center

Ping statistics for 124.150.157.158:
Packets: Sent = 50, Received = 30, Lost = 20 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 284ms, Average = 203ms

Route trace

Tracing route to 124.150.157.158 over a maximum of 30 hops

1 8 ms 9 ms 9 ms 10.126.152.1
2 18 ms 11 ms 11 ms 209.148.243.45
3 14 ms 11 ms 11 ms 69.63.248.205
4 15 ms 13 ms 13 ms ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]

5 11 ms 20 ms 9 ms gw-he.torontointernetxchange.net [206.108.34.112
]
6 80 ms 23 ms 24 ms 100ge13-1.core1.chi1.he.net [184.105.80.5]
7 72 ms 74 ms 75 ms 10ge11-4.core1.pao1.he.net [184.105.222.173]
8 73 ms 74 ms 75 ms 10ge3-1.core1.sjc2.he.net [72.52.92.70]
9 75 ms 73 ms 77 ms pacnet.10gigabitethernet2-2.core1.sjc2.he.net [2
16.218.192.234]
10 74 ms 76 ms 74 ms gi2-0-0.gw1.sjc1.asianetcom.net [202.147.50.210]

11 193 ms 198 ms 184 ms po4-0-0.cr1.nrt1.asianetcom.net [202.147.0.33]
12 198 ms 187 ms 186 ms squareco.asianetcom.net [203.192.149.210]
13 175 ms 212 ms 177 ms 61.195.56.129
14 173 ms 175 ms 172 ms 219.117.144.70
15 176 ms 177 ms 172 ms 219.117.144.49
16 186 ms 186 ms 188 ms 219.117.144.29
17 192 ms 194 ms 194 ms 219.117.147.186
18 173 ms 196 ms 197 ms 124.150.157.158

Trace complete.

Funny thing looking at the traceroute. Packets from NA to JP take ony 74 ms but within JP, there's a pass off that more than doubles that time at asiannetcom which is SE's provider according to the above.