I can see it.

I am able to see the site from home, and I am a Comcast customer.

works for me.

Comcast customer in Cambridge MA, torrentfreak works fine for me

Worked for this Comcast user.

Works for me -- Comcast customer in rural Virginia.

You might want to correct the text to say "torrentfreak.com" without the "s", although the hotlink is correct. (obviously).

i can see it too from my comcast connection

Comcast customer, northeastern MA. The link works for me.

I'm on comcast, yep can see it.

Will the MPAA and RIAA now be following my every move?

See it in Albuquerque, NM on Comcast.

Central Connecticut, good to go.

Got it!

Looks good in Washington DC.

Comcast here. I can see it in Washington DC. But lately, LimeWire has stopped working on both my desktop and laptop machines. I haven't yet tried to install a newer version on either one, however.

This is Crystal Palace, are you still on?

I can see it

I can also see it.

I'm on Comcast and the page loads fine.

northern NJ comcast user and I can see it

Yup I can also see it. South Jersey & I have comcast.

yes, can see it. comcast in minnesota.

good in nashville

Santa Clara, CA on Comcast can see everything just fine.

All good in Chicago.

Comcast subscriber in Revere, Ma and I could see it fine.

Good in Philly

Good in Tacoma, WA.

Gottit. Comcastic!

D'oh! San Jose. Comcast. Got it.

Successful Comcast connect in San Jose. BUT over the past 3 days, I've noticed that UpLaod speeds have dropped from +400K down to < 40K.

Works for me, Jacksonville, FL

c-76-106-244-155.hsd1.fl.comcast.net

Ok. It must just be me then. I could access it with a proxy server but not my Comcast internet connection. After a few comments I called Comcast and am now locked in a death battle for them to fix the problem. They are randomly blocking certain sites. Though I have figured out a way to work around that with a proxy server configuration for now...

@tedyc03:

Is Comcast blocking the IP address of the the website, or is it their DNS server that is blocking it? If it is the DNS server, there are public ones you can use rather than the ones provided by your ISP.

@ShadowFalls: When I ping the websites, the DNS server returns an IP address, but I can't connect to it. Still, changing the DNS server sounds like a good idea. Got any ideas?

When it comes to Comcast, never assume it's malice when it could just be incompetence.

I once had a hell of a time convincing them they had a problem when I couldn't get to ANY 64.*.*.* addresses. My comcast IP was in the range of 64.*.*.* and a traceroute clearly showed they weren't routing it outside their own network (it went into a loop until it hit TTL)

I called them and tried to explain but soon as I would say anything that included the word "router" I would get the same canned response "Sir, we don't support the use of routers." NOT MINE, YOURS! Then I'd get an explanation what a router is and that they don't use them, they are in customer's homes.

Arrgggh.... I then had to deal with a tech coming out to my house to check my connection even though I knew he wouldn't find anything.

Took them weeks to get it fixed. I ended up having to get one of my staff that had a part-time job there convinced it was their fault, and then have him contact an engineer within the company to get it fixed using his internal connections.

Update: found some DNS servers; no dice. Comcast won't even connect to the IP address of these websites.

Works for me in Florida

My ISP in the UK was (maybe still is, but I left them a few weeks ago) periodically blocking the uTorrent user-agent and the BitTorrent protocol itself by dropping responses.

Try setting the Firefox user-agent to uTorrent/1610 and browsing any web site whenever you suspect blocking. In the case of blocking, the web server logs the request, but the web servers second response (after the tcp connection request) never reaches me.

I scripted it on Windows with Task Scheduler like this:

date /t >> e:\btcheck\log.txt
time /t >> e:\btcheck\log.txt
wget -nv --spider -t 1 --no-http-keep-alive -U uTorrent [www.google.com] 2>> log.txt

I then ran an UltraEdit macro with this command line:
f:\ultraedit\uedit32.exe /M,E="f:\ultraedit\btchecker.MAC"

The .mac file has some binary in it, so I can't post it. Besides, it can probably be done better with bash shell scripting.

Works fine in Atlanta.

Fine in York, PA.

Then again, I use OpenDNS.

Fine in Central CT.