InTrace performs a traceroute from an Android device and presents the result both as a list and on a map. Entering a hostname or address returns each hop with its address, resolved name, round trip time, and an inferred location.
The list is the accurate part and the map is the interpretive one. Each hop is measured with several probes and reported individually, which is the same information any traceroute produces, and the addition here is that the resolved names and geographic lookups are performed automatically rather than requiring a second tool. That saves real time when the question is which provider a path traverses, because the transition between networks is usually visible in the hostnames long before it appears anywhere else. The mapping is where care is needed, since geographic location for an address is derived from registration data that is frequently regional rather than precise, and a hop shown in one city may be equipment several hundred kilometres away registered to an office there. Reading the map as an indication of which networks are involved is sound, and reading it as a physical route is not.
It suits orientation rather than measurement, and the round trip times shown for intermediate hops reflect how quickly that device chose to reply rather than the latency through it. A hop showing higher times than the ones after it is normal and is not a fault.
Link: InTrace on Google Play