ISP blocking nzb site? ***FIXED***

[blackangst1]

Hey all. So, theres an NZB site Ive used for years, and now cant get there. Theyve had a major re-structure, server upgrade, etc and was down for a few weeks, but theyre back up. Same URL. Now I cant get there.

Here's the relevant info: on Century Link fiber using Level 3 for DNS (4.2.2.1, 4.2.2.2). The errors I receive are (on firefox) Firefox can't establish a connection to the server at www.(nzbsite). On IE I get page cant be displayed.

I also cant get there via my cell provider (TMobile).

The interesting thing? I can get there through TOR.

Any ideas?

 

[ch33zw1z]

Try different DNS, run a traceroute and post the results.

 

[Mushkins]

ISPs dont typically block sites like that unless it's by government order, which is extremely rare, and if they do they redirect you to a takedown notice splashpage. It opens them up to legal ramifications for not doing it proactively for other "bad stuff" on the internet. As long as they stay neutral, they (currently) stay legally safe.

Sounds more like this NZB site went the way of so many other similar sites. Down for "maintenance and upgrades" indefinitely and then they never come back.

 

[vshah]

can you get there if you punch in the ip address directly? eliminate DNS issues first.

 

[blackangst1]

ISPs dont typically block sites like that unless it's by government order, which is extremely rare, and if they do they redirect you to a takedown notice splashpage. It opens them up to legal ramifications for not doing it proactively for other "bad stuff" on the internet. As long as they stay neutral, they (currently) stay legally safe.

Sounds more like this NZB site went the way of so many other similar sites. Down for "maintenance and upgrades" indefinitely and then they never come back.

No. Many others are reporting its fine, and as I said, if I go through TOR, I get there just fine.

can you get there if you punch in the ip address directly? eliminate DNS issues first.

Nope same results.

Try different DNS, run a traceroute and post the results.

Now, this is interesting. Looks its its dying at MY hardware? But it IS resolving. As I said Im using 4.2.2.2/.1, but changed to Google 8.8.8.8 with same results:

Tracing route to nzbgrabit.sx [188.95.54.29]
over a maximum of 30 hops:

1 General failure.

Trace complete.


What the heck is going on? *I* havent made ANY changes in months (yah I know...everything works until it doesnt lol)

edit: I turned off my firewall, got same trace results. In my router, I have no firewall turned on. Since the trace is failing before my gateway something wonky is happening in my path. No idea what to look for though. I know this is the case since when tracing to yahoo my first hop is my gateway:

Tracing route to ds-any-fp3-real.wa1.b.yahoo.com [206.190.36.105]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 192.168.0.1

First hop is my router, second hop is my ISP router.

 

[blackangst1]

****FIXED***

It appears Malwarebytes was b;acklisting the website (ggrrr). I disabled "Enable malicious website blocking" and I can get there now. Thanks guy-