Quote:
|
Originally Posted by EvilFubAr
Ok... Seems like we spent more time in this thread than it would take to call your ISP hehe  I still think they blocked us, or they are pointing to the wrong place. Guess we will never know.
Id still REALLY like to see your true trace route. Its the most important part of this whole issue.
http://centralops.net/co/DomainDossier.aspx prints out a nice trace. |
Using the link you have provided yielded this result:
hop rtt rtt rtt ip address fully qualified domain name
1 0 0 0 63.134.215.1
2 0 0 0 216.197.122.81 dr-ded1-ge-1-6.crystaltech.com
3 0 0 0 216.197.122.65 cr-edge1-ge-5-0.crystaltech.com
4 0 0 0 67.131.24.221 phv-edge-01.inet.qwest.net
5 1 1 1 205.171.129.85 tmp-core-01.inet.qwest.net
6 11 11 11 67.14.10.6 bur-core-01.inet.qwest.net
7 11 11 11 205.171.213.106 lap-brdr-01.inet.qwest.net
8 12 12 12 208.174.196.13 bpr4-so-6-3-0.losangelesequinix.savvis.net
9 12 12 12 208.174.196.70 dcr2-so-4-2-0.losangeles.savvis.net
10 12 12 12 208.172.44.130 bpr1-ae1.losangeles.savvis.net
11 19 18 19 208.173.57.74
12 38 38 37 63.216.14.90 ge3-2.br01.sea01.pccwbtn.net
13 37 37 37 63.216.14.70 g4-0-1000m.br4.sea.accretive-networks.net
14 38 37 39 207.246.155.129 v5-1000m.core0.sea.accretive-networks.net
15 37 37 38 216.127.42.58
The end. El fin. As you said I have wasted too much time on this already. Have a nice day