This is the output that I get every so often when trying to do a traceroute to the web server whenever it's inaccessible:
traceroute to 64.40.98.181 (64.40.98.181), 30 hops max, 40 byte packets
1 207.97.207.194 (207.97.207.194) 2.625 ms 2.840 ms 2.968 ms
2 core1-5.iad1.rackspace.com (69.20.2.18) 0.290 ms 0.356 ms 0.849 ms
3 vlan901.edge3.iad1.rackspace.com (69.20.1.3) 0.845 ms 0.848 ms 1.091 ms
4 bbr1.iad1.rackspace.net (69.20.2.193) 0.817 ms 1.052 ms 1.049 ms
5 rt0as-equinix.vx.shawcable.net (206.223.115.20) 1.053 ms 1.172 ms 1.168 ms
6 rc2as-ge2-0-0.vx.shawcable.net (66.163.64.2) 1.014 ms 0.590 ms 0.624 ms
7 rc1nr-pos0-8-0-0.wp.shawcable.net (66.163.77.93) 52.483 ms 52.480 ms 52.469 ms
8 rc2so-pos0-8-5-0.cg.shawcable.net (66.163.76.193) 69.078 ms 69.061 ms 69.065 ms
9 rc2wh-pos0-15-5-0.vc.shawcable.net (66.163.76.186) 82.930 ms 82.912 ms 82.917 ms
10 ra2wh-tge2-1.vc.shawcable.net (66.163.69.186) 154.364 ms 154.584 ms 154.582 ms
11 rx0wh-net-nation.vc.bigpipeinc.com (64.251.87.170) 80.240 ms 80.221 ms 80.402 ms
12 64.40.105.25 (64.40.105.25) 80.454 ms 80.628 ms 80.816 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * hostwaydcs.com (64.40.103.106) 78.438 ms 78.419 ms
Could anyone offer an explanation why hops 13-17 are timing out yet hop 18 shows up? And Hop 18 isn't even the destination IP? Thanks!
To keep the forums high quality for all users, please take the time to format your posts correctly.
First of all, use Code Tags when you post any code or data samples so others can easily read your code. You can easily do this by highlighting your code and then clicking on the # in the editing menu. (You can also type code tags
```text
and
```
by hand.)
Second, avoid adding color or different fonts and font size to your posts. Selective use of color to highlight a single word or phrase can be useful at times, but using color, in general, makes the forums harder to read, especially bright colors like red.
Third, be careful when you cut-and-paste, edit any odd characters and make sure all links are working property.
13-17 are probably hosts that do not answer ICMP echo requests or send ICMP TTL timeouts.
Host 18 is probably a host with multiple interfaces, all connected to the same router, and it answers through whatever interface that's first available.
Thanks pludi.
So I pretty much get a traceroute like this whenever the site w/ IP 64.40.98.181 is inaccessible (seems to happen once every few weeks or so). If the site is working fine, I get a normal traceroute.
Can any conclusions be drawn from this traceroute to pinpoint what could be causing the sporadic outages?
Not really. traceroute isn't really for endpoint checking, but rather testing the network between two nodes.
Meaning: you can check whether the host at the other end is the problem or if a component in between fails.
Sorry, not to belabor the point but here's the traceroute output for the same IP when the site is up (note that I'm doing the traceroute from a different location but the last couple of hops is my concern here):
Here, the device at 64.40.105.25 routes to the final destination correctly. Whereas, in the first traceroute i posted, it goes through 5 hosts that don't respond to pings then ends up at a host w/ a different IP. Does this mean 64.40.105.25 is the problem?