dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
764
share rss forum feed


omghi2u

@charter.com

Charter blocking nzb.su?

Have been unable to access this website for the last few days, but confirmed working by others and other charter users has said they cant access this website. My cell phone can access site, and tether to my laptop would allow it. Pretty sure its a charter thing.

it is up according to web test
»www.isup.me/nzb.su

tracert nzb.su

Tracing route to nzb.su [209.208.8.190]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.

siech0

join:2001-03-20
Warrensburg, MO
works for me


charteruser

@charter.com
reply to omghi2u
I have the same issue and i'm on Charter in Long Beach. Seems others are having issues too, any ideas on how to get around it?

»www.reddit.com/r/usenet/comments···on_open/

speedxdesign

join:2010-02-25
Alexandria, MN
reply to omghi2u
Works for me on Charter in MN.


lineofsight

join:2003-01-03
East Saint Louis, IL
reply to omghi2u
Here is a cut and paste of what I get:

It's just you. »nzb.su is up.
Check another site?

Web Hosting built for designers & developers -> Special Offer

It is up when I go there direct.


88615298
Premium
join:2004-07-28
West Tenness
reply to omghi2u
works for me


SOB

@ingtonhospital.com
reply to lineofsight
I am experiencing the same issue with Charter in Pasadena. The domain name and IP both appear to be blocked. I have switched DNSs as well, with no result.


Dogg
Premium
join:2003-06-11
Belleville, IL
Reviews:
·Charter
reply to omghi2u
Very doubtful, and if they are, it's likely not on purpose. Charter has never blocked access to any site/service that I'm aware of.

Your trace route isn't even hitting the Charter network. You would hit at least one router before anything would be blocked.
--
Google is your Friend


omghi2u

@charter.com
reply to omghi2u
Update, it appears to be fixed and working now. Charter tech probably finally notice the problem and fixed it. I am located in the san gabriel valley area, and like the two person above with issues, we all are located in the SoCal region. Seems the problem was a local node issue that only we experienced.