![]() Packet loss is almost always bad when it occurs at the final destination. Tracing across an ocean, or through a satellite link, or some other link where the distance is further will certainly impact the expected latency more. This means that a DSL modem on the west coast of the United States, tracing to a server on the east coast of the United States should expect somewhere around 120 ms (depending on the route and a number of other factors, but this is a rough ballpark) - 25 ms for the DSL modem and 100 ms for the distance. ![]() Normally, it's more like 75 after the data zig-zags around a bit and goes through numerous routers. With traceroute, we have to send the data there and back again, so roughly 1 ms of latency is added for every 60 miles (96km, although with the level of accuracy we're using here, we should say '100km') of distance between you and the target.Ĭonnecting to a web site across 1500 miles (2400 km) of distance is going to add at least 25 ms to the latency. Data travels at (very roughly) 120,000 miles (or 192,000 kilometers) per second, or 120 miles (192 km) per ms (millisecond) over a network connection. For a cellular link, this can be from 200 to 600 ms. For a dial-up modem, this is normally anywhere from 100 to 220ms. ![]() For a cable modem, this can normally be between 5 and 40 ms. There are two normal factors that significantly influence the latency of a consumer device (like a cable modem, Green / yellow / red at the upper right corner) in PingPlotter and MultiPing frames a basic reference to what a good or bad latency might be, although it's not specific for connection type or distance to What's a 'normal' latency (or good range) that I can expect to see?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |