As per: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-September/010798.html
FCC guidelines however should prevent this ( https://www.fcc.gov/openinternet )I have been struggling to get port 8333 open all year, I gave up and was using blockchain for months despite a strong desire to stay on Bitcoin Core, but now the issue has reached critical mass since I'm using the python Bitcoin server module. I have literally spent my entire day trying to open 8333, I thoroughly made sure it was open on the router and computer and it's still closed. Strangely enough I got it open for 30 seconds once today but something closed it immediately.
After hours of phone calls and messaging AT&T finally told me the truth of what was going on, and only because I noticed it myself and demanded an answer. The internet is being routed through a DVR/cable box, and they confirmed the DVR also has a firewall. To make this even more absurd they refused to turn the firewall off because it is their equipment. So effectively they can firewall any port they want even if the customer asks them not to, in the unlikely event the customer figures it out.
Perhaps this is the driving force behind the inexplicable and massive decline in Bitcoin nodes. Bitcoin is being censored by the ISPs themselves, and they won't even tell you that. I had to get in touch with headquarters and threaten to rip it out of the wall to get a proper answer.
What other things are generally blocked besides inbound port 80 and 25 traffic? I wonder if we'll see more bitcoin related stuff trying to be blocked at the ISP level as well or not. I'm not too privy to bitcoin setups and requirements but this does appear to be a pretty clear overreach.broadband providers may not block access to legal content, applications, services, or non-harmful devices.
These rules will protect consumers no matter how they access the Internet, whether on a desktop computer or a mobile device.
Last edited by a moderator: