The path from our server to any public host: each router, its network and the delay.
Every connection crosses a chain of routers run by different companies. When a site is slow, unreachable from one country, or drops partway, the useful question is where along that chain things go wrong, and whose network it is.
Enter a public host name or address. The trace lists each router on the way from our server in Hyderabad to the target, the time to reach it, its reverse DNS name where it has one and the network that announces its address. Routers inside our hosting provider's private network are shown as a single line without their addresses.
The probe is a small UDP packet to a high port, which many firewalls drop even when the website is fine. An unfinished trace is a reason to look, not proof of an outage. Check the port with the Open Port Checker.
They are inside our hosting provider's private network. Their addresses say nothing about the path to your host, so they are collapsed into one line.
No. It shows the route from our server in India to the target. Your own route may differ, but the last few hops, near the target, are usually shared.
Large networks spread traffic over several equivalent paths and change them as load shifts.
No. Only public hosts are traced, and names that point to private addresses are refused.