|
Try this, if you're running Windows. Open up an MSDOS window and type "tracert ytmag.com" (In UNIX, it's "traceroute ytmag.com".) traceroute will give you something that looks like this: traceroute to ytmag.com (64.85.72.115), 30 hops max, 38 byte packets 1 pm003-pontiac.bignet.net (198.108.19.4) 145.562 ms 139.054 ms 139.391 ms 2 bordercore1-ethernet4-0.mich.com (198.108.19.1) 139.085 ms 129.300 ms 129.409 ms 3 port105.net100.bignet.net (206.67.100.105) 139.012 ms 139.035 ms 139.309 ms 4 bignet-t3-gw.Alter.net (137.39.146.1) 139.062 ms 140.689 ms 137.872 ms 5 122.at-2-0-0.XR2.CHI4.ALTER.NET (146.188.208.206) 152.707 ms 149.168 ms 153.669 ms 6 0.so-3-0-0.TR4.CHI4.ALTER.NET (152.63.15.238) 156.137 ms 149.261 ms 149.311 ms 7 106.at-6-1-0.TR2.POR3.ALTER.NET (146.188.141.230) 218.980 ms 219.085 ms 219.569 ms 8 196.ATM7-0.XR2.SEA1.ALTER.NET (152.63.105.17) 218.787 ms 219.267 ms 219.399 ms 9 194.ATM7-0.GW6.SEA1.ALTER.NET (146.188.201.77) 219.059 ms 219.259 ms 219.414 ms 10 exodus-sea1-oc3.customer.ALTER.NET (157.130.12.186) 219.082 ms 220.158 ms 218.500 ms 11 dcr02-g2-0.tkwl01.exodus.net (216.34.64.162) 219.041 ms 219.055 ms 219.230 ms 12 csr12-ve240.tkwl01.exodus.net (216.34.64.35) 217.765 ms 219.310 ms 219.599 ms 13 64.85.71.174 (64.85.71.174) 226.726 ms 218.938 ms 219.504 ms 14 64.85.72.115 (64.85.72.115) 217.918 ms 219.818 ms 229.832 ms This tells you the route from you to ytmag. Any bottlenecks will show up as a big difference between two hops. In my case, it's the first hop between me and my ISP, which is about 140 milliseconds. The total time to get to ytmag is the last line in the report, which is about 220 milliseconds. If you see a single line that has numbers way bigger than the previous line, there's a bottleneck there and you have a legitimate complaint with your ISP. Run this test at different times over several days, then send all the reports to your ISP. If they don't try to fix it, then switch ISPs. If any hop
|