TraceRoute for IP Address

Sorry if this is a silly question but I've researched it and my  findings don't seem to match what this traceroute says. Can someone please analyze this and explain it for me or send me to a site where this can be done. I don't mind paying for this knowledge but I'm unable to figure it out.

Answers

  • Scooby
    Scooby Member Posts: 178
    25 Answers 100 Comments 25 Awesomes 25 Likes
    ✭✭✭
    It appears to be a "normal" trace route to cisco.com. From your screenshot, you are using Windows 10. It may help to run a trace route from Windows, as it may give more info, than your router's trace route. In the "Type here to search" text field, type, without the quotes, "powershell". When found, click on it. After the powershell window opens, at the prompt, type, without the quotes, "tracert cisco.com" and hit the "Enter" key. The results should be similar to your router's/screenshot one, but it may resolve more of the IP Addresses to their host names.

    Hop 1: 69.40.176.3 resolves to h3.176.40.69.dynamic.ip.windstream.net - Believe this is for your local ISP, Windstream Communications, or ISP provided equipment/modem.
    Hop2: 40.128.251.158 resolves to ae3-0.pe08.chr101-nc.us.windstream.net - NC (North Carolina) - traveling from your ISP, through Windstream network.
    Hop 3: 40.128.248.162 resolves to ae13.cr02.chr101-nc.us.windstream.net - NC (North Carolina) - still traveling through Windstream.
    Hop 4: 40.132.59.32 resolves to ae8-0.cr04.atln02.ga.us.windstream.net - GA (Georgia) - still traveling through Windstream.
    Hop 5: 208.120.133.25 resolves to user-387h18p.cable.mindspring.net - still traveling through Windstream. (Mindspring was acquired by Earthlink, who merged with Windstream)
    Hop 6: 64.125.29.36 resolves to ae1.cs1.atl10.us.zip.zayo.com - Believe to have left Windstream, traveling on a Tier 1 IP Network.
    Hop 7: 4.69.208.233 resolves to ae-4-15.edge5.Dallas3.Level3.net - still traveling on a Tier 1 IP Network, but in Dallas, TX.
    Hop 8: 4.69.208.229 resolves to ae-3-5.edge5.Dallas3.Level3.net - still traveling on a Tier 1 IP Network,
    Hop 9: 4.59.34.66 resolves to CISCO-SYSTE.edge5.Dallas3.Level3.net - still traveling on a Tier 1 IP Network.
    Hop 10: 128.107.2.5 doesn't resolve. Belongs to Cisco Systems, via a lookup (Netherlands). Appears to be traveling through Cisco's network.
    Hop 11: 72.163.0.102 doesn't resolve. Belongs to Cisco Systems (California). Still traveling through Cisco's network.
    Hop 12: 72.163.2.202 resolves to rcdn9-bb07-fab1-sw3811-dmzdcc1uplink.cisco.com. Still traveling through Cisco's network.
    Hop 13: 72.163.3.6 resolves to rcdn9-br07-fab1-sw3812-dmzdcc2uplink.cisco.com. Still traveling through Cisco's network.
    Hop 14: N/A (Most likely the request timed out, possibly due to trace route requests being blocked at the firewall).
    Hop 15: N/A (Most likely the request timed out, possibly due to trace route requests being blocked at the firewall).

    What seems strange/interesting is every other hop, the even numbered ones, appear to have high latency, with some of the times. However on most of those, the "Time 2" appear to have good times (lower ms). Not sure what your findings are.

    Here is a link that may help, too: https://archive.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf

  • Pixel
    Pixel Devon, U.K.Member, Moderator, Beta Tester Posts: 394
    100 Likes 25 Answers 100 Comments Second Anniversary
    ✭✭✭✭
    Hi @curmill1107 first why in particular are you specifically checking cisco.com? Being a large specialist networking company there is every likelihood that their servers are doing checks on incoming data packets that a non-networking sites don’t perform so, try another destination unless you have a specific interest in Cisco. I have also run a traceroute against cisco.com and get similar results to yours.