If you were actually experiencing packet losses the 37% "loss" visible @ 22.214.171.124 would propagate downwards. It doesn't and the only loss that should interest you is the one next to 126.96.36.199, which is 1 packet in total aka virtually no packet loss.
"When analyzing MTR output, you are looking for two things: loss and latency. If you see a percentage of loss at any particular hop, that may be an indication that there is a problem with that particular router. However, it is common practice among some service providers to rate limit the ICMP traffic that MTR uses. This can give the illusion of packet loss when there is in fact no loss. To determine if the loss you’re seeing is real or due to rate limiting, take a look at the subsequent hop. If that hop shows a loss of 0.0%, then you are likely seeing ICMP rate limiting and not actual loss:"
That's what the ISP I work for does in his backbone infrastructure and clients quite often send us similar complaints, which are unjustified, because all the packets go through without any problems, but internal routers have more important tasks than reacting to ICMP queries.
Were you actually lagging harder than usual on the server/experienced visible packet losses?