Quote:
Originally posted by Turboface
Thanks guys for the help so far. As I suspected, my host is leaking traffic, and has been for some time now.
I went to a DNS specific help forum and this is what the admin from there said:
traceroute stalls out, no ping, no answer on port 80.
If this has been ongoing, it may be best to look for a new host.
3 dsl-gw-216-220-114-1.dsl.bway.net (216.220.114.1) 19.198 ms 17.406 ms 17.353 ms
4 ge-8-0-113.ipcolo1.newyork1.level3.net (63.209.170.225) 19.699 ms 17.12 ms 83.486 m
*s
5 ge-3-0-0-53.gar1.newyork1.level3.net (4.68.97.66) 50.385 ms 17.598 ms 18.009 ms
6 4.78.172.10 (4.78.172.10) 19.396 ms 19.743 ms 38.906 ms
7 ds0.nyc1.webair.net (209.200.31.3) 21.82 ms 22.247 ms 19.016 ms
8 * * *
9 * * *
10 * * *
11 * * *
^C
(*) WARNING 1 long line(s) split
|
Well, this is not completelly correct. Traffic loss could happen on many hops, it's not because you time out for example on the 15th hop that the 15th hop is the cause of this. I don't want to get to technical but you can time out on any hop if the previous 1 to 6 hops are failing although those previous ones gave a correct reply. Could be for example a router of an ISP that times out once ina while causing a host that is 4 hops or even more after that ISP to be unreachable.
If i got the ip of the hosts FIRST inside hop i can do a 24 hour test to see it's availability from 6 different servers, it's a simple but effective test. I can send you the reports after the test.