Johnny17
@verizon.net
| Can't access katz.cd
Hey just four days ago I was accessing Katz fine but in the past 2 or 3 days the site is inaccessible. I can view it fine through a proxy so I'm wondering what the issue can possibly be. I read that verizon is blacklisting and banning some popular warez sites but don't know if it's true or not. Can anyone help? |
|
darcilicious
Cyber Librarian
Premium
join:2001-01-02
Forest Grove, OR
 ·Verizon FIOS
 ·Comcast
| Go here »whatismyip.com/ and post the first two sets of digits of your IP address. It's possible you're on an IP block that is still listed in various site's (not Vz) bogon filters.
»/nsearch?q=bog···61269586
P.S. I can reach that site fine and no, Vz doesn't block any sites that anyone has reported here. |
|
Johnny17
@verizon.net | reply to Johnny17
The first two digit of my IP address is 96.239. |
|
JohnA
Premium
join:2003-09-16
Pittsburgh, PA
| reply to Johnny17
I'm on a 98.111. right now, on Verizon DNS. Won't load or trace.
Tracing route to katz.cd [93.190.143.123]
over a maximum of 30 hops:
1 8 ms 1 ms 1 ms 192.168.1.1
2 4 ms 4 ms 4 ms 10.7.30.153
3 93.190.143.123 reports: Destination host unreachable. |
|
Smith6612
Premium
join:2008-02-01
united state
 ·Dish Network
 ·Verizon Online DSL
·FrontierNet Intern..
| reply to Johnny17
I was able to trace the site's domain fully on my Verizon DSL, however the end result goes to a site called Sedoparking (which is a Domain Parker) at a server I believe located in Germany. The site doesn't load however, so I'm assuming whatever happened to it, their domain expired or they shut down. As to why it can be reached on a proxy, who knows. I'm using OpenDNS by the way.
--
"All your base are belong to me!" |
|
birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI | reply to Johnny17
Unable to reach from 96.233 IP. Tracert similar to JohnA.
They've gone dark or they've gone blocked. Google cache makes it look like a warez site. Maybe they've been taken down, as opposed to gone down. |
|
tvmatt
@verizon.net
| reply to Johnny17
Looks like Verizon has no route to katz.cd's ISP on any of their block (see all of their IPs at »fixedorbit.com/cgi-bin/cgirange.···SN=15435 ). Not sure why that would be, though. |
|
sheepy
@verizon.net | reply to Johnny17
works if you use a proxy but not straight through the verizon dns. Seems to be the northeast region of verizon's network that has blocked the site. |
|
barje
join:2002-06-24
Park Ridge, NJ | reply to Johnny17
How can I use a proxy. Any suggestions. |
|
Smith6612
Premium
join:2008-02-01
united state
1 edit | You can try one of these proxies below. Of course there are better ones than the ones I listed below.
www.proxify.com
www.hidemyass.com
--
"All your base are belong to me!" |
|
STrRedWolf
join:2006-06-18
Severn, MD | reply to Johnny17
I'm getting similar problems and much slowness myself. Anyone seeing this? |
|
Frank
is chilling
Premium
join:2000-11-03
somewhere
·Verizon FIOS
| reply to Johnny17
i'm on a 74.105.*.* ip..... it looks like it's being blocked as the traceroute dies before even attempting to get out of verizon's network (dies @ first hop in vz's network).
you may want to go to the verizon direct forum to see if they can help.
--
At first I thought everyone on the highway was drunk but then I realized I was driving in Florida  |
|
birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
·Verizon FIOS
| reply to Johnny17
Access to katz.cd is now open on a 96.233 address block. What's curious is that I had been having problems with remote access from one 96.233.x address to another (home to work). I was looking at the port forwards on the router, but still couldn't connect.
So I decided to get FiOS TSR involved last night, and magically it was suddenly working. Then, this morning katz.cd is also working.
Coincidence? Maybe, but I think there was a router somewhere that just wasn't making the connection. |
|
JohnA
Premium
join:2003-09-16
Pittsburgh, PA |
Yesterday it worked with a proxy. Today it loads right up. Still in the same IP block. |
|
Johnny17
@verizon.net | reply to Johnny17
It's loading up today, I'm still on the same IP block. |
|
