said by exseven:
As the trace gets to host91-33.dh-c.net.br in all cases i would say the issue is between them and reclameaqui.com.br or a firewall at reclameaqui that is blocking a/multiple subnets. Contact them and ask for a reverse trace back to your home IP, and to verify their firewalls and with their hoster (dh-c.net). The packet leaves the cogeco network and makes it almost all the way to the end system then stops...
17ÃÂ host91-33.dh-c.net.br (126.96.36.199)ÃÂ 205.412 msÃÂ 206.180 msÃÂ 204.102 ms
18ÃÂ * * *
19ÃÂ reclameaqui.com.br (188.8.131.52) [open]ÃÂ 203.962 msÃÂ 205.996 ms *
How, then, would you explain the fact that Cogeco subscribers in Cornwall (see above) and at least one location can access the site? Surely the end points in Brazil would not be different for different Cogeco clients?
There is no point in contacting dh-c.net. Brazilian companies are notoriously bad at responding to consumer issues. I will receive no reply.
Edit to add info:
I just tried an experiment. I am now accessing the site through a VPN server in Montreal. The site can be reached. However, the tracert seems to be the same as with cogeco--final hop unreachable and the same second-last hop. I also did a trace on my ipad through virgin mobile--I get the site, but trace shows final destination unceachable and the same second last hop. This suggests to me that the final destination cannot be pinged or tracerted, and that does not necessarily mean it is broken. Many routers and providers block pings and tracerts ( ICMP packets).