Thank you for taking the time to reach out to the ISP and getting back to us. We appreciate the effort in trying to help us.
However, and respectfully I do not think they are correct. To me, this looks like a templated reply for shifting blame.
Like some have mentioned in this thread earlier, using a VPN or a different ISP seems to resolve the connectivity issue. While we are not going to endorse any VPN services we would recommend you should use one if you can.
We regret that you are facing this inconvenience but we would do everything on our part to resolve this if we could identify the root cause.
To the best of our knowledge, there is nothing specific on our end that we do once we open the doors to the internet - that is we do not filter traffic in any way.
Off the top of my head, this connectivity issue looks like some sort of a DNS leak problem to me. We have had ISPs in Pakistan & India accidentally block some of our FQDNs in the past.
For instance: ISPs often claim to be transparent proxies with the reason of “enhancing” your browsing experience. You know - So that you can access your social media and streaming services fast !
However, for a million reasons beyond our control, this approach can do more harm than good for your browsing experience (i.e. in general and not just visiting freeCodeCamp)
Anyways to drive this argument home, by using a VPN OR probably even a public resolver like https://1.1.1.1/dns/ or https://developers.google.com/speed/public-dns you may be able to resolve the connectivity issue.
You should also consider some “DNS over HTTPS” - (Google this if you are interested, I do not want to endorse anyone) service if a VPN or a Public DNS resolver based solution does not work for your ISP.
And,
If you ever need to check if one of our services is down, you should subscribe to updates here:
We are truly sorry about your experience, we hope we can be of help.
Thanks & happy coding.