Comcast blocking gambling websites?

I haven't been able to reach sportsbetting.com for the past day. I went to work and tried it on one of their computers and it worked just fine. I got home and completed a tracert to the sportsbetting.com webserver and this is what I got:

Tracing route to www.sportsbetting.com [213.219.21.74]
over a maximum of 30 hops:

1 10 ms 10 ms 11 ms 10.140.192.1
2 16 ms 13 ms 25 ms 12.244.84.145
3 14 ms 36 ms 14 ms 12.244.64.234
4 15 ms 17 ms 16 ms 12.244.72.46
5 19 ms 19 ms 27 ms gbr1-p80.st6wa.ip.att.net [12.123.203.182]
6 17 ms 29 ms 16 ms tbr1-p012501.st6wa.ip.att.net [12.122.12.157]
7 32 ms 32 ms 32 ms tbr2-cl1.sffca.ip.att.net [12.122.12.113]
8 32 ms 32 ms 30 ms ggr1-p370.sffca.ip.att.net [12.123.13.69]
9 37 ms 36 ms 45 ms nr1-p350.paix.ip.att.net [12.123.221.2]
10 att-gw.chi.uu.net [192.205.32.14] reports: Destination net unreachable.

It appears as if comcast is doing something at their gateway to block off request. Anyone else with comcast experiencing this?

DNS, not blocking. I don't think providers have rights to block any sites where customers wants to use (If it' not criminal things)

I had same situation with Intertops about two years ago. It worked well at work, but at home I couldn't log in. First I contacted Intertops and asked if other Finnish customers had reported this failure. They said no and told no any changes of their systems.

Then I phoned to my servive provider and told to a lady that I can't log into a one internet site and I asked have they done anything to their systems. She said no and then asked what kind of site is it.

"Well, it's one sportsbetting site, I don't know have you heard about it, Intertops", I said

"Yes, I know Intertops", she replied

I had to admit, I was quite surprised about her reply. The problem continued for a while, but then disappeared.

No, no no no no no.......

It has nothing to do with Comcast blocking anything.

comcast is cox, right???
I use cox and I cannot access it either. My neighbor uses aol and he can access it

It's probably a DNS issue....

I can't get to it from UUnet or Sprint networks.

In this case it doesnt seem to be a dns issue, the trace shows the right ip

the last hop in the trace seems to be the guilty one, may be uunet was having some problem at that particular moment?

So who should I contact to get this problem resolved