i can verify that it is cogent that is blocking. here is a traceroute to ezrss.it from my location:
traceroute to ezrss.it (192.121.86.89), 30 hops max, 60 byte packets
1 dir-825 (10.0.1.1) 0.272 ms 0.348 ms 0.421 ms
2 * * *
3 172.31.12.206 (172.31.12.206) 30.399 ms 37.043 ms 42.638 ms
4 ge5-0-0d0.cir1.ashburn-va.us.xo.net (216.156.116.21) 63.265 ms 68.788 ms 75.488 ms
5 206.111.0.230.ptr.us.xo.net (206.111.0.230) 82.640 ms 88.183 ms 95.319 ms
6 te0-1-0-5.mpd21.dca01.atlas.cogentco.com (154.54.29.117) 101.729 ms
te0-0-0-4.mpd21.dca01.atlas.cogentco.com (154.54.24.97) 104.156 ms
te0-3-0-5.mpd21.dca01.atlas.cogentco.com (154.54.5.45) 111.028 ms
7 te0-2-0-6.mpd21.fra03.atlas.cogentco.com (154.54.31.246) 214.052 ms
te0-3-0-6.mpd21.fra03.atlas.cogentco.com (154.54.26.102) 195.210 ms
te0-2-0-6.mpd21.fra03.atlas.cogentco.com (154.54.31.246) 194.521 ms
8 te4-1.ccr02.fra06.atlas.cogentco.com (130.117.50.202) 198.267 ms 183.519 ms 183.211 ms
9 * * *
10 * * *
11 * * *
12 * * *^z
[1]+ stopped traceroute ezrss.it
should have examined my traceroute more carefully... sadly, i can confirm that the route gets lost
somewhere in the cogent network. so they are guilty.
fetching the rss through a web proxy is a first step to work around this problem. but then of course
loading the .torrent-file from torrents.zoink.it fails. am using flexget, has anyone got an idea on
how two solve the second step?
norton safe web has analyzed 94.75.216.31 for safety and security problems. below is a sample of the
threats that were found.
threat report
total threats found: 1
viruses (what's this?)
threats found: 1
here is a complete list:
it seems that 94.75.216.31 (the ip where ezrss is hosted) has been black listed due to the above
risk, although the risk now seems to be removed the blacklisting is still inplace
i doubt that is the issue since that report was from 2009. this is more likely the answer.