You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Latency and Ping Tests
- Thread starter listedguru
- Start date
MadH:
In thinking about this - Some routers and firewalls turn off the ping reply feature to hide the system or for other technical reasons. Since you say you have 100% packet loss on your first link I suspect that to be what you are seeing. I'm not a Comcast user so don't know how you are set up with them or how your PC firewall works.
I use the paid version of PingPlotter and don't remember whether the free version offers a "don't display the first link" option. If it does you could turn it off. The latency should show as 1 millisecond, the lowest reportable value.
However, the way PingP works is that once it determines the route it pings each router in the chain individually. Since PingP sends the pings to each router sequentially, you'll sometimes see a higher ping time in the middle of your route than the end-to-end ping time.
If there was truly a 100% packet loss anywhere in the path you would not be able to get beyond that point. So if you do see 100% packet loss and you see a response beyond that point just assume that the ping response feature has been disabled.
Jack
In thinking about this - Some routers and firewalls turn off the ping reply feature to hide the system or for other technical reasons. Since you say you have 100% packet loss on your first link I suspect that to be what you are seeing. I'm not a Comcast user so don't know how you are set up with them or how your PC firewall works.
I use the paid version of PingPlotter and don't remember whether the free version offers a "don't display the first link" option. If it does you could turn it off. The latency should show as 1 millisecond, the lowest reportable value.
However, the way PingP works is that once it determines the route it pings each router in the chain individually. Since PingP sends the pings to each router sequentially, you'll sometimes see a higher ping time in the middle of your route than the end-to-end ping time.
If there was truly a 100% packet loss anywhere in the path you would not be able to get beyond that point. So if you do see 100% packet loss and you see a response beyond that point just assume that the ping response feature has been disabled.
Jack
Madhatter, what JackR said is right about that first hop.
Looking at the screenshot of your tracert I don't see anything wrong - 30 to 50ms of latency is normal and there are no large jumps indicating a bottleneck.
If you have occasional problems then leave pingplotter running continuously (ping every 15-30 seconds) in the background and then you can build up some historical data to figure out where the problem is when you perceive slowness, e.g. figure which hop is causing the latency.
Looking at the screenshot of your tracert I don't see anything wrong - 30 to 50ms of latency is normal and there are no large jumps indicating a bottleneck.
If you have occasional problems then leave pingplotter running continuously (ping every 15-30 seconds) in the background and then you can build up some historical data to figure out where the problem is when you perceive slowness, e.g. figure which hop is causing the latency.
Quote from JackR:
If there was truly a 100% packet loss anywhere in the path you would not be able to get beyond that point. So if you do see 100% packet loss and you see a response beyond that point just assume that the ping response feature has been disabled.
Jack
Thanks again to both of you for taking the time. Much appreciated.
What does it mean when I run a trace route and it never says it reaches it's destination? It goes about 13 hops or so and then the rest are just time outs. Is that an issue or not?
If anyone else here is trading on anvil could you post a traceroute to their server?
-Guru
If anyone else here is trading on anvil could you post a traceroute to their server?
-Guru
It could mean that there is a router (or firewall) that is not only ignoring ICMP packets (ping) but its also blocking them. Post the destination here for confirmation.Quote from listedguru:
What does it mean when I run a trace route and it never says it reaches it's destination? It goes about 13 hops or so and then the rest are just time outs. Is that an issue or not?
If anyone else here is trading on anvil could you post a traceroute to their server?
Quote from Madhatter:
No biggie? Or is there something I need to fix?
I have no idea what you are complaining about.
I would KILL to have trace-route latency measurements in the mid-30's!
But then again, I am on the West Coast and some ways away from my quote server and as a result, have to battle a lot of internet "congestion" which is not under anyone's control.
I'm getting 130 Avg. pinging TS at 63.99.207.119, obviously it finishes with 100% packet loss which I presume is due the server not confirming the packets for obvious reasons, being the TS data server.
Could others please confirm what their Avg pings are on the same IP 63.99.207.119.
thanks
Could others please confirm what their Avg pings are on the same IP 63.99.207.119.
thanks