Perform an IP trace with
mtr, an advanced
traceroute tool that uses multiple ICMP pings to test the connectivity to each hop across the Internet.
What is Traceroute?
Traceroute is a network testing term that is used to examine the hops that communication will follow across an IP network. It also is commonly referred to by the name of the tools used to perform the trace; typically traceroute on Linux based systems and
tracert on Windows operating systems. There are also variations on these such as tcptraceroute. The tools all perform a similar function but have different capabilities or methods for performing the trace.
Why would I run a Traceroute?
A popular reason one might perform a
traceroute is for interest sake. It is a good way to see the path your network connection is taking as it traverses the globe. However, the most common reason is its use by networking and computer professionals to diagnose problems in a network path. As the
traceroute can pin point routers with high response times, possibly indicating network congestion or other problems.
What techniques are used to measure the IP Path?
Packets are sent across the network and something called a TTL (time to live) is measured, as the packets reach hops (router) in the network the TTL is incremented. The packets are usually ICMP or UDP packets; another version uses the TCP protocol. One advantage of using the different protocols is on some networks a router or firewall may block the packets, thereby giving you an incomplete path across the network. By using different protocols you may be able to get past some of the systems that are blocking the other types of packets. TCP Traceroute is popular as it can be used to trace a path to a TCP service that has to have an open port for that service to be operational. For example a web server on port 80 or a mail server on port 25.
GeoIP Location Finding of a network path
We have an online traceroute tool hosted at traceroute-online.com where we include a map of the IP trace as it traverses the world. This is done by looking up each responding router's IP address against GeoIP based services. These services are not always reliable; therefore always take the mapping data with a grain of salt and beware of strange results that bounce back and forth.
Host Name / IP Address
Responding hops are resolved in DNS, if the have a PTR record this is included in the table, those with no record will show the IP Address.
Packet Loss and Response Times
As is pretty obvious these are the results from the
traceroute. The packet loss can show if packets are being dropped either along the path or at the router and the response time shows the latency.
API access to MTR Traceroute
All of our IP Tools have an easy to use API that allows access to remote Traceroute by requesting a URL and receiving the results back in a simple text based output. Access the API using
curl a browser or even
netcat if that floats your boat. 🙂
Access to the MTR Traceroute API
As with all the API calls access is completely free, however you are limited to a total of 50 queries per day from a single IP address.