Quote:
Originally Posted by blind-eddie
Is anyone else on the (USA)east cost,mid-west having similar issues connecting to sites out west?
|
My results look similar, but I haven't really noticed any problems accessing sites in general:
Code:
Tracing route to vbulletin.org [98.158.195.239]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 * * * Request timed out.
3 7 ms 7 ms 7 ms te-8-4-ur02.dover.nh.boston.comcast.net [68.85.185.97]
4 7 ms 7 ms 7 ms te-9-3-ur01.portsmouth.nh.boston.comcast.net [68.87.145.98]
5 11 ms 10 ms 11 ms be-59-ar01.woburn.ma.boston.comcast.net [68.85.69.53]
6 15 ms 11 ms 12 ms pos-3-0-0-0-ar01.needham.ma.boston.comcast.net [68.87.146.14]
7 18 ms 19 ms 20 ms pos-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.65]
8 17 ms 15 ms 15 ms xe-11-3-0.edge1.NewYork2.Level3.net [4.71.186.5]
9 16 ms 15 ms 16 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
10 15 ms 15 ms 16 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
11 85 ms 84 ms 85 ms 4.69.135.185
12 92 ms 92 ms 92 ms ae-2-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
13 94 ms 99 ms 99 ms ae-93-93.csw4.LosAngeles1.Level3.net [4.69.137.46]
14 92 ms 92 ms 92 ms ae-41-90.car1.LosAngeles1.Level3.net [4.69.144.195]
15 107 ms 107 ms 107 ms INTERNET-BR.car1.LosAngeles1.Level3.net [4.59.56.162]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 ^C
(I assume the string of "Request timed out" at the end isn't what you're talking about, because I believe that just means it's hit a point where tracert packets aren't passed through).
One problem I have been having (with vbulletin.org only) for the past couple of weeks or so: Sometimes I'll load a page and it will hang, and if I hit reload it doesn't help, but if I stop the page loading then hit reload, it loads right away.