A traceroute is not checking either port 80 or 443, which is why I offered the tcptraceroute suggestion. I also have a remote server which doesn't properly completely traceroutes, so that doesn't surprise me in the least.
If you do a valid test and still stop at 220.127.116.11, you can let us know. But, that's not our equipment, so if there's actually some sort of block there it's likely automated and due to your server doing bad stuff, so you'd also want to look into what it's really doing.
On Friday, March 30, 2012 5:39:53 AM UTC-4, Mark van der Sanden wrote: