Yeah, I'm in san diego and with cox network it's a no go. Other networks work just fine so far. Anyone else in San Diego with cox getting a white page of death from torrentcrazy.com?

where are you located?

this site loads with default COX DNS
»imgur.com/1gv6A

quality torrents though.....

Or torrentcrazy.com is blocking Cox, some or all of their IP blocks. Meanwhile I'm seeing the exact same thing (page won't load) using Clearwire. I think it is on TC's end.

Not sure what you mean by that, but COX has it's own discrete DNS servers. L3 has anycasted DNS servers all over america in a few of their larger peering points/datacenters.

No, that hasn't been ruled out since I can connect to torrentcrazy.com through my verizon 4g connection, I can connect to it from my work computer, I can connect to it through my at&t 4g connection and most other wireless connections outside of cox. As a matter of fact, I just did a brand new install of windows 7 on this computer that I'm typing on right now and I can't access it through cox either. There is nothing loaded on this machine except for internet explorer. At this point, I have to assume that cox is either blocking it or rerouting it into a black hole somewhere.

H:\>tracert torrentcrazy.com Tracing route to torrentcrazy.com [94.185.82.42]over a maximum of 30 hops:   1	 torrentcrazy.comServer:  ns1.ri.cox.netAddress:  68.9.16.30 Non-authoritative answer:Name:	torrentcrazy.comAddress:  94.185.82.42 > torrentcrazy.comServer:  ip68-105-28-16.at.at.cox.netAddress:  68.105.28.16 Non-authoritative answer:Name:	torrentcrazy.comAddress:  94.185.82.42 > torrentcrazy.comServer:  google-public-dns-a.google.comAddress:  8.8.8.8 Non-authoritative answer:Name:	torrentcrazy.comAddress:  94.185.82.42 

I think we have ruled out that Cox is blocking torrent sites. Those are just flaky sites that go up and down on a whim.

and Cox's DNS servers are sourced from Level 3 (anycast address of 4.2.2.1, guessing mine resides in Arizona, so it may be different elsewhere.)

HTTP/1.1 400 Bad RequestDate: Mon, 12 Nov 2012 01:23:18 GMTServer: Apache/2.2.3 (CentOS)Content-Length: 311Connection: closeContent-Type: text/html; charset=iso-8859-1                                                               400 Bad Request                                                                                                          Bad Request                                                                                                                             <p>Your brows sent a request that this server could not understand.                                                            </p>                                                                <hr>                                                                    Apache/2.2.3 (CentOS) Server at www.torrentcrazy.com Port 80 Connection to host lost. 

I really don't think Cox is doing IP level blocking of anything (in fact, I haven't heard of any domestic consumer facing ISPs that do any kind of IP level blocking of public addresses.)

I don't think they are doing DNS blocking of anything either, though they DO have flaky DNS servers (I remember one time they had an entire day where DNS servers were down due to a routing loop, and routing loops are usually a pretty easy thing to find and fix; shouldn't take a whole day.)

There are even times when I have tried to reach a subdomain which at certain times of the day, Cox's DNS servers can't resolve, whereas other DNS servers can. Interestingly, Level 3's DNS servers can't resolve them either, and Cox's DNS servers are sourced from Level 3 (anycast address of 4.2.2.1, guessing mine resides in Arizona, so it may be different elsewhere.)

What you might be running into is DNS poisoning. It's possible that your gateway device (router as most people call it, though it's actually multiple devices in one) has an internal DNS server that has a poisoned cache, or even a poisoned hosts file.

Or worse, it's possible that your client machine has a poisoned hosts file.

Highly unlikely and pretty much nearly impossible. When you check these sites "work" how are you doing it? Same computer connected to another ISP, or some other computer on another ISP? You may want to check the computers host file/table. I can't imagine malware would blackhole specific torrent sites, but that is the next most likely scenario if alternative DNS doesn't work.

Okay, i tried opendns and google dns and I still can't access those sites. I can access them elsewhere, but not here. How do I go about to see if cox is blocking my ip specifically?

Okay, i tried opendns and google dns and I still can't access those sites. I can access them elsewhere, but not here. How do I go about to see if cox is blocking my ip specifically?

Okay, i tried opendns and google dns and I still can't access those sites. I can access them elsewhere, but not here. How do I go about to see if cox is blocking my ip specifically?

both sites are responding to me on Google DNS and Cox DNS.

torrent sites are always going up/down. try a different DNS provider, we might not have the updated DNS after the server was moved.(which they do very often)