Sounds like the same thing to be honest. This was what I sent to them almost a week back (and they haven't replied to me by email that they're looking into it).
Before the game started lagging (100 ms latency):
1 <1 ms <1 ms <1 ms RT-AC68U-33A0 [192.168.1.1]
2 52 ms 7 ms 2 ms ag-01-glsfb.ni.time.net.my [223.28.0.216]
3 2 ms 1 ms 1 ms ae2-er-01-glsfb.ni.time.net.my [223.28.26.41]
4 11 ms 15 ms 15 ms 223.28.2.1
5 8 ms 8 ms 7 ms Bundle-Ether1-br-01-mciwg.ni.time.net.my [223.28.26.82]
6 8 ms 8 ms 8 ms 124.158.226.149
7 8 ms 8 ms 7 ms xe-0-1-0-1.cr-gw-2-sin-pip.sg.globaltransit.net [124.158.224.241]
8 8 ms 9 ms 11 ms 124.158.224.70
9 84 ms 83 ms 76 ms 4826.sgw.equinix.com [27.111.228.74]
10 193 ms 194 ms 186 ms so-0-7-0-0.cor01.per02.wa.VOCUS.net.au [114.31.206.140]
11 179 ms * 182 ms bundle-102.cor03.syd03.nsw.vocus.net.au [114.31.206.128]
12 169 ms 178 ms 183 ms ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.73]
13 180 ms 178 ms 177 ms as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
14 185 ms 189 ms 178 ms 27.111.251.106
15 172 ms 168 ms 172 ms 103.4.115.248
After the game started lagging (>250 ms latency)
<1 ms <1 ms <1 ms RT-AC68U-33A0 [192.168.1.1]
2 2 ms 2 ms 1 ms ag-01-glsfb.ni.time.net.my [223.28.0.216]
3 2 ms 1 ms 1 ms ae2-er-01-glsfb.ni.time.net.my [223.28.26.41]
4 11 ms 15 ms 7 ms 223.28.2.1
5 8 ms 8 ms 8 ms Bundle-Ether1-br-01-mciwg.ni.time.net.my [223.28.26.82]
6 8 ms 11 ms 8 ms he.sgix.sg [103.16.102.81]
7 40 ms 40 ms 46 ms 10ge1-16.core1.hkg1.he.net [184.105.223.189]
8 194 ms 193 ms 198 ms 100ge8-2.core1.lax2.he.net [184.105.64.125]
9 202 ms 202 ms 202 ms 100ge8-2.core1.pao1.he.net [184.105.81.237]
10 205 ms 215 ms 208 ms 10ge4-1.core1.sjc1.he.net [72.52.92.114]
11 224 ms 226 ms 224 ms vocus.gigabitethernet2-13.core1.sjc1.he.net [64.71.184.46]
12 232 ms 231 ms 232 ms bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.24]
13 228 ms 228 ms 228 ms ten-0-5-0-0.cor01.syd04.nsw.VOCUS.net.au [114.31.199.37]
14 230 ms 228 ms 228 ms ten-2-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.77]
15 228 ms 228 ms 228 ms as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
16 228 ms 228 ms 228 ms 27.111.251.106
17 * * * Request timed out.
18 228 ms 228 ms 228 ms 103.4.115.37
IMHO, this is really a big boomerang routing issue.
7 40 ms 40 ms 46 ms 10ge1-16.core1.
8 194 ms 193 ms 198 ms 100ge8-2.core1.
9 202 ms 202 ms 202 ms 100ge8-2.core1.
10 205 ms 215 ms 208 ms 10ge4-1.core1.
11 224 ms 226 ms 224 ms vocus.gigabitethernet2-13.core1.
12 232 ms 231 ms 232 ms bundle-153.cor02.
13 228 ms 228 ms 228 ms ten-0-5-0-0.cor01.syd04.
The packet reached SG then go to HKG then go over Pacific to LA then Palo Alto then San Jose (the whole Silicon Valley) and then go over Pacific (again) reaching New South Wales (Australia).
yeapch01 and jjj2 should help escalate this routing issue for you.