I'm on Comcast too , and HAD been having exact same problems as BMWCCA , but no problems for about a week ... speed is fine
XP
firefox
I'm on Comcast too , and HAD been having exact same problems as BMWCCA , but no problems for about a week ... speed is fine
XP
firefox
Some kind of happiness is measured out in miles
The site was running super hot all day. Now it's bogged down. Took me over a minute just to load one page of this thread. I'm running a traceroute now. I have no idea what it means, or how long to run it.
Edit: but it posted this reply quick enough with no stall.
Traceroute has started ...
traceroute to http://audioheritage.org/vbulletin/ (208.69.32.132), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.423 ms 0.905 ms 1.012 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
Unbelievably slow for the past couple days. Takes forever to load a thread, with one post appearing at a time. Sometimes, hitting reload will break the bottleneck and load the page.
XP and FF 2
Reporting the good with the bad:
Everything is working great right now and the site loads as quickly as any other I've been to today. I can even access the smilie page which I'm sure adds so much more to the forum experience for those who bother to check my posts!
Fingers crossed!
The problem is likely Comcast. You could find a neighbor who doesn't use Comcast and try it there.
Bo had a similar problem over the weekend at home with Comcast, but the site worked fine at his work.
Comcast appears to be limiting bandwidth.
I'm typing "Comcast" way too much!
Last edited by John Nebel; 12-10-2008 at 02:44 PM. Reason: Type comcast a few more times
John Nebel
Yeah, sometimes thats how internet routing works ... a slew of net addresses can be funky through one ISP
But I don't know why you'd expect these two addresses to NOT work the same for you ... they are on the same hosting service ...
Basically that means your path to both of them is the same...
AudioHeritage.org -
Name Server:NS1.CSD.NET
Name Server:NS2.CSD.NET
LansingHeritage.org -
Name Server:NS1.CSD.NET
Name Server:NS2.CSD.NET
2ch: WiiM Pro; Topping E30 II DAC; Oppo, Acurus RL-11, Acurus A200, JBL Dynamics Project - Offline: L212-TwinStack, VonSchweikert VR-4
7: TIVO, Oppo BDP103D, B&K, 2pr UREI 809A, TF600, JBL B460
I don't, but I'm a computer dummie using a Mac!
I will reiterate what Comcast told me when I called and asked if they could possibly be limiting access to specific sites and not others:
BTW, it's been working normally for me all day long. Go figure!Originally Posted by BMWCCA
my "wild ass guess" (tho lots of past experience)
is an issue with Comcasts DNS resolution server ......you mite
get the IP of LHF and key that as a destination rather
than the common name, thusly bypassing Comcast DNS server, or
if on Windoze, you could mod the host file to make a permanent
local DNS lookup. So key "198.80.11.57" in instead of http://www.audioheritage.org
(I was working on my CCNA a couple yesrs back,but forgot most of it)
bottom line...NOT LHF problem.
Some kind of happiness is measured out in miles
I'm not sure that a telephone call to Comcast would yield much information unless they (1) performed actual tests (2) described the tests they performed (3) gave you set of conclusions and the reasoning behind them (4) the tests were independently verified.
Here is the routing from a few well-known networks to AH - this looks reasonable although the AT&T-Sprint NYC peering might be a bit congested.
route-views.oregon-ix.net>traceroute 198.80.11.57
Tracing the route to 198.80.11.57
1 128.223.51.2 [AS 3582] 0 msec 0 msec 0 msec
2 128.223.3.8 [AS 3582] 0 msec 0 msec 0 msec
3 207.98.64.65 [AS 3701] 0 msec 0 msec 4 msec
4 207.98.64.162 [AS 3701] 0 msec 0 msec 0 msec
5 207.98.64.10 [AS 3701] 4 msec 0 msec 4 msec
6 207.98.64.137 [AS 3701] 4 msec 0 msec 4 msec
7 63.211.200.245 [AS 3356] 8 msec 4 msec 4 msec
8 4.68.105.68 [AS 3356] 8 msec 4 msec 8 msec
9 4.68.63.34 [AS 3356] 8 msec 4 msec 8 msec
10 144.232.9.151 [AS 1239] 4 msec 8 msec 8 msec
11 144.232.20.104 [AS 1239] 28 msec 28 msec 24 msec
12 144.232.20.140 [AS 1239] 68 msec 64 msec 64 msec
13 144.232.1.190 [AS 1239] 68 msec 64 msec 64 msec
14 160.81.226.14 [AS 1239] 68 msec 68 msec 72 msec
15 198.80.11.57 [AS 3364] 68 msec 72 msec 72 msec
AT&T Enhanced Network Services #########################
Tracing the route to apollo.csdco.com (198.80.11.57)
1 12.129.193.236 0 msec 0 msec 0 msec
2 mdf001c7613r0002-gig-12-2.lax1.attens.net (12.129.193.253) 0 msec 0 msec 0 msec
3 gar4.la2ca.ip.att.net (12.122.255.69) 0 msec 0 msec 0 msec
4 tbr2.la2ca.ip.att.net (12.123.222.94) [MPLS: Label 30707 Exp 0] 4 msec 0 msec 4 msec
5 cr2.la2ca.ip.att.net (12.122.19.205) [MPLS: Label 16072 Exp 0] 4 msec 0 msec 4 msec
6 ggr3.la2ca.ip.att.net (12.122.129.13) 0 msec 4 msec 0 msec
7 192.205.33.190 4 msec 0 msec 4 msec
8 sl-crs1-sj-0-8-0-2.sprintlink.net (144.232.18.57) 16 msec 16 msec 12 msec
9 sl-crs1-stk-0-0-0-2.sprintlink.net (144.232.20.98) 20 msec 16 msec 16 msec
10 sl-crs1-che-0-0-3-0.sprintlink.net (144.232.20.240) 56 msec 56 msec 56 msec
11 sl-gw11-che-9-0.sprintlink.net (144.232.1.188) 56 msec 56 msec 56 msec
12 sl-csd-10-0.sprintlink.net (160.81.226.14) 60 msec 60 msec 56 msec
13 apollo.csdco.com (198.80.11.57) 56 msec 56 msec 56 msec
-------------- route-server.ip.att.net ---------------
--------- AT&T IP Services Route Monitor -----------
The information available through route-server.ip.att.net is offered
by AT&T's Internet engineering organization to the Internet community.
This router has the global routing table view from each of the above
routers, providing a glimpse to the Internet routing table from the
AT&T network's perspective.
This router maintains eBGP peerings with customer-facing routers
throughout the AT&T IP Services Backbone:
12.123.21.243 Atlanta, GA 12.123.133.124 Austin, TX
12.123.41.250 Cambridge, MA 12.123.5.240 Chicago,IL
12.123.17.244 Dallas, TX 12.123.139.124 Detroit, MI
12.123.37.250 Denver, CO 12.123.134.124 Houston, TX
12.123.29.249 Los Angeles, CA 12.123.1.236 New York, NY
12.123.33.249 Orlando,FL 12.123.137.124 Philadelphia, PA
12.123.142.124 Phoenix, AZ 12.123.145.124 San Diego, CA
12.123.13.241 San Francisco, CA 12.123.25.245 St. Louis, MO
12.123.45.252 Seattle, WA 12.123.9.241 Washington, DC
*** Please Note:
Ping and traceroute delay figures measured with this box are unreliable,
due to the high CPU load this box experiences when complicated "show" commands
are being executed.
For questions about this route-server, send email to: [email protected]
*** route-server.ip.att.net now uses AAA for logins. Login with
username "rviews".
User Access Verification
Username: rviews
route-server>traceroute 198.80.11.57
Type escape sequence to abort.
Tracing the route to apollo.csdco.com (198.80.11.57)
1 white-dwarf.cbbtier3.att.net (12.0.1.1) [AS 7018] 0 msec 0 msec 0 msec
2 ar13.s10-0-0.n54ny.ip.att.net (12.124.182.17) 212 msec 0 msec 200 msec
3 gbr7.n54ny.ip.att.net (12.122.84.162) [MPLS: Label 9609 Exp 0] 200 msec 200 msec 200 msec
4 cr1.n54ny.ip.att.net (12.122.4.134) [MPLS: Label 16366 Exp 0] 200 msec 200 msec 204 msec
5 ggr3.n54ny.ip.att.net (12.122.131.9) 200 msec 200 msec 0 msec
6 sl-bb26-nyc-5-0.sprintlink.net (144.232.8.193) [AS 1239] 200 msec 208 msec 200 msec
7 sl-bb20-nyc-15-0.sprintlink.net (144.232.13.10) [AS 1239] 404 msec 0 msec 200 msec
8 sl-crs2-nyc-0-2-3-0.sprintlink.net (144.232.2.110) [AS 1239] 208 msec 200 msec 204 msec
9 sl-crs2-chi-0-5-0-0.sprintlink.net (144.232.20.162) [AS 1239] 200 msec 200 msec 200 msec
10 sl-crs1-che-0-0-0-0.sprintlink.net (144.232.20.161) [AS 1239] 200 msec 204 msec 200 msec
11 sl-gw11-che-9-0.sprintlink.net (144.232.1.188) [AS 1239] 200 msec 204 msec 204 msec
12 sl-csd-10-0.sprintlink.net (160.81.226.14) [AS 1239] 200 msec 204 msec 200 msec
13 apollo.csdco.com (198.80.11.57) [AS 3364] 200 msec 200 msec 204 msec
####################### route-server.savvis.net #######################
####################### Savvis Route Monitor #######################
208.172.146.29 Santa Clara, CA 208.172.146.30 Santa Clara,CA
This route-server shows the complete view of AS 3561 routes.
This router should be used to see if a route is in Savvis routing tables.
This router sets local-preference, MED, etc. for all routes equally.
This router should also be used to verify reachability from Savvis to other
networks.
This router should _not_ be used to verify Savvis backbone routing policy.
The best path shown is the current best path _from this router_.
For questions about this route server, send email to [email protected]
####################### route-server.savvis.net #######################
route-server.savvis.net>trace 198.80.11.57
Type escape sequence to abort.
Tracing the route to apollo.csdco.com (198.80.11.57)
1 bhr2-pos-11-1.santaclarasc8.savvis.net (209.1.169.178) 0 msec 0 msec 0 msec
2 204.70.200.25 4 msec 4 msec 0 msec
3 pr1-ge-4-0-0.SanJoseEquinix.savvis.net (204.70.200.221) 4 msec 0 msec 0 msec
4 204.70.203.22 0 msec
204.70.203.34 0 msec
204.70.203.22 36 msec
5 bpr2-so-4-0-0.sanjoseequinix.savvis.net (208.175.172.170) 0 msec 4 msec 4 msec
6 0.so-0-1-0.XT2.SCL2.ALTER.NET (152.63.57.102) [AS 701] 0 msec 4 msec 0 msec
7 0.so-7-0-0.XL4.DEN4.ALTER.NET (152.63.89.233) [AS 701] 44 msec 44 msec 40 msec
8 POS7-0.GW4.DEN4.ALTER.NET (152.63.93.205) [AS 701] 40 msec 40 msec 40 msec
9 csd-gw.customer.ALTER.NET (157.130.160.62) [AS 701] 68 msec 68 msec 68 msec
10 apollo.csdco.com (198.80.11.57) [AS 3364] 68 msec 72 msec 68 msec
John Nebel
This is completely random, and makes no difference if I access with IP or domain. It works great for a bit then completely slows to a stop. If a page stops loading, hitting refresh a few times will often cause it to load quickly. Mostly I'm just sitting and staring at the red "Lansing" banner and nothing else, then a thread will slowly load one post at a time. Progress bar always just says: waiting for audioheritage.org.
There are currently 1 users browsing this thread. (0 members and 1 guests)