In a perfect world, data would move over the Internet in real time. There would be no delays whatsoever between when one computer sends data out over the network and when it reaches the recipient.
In the real world, however, there is always some level of delay when exchanging data over the network. That delay is measured in terms of network latency.
Ideally, network latency is so low that no one notices it. But when latency increases – even if only to fractions of a second – it can dramatically impede the quality of your network and the services that depend on it.
Keep reading for a look at how network latency works, why monitoring latency is important, and how to track latency across all segments of your network.
Network latency is a measure of delays in data movement across a network.
Again, although we often imagine that networks can move data in real time, in actuality there is always a delay because it takes some time for packets (the units of information used to transfer data over a network) to travel across the network.
On a healthy network, those delays can be measured in milliseconds, which are one one-thousandth of a second. Network latency rates below 100 milliseconds are typically considered to be good, and those of 50 milliseconds are considered very good. At those levels, the delays in transferring data across the network are virtually imperceptible to humans, and applications designed to operate in near-real time (such as autonomous vehicles) can do so effectively.
But when your network encounters problems, latency rates can spike. You might start seeing delays of several hundred milliseconds or (in instances of truly high latency) several seconds. Data still gets through, but the delays become so high that some applications cease to meet acceptable levels of performance.
Importantly, latency is only one of several factors that can impact network performance. Bandwidth limitations, which refer to the volume of data your network is capable of transmitting, are another common challenge. So is packet loss, which is the failure of packets to reach their intended destination. Thus, if your network is not performing as expected, you should assess whether the problem is high latency or another issue. In some cases, it could be a combination of multiple problems.
There are a number of reasons why latency rates can become high. Common causes of high latency include:
Some of these problems originate from local network equipment or resources that are owned and managed by your business. Others affect your ISP's network. And some latency problems could originate either locally or on your ISP's end.
High latency rates will always negatively impact applications and services, but the extent to which latency issues cause severe problems depends on how high the latency is and how much latency you can tolerate for a given application or use case.
For example, a Web application may still deliver an acceptable user experience even if latency rates reach several seconds. Having to wait several seconds for Web content to load is inconvenient, but the website would still be usable under those circumstances.
On the other hand, a self-driving car that needs to send and receive data from external servers continuously in order to navigate may crash (literally) if latency rates exceed several hundred milliseconds. The car needs to determine very quickly where to turn or how to avoid an obstacle, and delays as short as just a couple hundred milliseconds may cause it to fail to do that.
Thus, while your goal should always be to minimize latency to the extent possible, it's important to take context into account when determining how much latency is acceptable to your business.
The simplest way to track network latency is to use basic Linux command-line utilities. Key tools include:
These tools are useful if you want to gather basic data about latency and determine whether a latency issue is impacting the performance of your network.
However, if you need to troubleshoot a latency problem and determine exactly where and why it's occurring, you'll typically need more sophisticated tools than ping and traceroute. You'll want tools that can compare latency rates on both your Local Area Network (LAN) and the Wide Area Network (WAN) so that you can determine whether the latency issue is specific to your local network configuration or related to a larger network problem.
In the former case, you'll know that the issue most likely results from the way your local routers, load balancers, or other networking equipment and services are configured. On the other hand, if it's a WAN-level problem, the issue may be on your ISP's end.
High network latency is always a bad thing. But just how bad it is depends on which latency rates your applications, services, and use cases require. Likewise, there are many possible causes of high latency, and getting to the root of latency problems requires the ability to collect as much context as possible about the state of all segments of the networks you depend on.
All of the above means that to manage network latency, context is key. The more information you have at your disposal about what's impacting latency and whether latency issues are undercutting your business needs, the more capable you are of preventing latency problems from becoming the weakest link in your user experience.