Hmm, your machine seems to be having problems:
1 206.117.161.1 (206.117.161.1) 0.564 ms 0.832 ms
2 isi-acg.ln.net (130.152.136.1) 2.411 ms 2.305 ms
3 usc-isi-atm.ln.net (130.152.128.2) 5.33 ms 3.841 ms
4 uscisi-pbi-630375.cust-rtr.pbi.net (209.232.128.189) 4.666 ms 4.352 ms
5 edge1-ge2-0.lsan03.pbi.net (206.13.29.205) 4.132 ms 5.464 ms
6 sl-gw15-ana-6-0.sprintlink.net (144.232.192.61) 4.659 ms 4.973 ms
7 sl-bb21-ana-12-0.sprintlink.net (144.232.1.209) 6.871 ms 6.274 ms
8 pos6-0.core2.LosAngeles1.Level3.net (209.0.227.49) 15.664 ms 17.894 ms
9 so-4-1-0.mp1.LosAngeles1.Level3.net (209.247.10.197) 18.689 ms 18.401 ms
10 so-0-1-0.mp2.Philadelphia1.Level3.net (64.159.0.142) 88.619 ms 88.536 ms
11 gigabitethernet9-1.hsipaccess1.Philadelphia1.Level3.net (64.159.0.154) 87.407 ms 86.442 ms
12 63.209.178.162 (63.209.178.162) 87.674 ms 91.260 ms
13 rif1.phl004bd01.yipes.com (209.50.43.189) 88.784 ms 88.213 ms
14 phl018s101.yipes.com (66.54.144.46) 88.993 ms 90.614 ms
15 66.7.139.82 (66.7.139.82) 90.802 ms 91.817 ms
16 66.54.221-yipes-webreseller.net (66.54.221.131) 89.143 ms 88.211 ms
from samspade.org, type in valuablehost.com for traceroute.
P.S this is quite good, dont forget the train derailed today and cut out uunet cables.
Regards,
ValuableHost
Originally posted by robin
hahahaha. never mind. check out this traceroute from my machine:
traceroute to valuablehost.com (66.54.221.131), 30 hops max, 40 byte packets
1 resnetx-xx-x.resnet.umbc.edu (xx.xx.xx.xx) 1.198 ms 0.744 ms 0.711 ms
2 * * *
3 xxx.umbc.edu (xx.xx.xx.xx) 0.985 ms 0.665 ms 0.882 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 *
and it's just been sitting there for a while. I compared it to a traceroute from alertsite.com and am feeling mollified, if a bit silly, now.