For comparison im getting no loss except for pinging to one router along the way
Tracing route to 185.149.90.50 over a maximum of 30 hops
...
16 136 ms 136 ms 135 ms xe-0-0-0-100-55s-cr1.any2ix-coresite.as45177.net [206.72.210.17]
17 145 ms 137 ms 138 ms as49544.any2-la.coresite.com [206.72.211.4]
18 276 ms 276 ms 276 ms 10ge.dfwr0-laxr0.vwdal01.dfw.i3d.net [109.200.218.192]
19 277 ms 276 ms 276 ms 10ge.iadr0-dfwr0.csva01.iad.i3d.net [109.200.218.188]
20 * * 276 ms 10ge.lr0-iadr0.th-n.lhr.i3d.net [109.200.218.149] <<<Lossy
21 276 ms 276 ms 277 ms 30ge.cr1-lr0.smartdc.rtm.i3d.net [109.200.218.173]
22 300 ms 299 ms 300 ms 0 [5.200.30.163]
23 299 ms 299 ms 299 ms 185.149.88.26
24 298 ms 302 ms 298 ms 185.149.90.50
Trace complete.
Otherwise its pretty good with no loss at the far end.
Packet loss will cause your tcp packets to be retransmitted, slowing down the total throughput speed due to the tcp congestion control mechanisms. The acknowledgements may not get back and also be lost further contributing to retransmissions at various points along the path, further slowing down the sending of packets from the source end.

