[Mike Irwin]

Just for grins and giggles I've been running some tracerts when the THR is responding slowly as well as quickly.

It doesn't seem to matter, my tracert request hits the 10th hop and then does nothing but "request time out" up to the maximum.

Is anyone else running tracerts? What are they saying?

[BryanP]

That's exactly what I get as well.

As I mentioned in the other thread, if I click and don't get a response within a couple of seconds then I know it will just time out. If I click again it's about a 50/50 chance it will suddenly respond quickly. I've had to click up to 3 or 4 times on a link sometimes before I get a response. Here's what I get on a tracert -

tracert thehighroad.org

Tracing route to thehighroad.org [66.80.73.51] over a maximum of 30 hops:

1 10 ms 9 ms 10 ms 10.179.72.1
2 14 ms 23 ms 10 ms 172.30.50.209
3 11 ms 30 ms 12 ms 172.30.50.250
4 11 ms 13 ms 31 ms 172.30.51.174
5 13 ms 24 ms 14 ms 172.30.50.186
6 15 ms 13 ms 14 ms 68.52.0.50
7 18 ms 20 ms 20 ms so-1-1-0.gar1.atl1.Level3.net [67.72.8.33]
8 21 ms 19 ms 19 ms so-0-3-0.bbr1.Atlanta1.level3.net [209.247.9.157]
9 42 ms 20 ms 20 ms gigabitethernet10-0.hsipaccess2.Atlanta1.Level3.
net [64.159.1.254]
10 * * * Request timed out.
11 * * * Request timed out.

<repeat for 30 hops>

Trace complete.

[Gewehr98]

And I even turned my router's internal firewall into a DMZ to clear the path. Think I'll fire up NeoTrace Pro and drill down a smidgen. ;)

[Derek Zeanah]

I don't know that my firewall is gonna respond to ICMP echo's -- it was turned off for a while, but I can't remember if I turned it on for diagnosis or not...

Regardless, my ISP wasn't respond to pings within their network; something about the latest worm mess was causing a lot of ping traffic. It looks like they've reversed that policy, though.

Here's the way it looks from this end, for anyone interested:


[root@wellbuiltnetworks root]# traceroute www.google.com
traceroute to www.google.com (216.239.37.99), 30 hops max, 38 byte packets
1 ip-66-80-73-49.iad.megapath.net (66.80.73.49) 3.700 ms 2.608 ms 3.982 ms
2 ip-64-32-192-1.dsl.iad.megapath.net (64.32.192.1) 36.333 ms 33.255 ms 35.462 ms
3 ve004.bbsr1.iad.megapath.net (66.80.129.1) 32.527 ms 38.085 ms 39.180 ms
4 gigabitethernet4-1-110.ipcolo2.washington1.level3.net (166.90.148.1) 34.165 ms 38.109 ms 33.305 ms
5 ae0-55.bbr1.washington1.level3.net (64.159.18.129) 35.558 ms 44.509 ms 34.916 ms
6 so-6-0-0.edge1.washington1.level3.net (209.244.11.10) 37.125 ms 34.064 ms 36.292 ms
7 bpr1-ge-5-2-0.virginiaequinix.cw.net (208.173.52.73) 49.839 ms 49.181 ms *
8 bhr1-pos-0-0.sterling1dc2.cw.net (208.173.52.38) 57.680 ms 53.178 ms 50.506 ms
9 csr11-ve240.Sterling1dc2.cw.net (216.33.98.146) 164.246 ms 50.657 ms 50.576 ms
10 209.225.34.218 (209.225.34.218) 48.696 ms 42.815 ms 51.172 ms
11 216.239.48.94 (216.239.48.94) 43.741 ms 51.111 ms 49.728 ms
12 * * *
13 *
[root@wellbuiltnetworks root]# traceroute cnn.com
traceroute: Warning: cnn.com has multiple addresses; using 64.236.24.12
traceroute to cnn.com (64.236.24.12), 30 hops max, 38 byte packets
1 ip-66-80-73-49.iad.megapath.net (66.80.73.49) 4.118 ms 5.298 ms 3.994 ms
2 ip-64-32-192-1.dsl.iad.megapath.net (64.32.192.1) 36.287 ms 35.269 ms 52.893 ms
3 ve004.bbsr1.iad.megapath.net (66.80.129.1) 50.980 ms * 33.587 ms
4 ve025.bbsr1.atl.megapath.net (66.80.133.106) 64.617 ms 51.636 ms 58.130 ms
5 gigabitethernet5-0-116.hsipaccess2.atlanta1.level3.net (63.210.68.229) 54.312 ms * 46.268 ms
6 ge-6-1-1.bbr1.atlanta1.level3.net (64.159.3.13) 48.951 ms * 62.662 ms
7 pos8-0.hsa1.atlanta1.level3.net (209.247.9.166) 59.797 ms 47.833 ms *
8 pop2-atm-p0-2.atdn.net (66.185.138.33) 48.483 ms 48.139 ms 48.010 ms
9 * bb1-atm-p0-1.atdn.net (66.185.147.208) 54.760 ms 47.253 ms
10 * pop1-atl-p4-0.atdn.net (66.185.136.17) 53.623 ms 46.979 ms
11 * * *
12 * * *
13 * * *
14 *

[Standing Wolf]

...if I click and don't get a response within a couple of seconds then I know it will just time out. If I click again it's about a 50/50 chance it will suddenly respond quickly. I've had to click up to 3 or 4 times on a link sometimes before I get a response.

I've found the same thing. My I.S.P. (intermittent service provider) is one of the worst in terms of both speed and reliability, but this site seems to be the slowest and least dependable of the sites I visit regularly. Why does this have to happen to one of my favorite sites?