If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

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.

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!

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:

Originally Posted by BMWCCA

As I said in a previous post today, Comcast says there's no way it can be them if it's only one site. If they do limit an individual's speed or access to the web from abuse of bandwidth, it limits all sites. That's not the issue here. It can't be Firefox, either, since when it happens I can switch to Safari with the same lack of response.

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.

I know my life would look alright if I could see it on the Silver Screen

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!

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-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 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_.

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.

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.

You might try connectingcolorado.com (use the quicksearch) and ancientmoney.org to see if those are slow at the same time as you observe that AH is slow.