As mtr starts, it investigates the network connection between the host mtr runs on and certain HOSTNAME by sending packets with purposly low TTLs. It continues to send packets with low TTL, noting the response time of the intervening routers. This allows mtr to print the response percentage and response times of the internet route to HOSTNAME. A sudden increase in packetloss or response time is often an indication of a bad (or simply overloaded) link.
I found this utility very useful during troubleshooting packet loss issues. MTR helps to determine source of the problem much easier and fast. At the next screen you can see the results of mtr google.com -n command executed at my home laptop.
Please note that packetloss to intermediary router 184.108.40.206 is higher that to final destination 220.127.116.11.