I have a problem with my internet connection and my ISP is unwilling (or perhaps unable) to resolve it. The connection is wireless broadband. According to the CPE (at 172.16.1.1) it is a Mikrotik V4.5. Since I do not have a log in password, I can not provide any further information about the CPE.

Several weeks ago I noticed that I could no longer access the website http://www.blacklistednews.com from any computer on my home network. If I use my laptop in another location (a friends house, a public network, etc.) I can access the website.

If I ping http://www.blacklistednews.com (204.27.61.74) from any computer on my network, I get 100% packet loss.

I have not noticed if any other websites are blocked.

I have contacted my ISP several times regarding this issue and they have responded by asking me questions such as "is your computer turned on?" and "are you connected to the internet?"

At one point they informed me that they connected to my CPE (from their office) and could not see any problems, therefore the problem must be with the network settings on my computer.

Does anyone know what could be causing this, or how to resolve it?

This doesn't look like a website that an ISP would block. You can try accessing the site through a free proxy or a VPN service (ex: http://usaip.eu) to verify if it is a local problem. If you can access it, then probably your ISP is blocking it and you will be in a better position to ask for an explanation. If you still have problems through the VPN or proxy, then it is possibly a local problem.

GL

Thanks GL

I am able to access the site using a free proxy service.

I still suspect the problem is with the CPE. Since my previous post I have found several more addresses which appear to be blocked.
Ping:
204.27.61.74 (100% loss)
204.27.61.75 (100% loss)
204.27.61.76 (100% loss)
204.27.61.77 (100% loss)
204.27.61.78 (100% loss)
204.27.61.79 (100% loss)
*these all return normal pings from outside of my network.

Its all good as long as I can access using a proxy. I am just disappointed with my ISP's lack of support.

Thanks again.

you can always try to reset the CPE unit and cause their technician to come to your house, probably he will be more qualified to answer your questions

I like the idea normis suggested. But while you wait for the tech to show up, try a traceroute to see where the connection is being stopped. ADD: You shouldn't need to reset the CPE. Unplug it just before you call tech support. If it doesn't answer their connection request, they will probably send a technician.

Several months before this issue began, I had to unplug the CPE after installing a new UPS. It reestablished the connection right after powering it back up. I will try it again later today to see if it helps.

I just ran traceroute and the results are different than they were two weeks ago.

Previous traceroute results:
traceroute to 204.27.61.74 (204.27.61.74), 30 hops max, 40 byte packets
1 172.16.1.252 (172.16.1.252) 3000.831 ms !H 2998.072 ms !H 2997.885 ms !H

*172.16.1.252 is the internet IP address of my router, which is connected to the Mikrotik CPE gateway (at 172.16.1.1)

Current traceroute results:
traceroute to 204.27.61.74 (204.27.61.74), 30 hops max, 40 byte packets
1 172.16.1.1 (172.16.1.1) 1.581 ms 0.881 ms 0.827 ms
2 70-36-175-129.dynamic.sonic.net (70.36.175.129) 5.555 ms 2.451 ms 8.677 ms
3 208-106-117-217.static.sonic.net (208.106.117.217) 3.240 ms 4.188 ms 5.229 ms
4 3.ge-2-1-0.gw2.sr.sonic.net (64.142.117.37) 21.032 ms 4.938 ms 6.408 ms
5 0.ge-6-1-6.gw3.equinix-sj.sonic.net (64.142.0.206) 14.119 ms 8.784 ms 12.548 ms
6 10gigabitethernet2-3.core1.sjc2.he.net (206.223.116.37) 10.418 ms 14.811 ms 19.082 ms
7 10gigabitethernet3-3.core1.den1.he.net (184.105.213.106) 36.198 ms 36.900 ms 60.877 ms
8 10gigabitethernet1-2.core1.mci1.he.net (72.52.92.5) 52.530 ms 54.309 ms 49.221 ms
9 10gigabitethernet1-1.core1.mci2.he.net (184.105.213.2) 52.347 ms 51.325 ms 49.104 ms
10 joe_s-data-center-llc.10gigabitethernet1-4.core1.mci1.he.net (216.66.79.14) 103.236 ms 66.602 ms 56.449 ms
11 SW1.KCMODATACENTER.COM (96.43.134.62) 80.807 ms 136.862 ms 54.156 ms
12 * * * Request timed out.

It is using a different gateway now. Two weeks ago it was trying 172.16.1.252 for non-local addresses. Now it is using 172.16.1.1. That new one sounds correct to me.

However, I will guess that the new challenge is out of your ISP's control. That timeout looks way down the list somewhere.

ADD: Here is mine. I cut out the stuff that was different. Start reading yours at line 7. Some of these ips appear to be the same subnets. (add: line 12 below is the same ip as your line 11)

6 184.105.213.109 45ms 47ms 49ms
7 72.52.92.85 58ms 54ms 54ms
8 72.52.92.178 71ms 72ms 73ms
9 72.52.92.2 87ms 79ms 85ms
10 184.105.213.2 89ms 85ms 83ms
11 216.66.79.14 114ms 106ms 109ms
12 96.43.134.62 81ms 82ms 84ms
13 204.27.61.74 79ms 113ms 80ms