How to read a traceroute.
How can i distinguish how many routers and how many ISPs exist in a traceroute??
1 <1 ms <1 ms <1 ms 192.168.1.1 2 3 ms 2 ms 2 ms ip-216-54-0-119.coxfiber.net [216.54.0.119] 3 827 ms 925 ms 830 ms 100gigabitethernet7-1.core1.nyc4.he.net [184.105.223.166] 4 8 ms 7 ms 8 ms as54641.xe-9-0-1.ar1.iad1.us.nlayer.net [69.31.31.42] 5 8 ms 9 ms 9 ms ecbiz103.inmotionhosting.com [69.174.52.11]We can see that our first hop is under 1ms and is going to our local router of 192.168.1.1. The 2nd hop is still very low at around 3ms max, and is our Internet service provider that actually gives our office an Internet connection. The 3rd hop is another router that must be gone through before hitting our East Coast data center for a particular website hosted there. We can see that it's taking close to a full second to respond at around 900ms. Based off that router's hostname 100gigabitethernet7-1.core1.nyc4.he.net, I can guess that this router is in New York from the nyc4 in its hostname. In this case I did the trace route test from our Virginia Beach office, to a server in our Washington, D.C. data center which geographically is pretty close. But first the connection is going up past DC to a router in New York possibly due to temporary network saturation or maintenance issue. Then our 4th and 5th hops are back to normal low ping times, ending up on one of our shared servers in the East Coast data center. So in this case we could see the problem wouldn't be with either our Local internet connection, or with InMotion's data center or server, but rather the networking path my local computer tried to take to end up there. If your first few packets have high ping times, or are timing out, that would be an indication of your local router setup, or possibly your ISP having issues. If the last hop or 2 have these problems, then it could be something temporary from our side of the network, and so that's how you pin-point which it might be. I hope that made sense and was helpful, please let us know if you had any other questions! - Jacob
Hi can anyone tell me where the problem lies?
[1]
Tracing route to 155.133.233.98 over a maximum of 30 hops
1 2 ms 2 ms 2 ms 192.168.1.1
2 9 ms 5 ms 6 ms 10.10.206.230
3 * * * Request timed out.
4 539 ms 628 ms 672 ms mail.triconinfra.in [182.73.250.153]
5 363 ms 351 ms 434 ms 116.119.57.56
6 576 ms 557 ms 541 ms aes-static-010.137.144.59.airtel.in [59.144.137.10]
7 590 ms 558 ms 488 ms 192.168.163.3
8 557 ms 484 ms 415 ms 155.133.233.98
Trace complete.
[2]
Tracing route to 155.133.233.99 over a maximum of 30 hops
1 10 ms 25 ms 8 ms 192.168.1.1
2 7 ms 8 ms 5 ms 10.10.206.230
3 21 ms * * 10.10.206.229
4 468 ms 554 ms 544 ms mail.triconinfra.in [182.73.250.153]
5 598 ms 568 ms 546 ms 116.119.50.254
6 354 ms 315 ms 409 ms aes-static-010.137.144.59.airtel.in [59.144.137.10]
7 665 ms 572 ms 434 ms 192.168.163.3
8 400 ms 365 ms 296 ms 155.133.233.99
Trace complete.
[4]
ping 10.10.206.230 -t
Pinging 10.10.206.230 with 32 bytes of data:
Reply from 10.10.206.230: bytes=32 time=5ms TTL=63
Reply from 10.10.206.230: bytes=32 time=5ms TTL=63
Reply from 10.10.206.230: bytes=32 time=17ms TTL=63
Reply from 10.10.206.230: bytes=32 time=10ms TTL=63
Reply from 10.10.206.230: bytes=32 time=5ms TTL=63
Reply from 10.10.206.230: bytes=32 time=5ms TTL=63
Ping statistics for 10.10.206.230:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 17ms, Average = 7ms
[5] pinging 4th hop
ping 182.73.250.153 -t
Pinging 182.73.250.153 with 32 bytes of data:
Reply from 182.73.250.153: bytes=32 time=658ms TTL=61
Reply from 182.73.250.153: bytes=32 time=676ms TTL=61
Reply from 182.73.250.153: bytes=32 time=675ms TTL=61
Reply from 182.73.250.153: bytes=32 time=563ms TTL=61
Ping statistics for 182.73.250.153:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 563ms, Maximum = 676ms, Average = 643ms