Or, just do a traceroute ('tracert' in Windows) to the destination. Here are my results. The first tracert is through PacBell 1.5Mbit DSL service and the second is through Earthlink modem dial-up. As you can see there are more than one route to
http://www.dpreview.com . The bottleneck for me appears to be somewhere through Sprint when using my super fast DSL connection.
Through PacBell DSL.
Tracing route to
http://www.dpreview.com [209.207.162.7]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 35 ms 33 ms 33 ms adsl-216-101-212-254.dsl.lsan03.pacbell.net [216
.101.212.254]
3 21 ms 22 ms 22 ms core5-vlan50.lsan03.pbi.net [216.102.176.193]
4 20 ms 23 ms 23 ms edge1-ge1-0.lsan03.pbi.net [206.13.29.144]
5 21 ms 22 ms 22 ms lang1sr3-so-5-2-0-0.ca.us.prserv.net [165.87.157
.206]
6 21 ms 22 ms 23 ms 165.87.157.189
7 23 ms 23 ms 22 ms sl-bb11-ana-2-2.sprintlink.net [144.232.1.21]
8 30 ms 29 ms 30 ms sl-bb11-sj-4-0.sprintlink.net [144.232.18.81]
9 33 ms 32 ms 30 ms sl-bb10-sj-9-0.sprintlink.net [144.232.3.25]
10 148 ms 153 ms 141 ms sl-bb12-rly-5-0.sprintlink.net [144.232.9.217]
11 114 ms 114 ms 115 ms sl-bb11-rly-8-0.sprintlink.net [144.232.7.213]
12 109 ms 230 ms 261 ms sl-bb5-dc-4-0-0.sprintlink.net [144.232.7.166]
13 90 ms 88 ms 88 ms 208.28.7.19
14 101 ms 95 ms 95 ms sl-csg-1-0-0-T3.sprintlink.net [144.228.108.94]
15 96 ms 96 ms 94 ms fe0000.ed1.wdc.dn.net [209.207.190.38]
16 94 ms 97 ms 95 ms
http://www.dpreview.com [209.207.162.7]
Through Earthlink modem dial-up.
Tracing route to
http://www.dpreview.com [209.207.162.7]
over a maximum of 30 hops:
1 * * * Request timed out.
2 98 ms 102 ms 103 ms f8-0-0-ar01-pas.neteng.itd.earthlink.net [207.21
7.148.1]
3 99 ms 114 ms 122 ms vlan232-cr04-pas.neteng.itd.earthlink.net [207.2
17.2.37]
4 100 ms 117 ms 114 ms f4-1-0-br03-pas.neteng.itd.earthlink.net [207.21
7.1.3]
5 * * * Request timed out.
6 98 ms 99 ms 101 ms 166.ATM3-0.XR1.LAX4.ALTER.NET [152.63.113.98]
7 112 ms 105 ms 112 ms 293.ATM2-0.TR1.LAX2.ALTER.NET [146.188.248.250]
8 163 ms 165 ms 164 ms 111.ATM7-0.TR1.DCA8.ALTER.NET [146.188.138.145]
9 163 ms 166 ms 165 ms 197.ATM6-0.XR1.TCO1.ALTER.NET [152.63.32.189]
10 171 ms 190 ms 177 ms 193.ATM9-0-0.GW3.DCA3.ALTER.NET [152.63.32.65]
11 183 ms 179 ms 182 ms dn4-gw.customer.ALTER.NET [157.130.15.230]
12 189 ms 182 ms 235 ms fe0500.ed1.wdc.dn.net [209.207.190.58]
13 188 ms 196 ms 194 ms
http://www.dpreview.com [209.207.162.7]
Here's a freeware program that will tell you where the trouble may be.
http://www.nessoft.com/pingplotter/files.html
For those who know how the Internet works you'll have no trouble using it.
Ike
Hi Phil:
There is a variable associated with your site affecting many of us; this
"slow/fast" issue does not make sense. As the time of this post, it took
about 30 seconds to get a hit on the News Discussion Forum. I am on the
equivalent of a T1 line. Normally, BANG - I'm ON, but not today. I had
the same problem a couple of times yesterday. Every once in a while, you
have to wait more than two minutes. The problem does not appear to be a
function of the "time of day".
Just thought you would like to know; hope this is of some help to you.
Sincerely,
Joe Kurkjian