PRTG: All-in-one
bandwidth monitoring

Bandwidth is measured as the amount of data that can be transferred from one point to another within a network in a specific amount of time. Typically, bandwidth is expressed as a bitrate and measured in bits per second (bps).

The term bandwidth refers to the transmission capacity of a connection and is an important factor when determining the quality and speed of a network or the internet connection. 

There are several different ways to measure bandwidth. Some measurements are used to calculate current data flow, while others measure maximum flow, typical flow, or what is considered to be good flow.

Bandwidth is also a key concept in several other technological fields. In signal processing, for example, it is used to describe the difference between the upper and lower frequencies in a transmission such as a radio signal and is typically measured in hertz (Hz).

Bandwidth can be compared to water flowing through a pipe. Bandwidth would be the rate at which water (data) flows through the pipe (connection) under various circumstances. Instead of bits per second, we might measure gallons per minute. The amount of water that possibly can flow through the pipe represents the maximum bandwidth, while the amount of water that is currently flowing through the pipe represents the current bandwidth.

Bandwidth was originally measured in bits per second and expressed as bps. However, today’s networks typically have much higher bandwidth than can be comfortably expressed by using such small units. Now it is common to see higher numbers that are denoted with metric prefixes, such as Mbps, (megabits per second), Gbps (gigabits per second), or Tbps (terabits per second).

K = kilo = 1,000 bits

M = mega = 1,000 kilo = 1,000,000 bits

G = giga = 1,000 mega = 1,000,000,000 bits

T = tera = 1,000 giga = 1,000,000,000,000 bits

After terabit, there are petabit, exabit, zettabit, and yottabit, each representing an additional power of 10.

Bandwidth can also be expressed as bytes per second. This is commonly denoted with a capital B. For example, 10 megabytes per second would be expressed as 10 MB/s or 10 MBps.

One byte is eight bits.

Thus, 10 MB/s = 80 Mb/s.

The same metric prefixes can be used with bytes as with bits. Thus, 1 TB/s is one terabyte per second.

Measuring bandwidth is typically done using software or firmware, and a network interface. Common bandwidth measuring utilities include the Test TCP utility (TTCP) and PRTG Network Monitor, for example.

There are many ways to think about the flow of data in a network. The speed of a network is defined as the bit rate of the circuit, determined by the physical signal speed of the medium.

Bandwidth is how much of the physical circuit’s capacity can be used to transmit data and is determined by how much of the network capacity is available based on the connection. While a Gigabit Ethernet network connection would allow for 1 Gbps, the bandwidth available to a computer connected by a Fast Ethernet card would only be 100 Mbps.

Throughput is the rate of successful transmission, while bandwidth is a calculation of the amount of data that passes the network interface, regardless of whether the data results in a successful transmission. As such, throughput is always lower than bandwidth.

There are several reasons to measure bandwidth. Low usable bandwidth compared to the theoretical maximum bandwidth may be indicative of network problems, particularly if there are widely different usable bandwidths from different parts of a network that are designed to operate the same.

Additionally, measuring bandwidth is necessary to ensure that any paid connections are living up to their promise. Home users may run an online bandwidth test such as the DSLReports speed test to see just how much of that “up to 40 Mb/s” connection their internet service provider (ISP) charges them for they actually get to use. Corporate connections might be better served by measuring throughput between offices connected by a carrier-leased line connection.

Bandwidth management

In order to implement proper bandwidth management, or Quality of Service (QoS) controls, one must first understand what bandwidth is used. Once determined, a continuous measurement will ensure that all users get the necessary bandwidth.

Bandwidth throttling

Once bandwidth usage patterns are understood, and if specific users or applications are degrading network performance for others, tools can be used to limit the amount of bandwidth they are using.

Bandwidth maximums

Some types of connections have a maximum defined bandwidth. Actual bandwidth depends on many factors including environment, cabling, and usage, and is usually less than the theoretical maximum.

Wired bandwidth standards for connections

Wireless network standard maximum download speeds

Wireless network connection speeds vary widely based on the conditions of the connection. The numbers below are the maximum bandwidth speeds according to the standard or specification.

Bandwidth is most often purchased from telecommunications companies. Most consumer bandwidth is sold as “up to” meaning that the customer may get up to 40 MB/s, but not always have that speed while using the connection. Speeds may be higher or lower at different times of the day or under different circumstances. Corporate bandwidth is also typically purchased from telecommunications companies. However, many corporate agreements come with contractual performance measures that must be met, including a minimum usable bandwidth, minimum uptime, and other metrics.

Additionally, bandwidth metering may be used to charge for specific usage rather than a full connection. For example, a website owner may pay the website host only for the amount of bandwidth used by that specific website over a period of time, such as a monthly billing period.

Too little bandwidth

While modern protocols are pretty good about not losing any packets, limited bandwidth can still cause operations to be too long to complete, resulting in timeouts or other issues. These issues can cause application errors or database errors. When backing up or copying data over a network, too little bandwidth can cause backups to take too long, often running into other batch processes, or even main working hours.

In addition, users relying on a connection with too little bandwidth may notice long lag times between when they do something, like click a button, and the response to that action. In the case of waiting for information or other data to load, too little bandwidth can cause operations to take a long time, or even cause users to give up waiting.

For users attempting to make phone calls over a network, such as Voice over Internet Protocol (VoIP), having too little bandwidth results in lower quality calls. Most VoIP systems reduce the fidelity of a call based on the available bandwidth. If there is not enough bandwidth, the call may sound “tinny” or “echo-y”. If the quality is bad enough, there may be actual gaps in the call where parts of the conversation are missed.

Video calls require even more bandwidth. Video calls made without the necessary bandwidth will not only result in bad sound quality, but also low quality or jittery video.

For internet users, the United States Federal Communications Commission (FCC) recommends a minimum bandwidth of 4 Mbps for adequate performance when streaming a video in HD quality. Many video players will work with less bandwidth by “buffering”, or downloading data ahead of when it is actually displayed. If the connection is too slow, users will either have to wait a long time before the video starts while the system buffers a lot of data, or the video may stop suddenly when the system runs out of buffered video to play.

Gamers are often frustrated by limited bandwidth as well. While playing against other players online, players with faster connections see what is happening quicker, and the data about their reactions is transmitted and received faster. The FCC recommends a minimum download speed of 4 Mbps for Online Multiplayer Gaming in HD.

Table of FCC minimum required download speed

Too much bandwidth

There a few technical issues caused by too much bandwidth. Higher capacity bandwidth, however, typically costs more. Thus, too much bandwidth may not be cost effective.

Latency

Network design and infrastructure can create bandwidth issues as well. Latency measures the delays on a network that may be causing lower throughput or goodput. A low latency network has short delays, while a high latency network has longer delays. High latency prevents data from fully using the network’s capabilities, therefore decreasing the bandwidth.

Finding and remedying bandwidth issues helps improve network performance without costly upgrades.

Ping and traceroute

Tools such as Ping and traceroute can help troubleshoot basic issues.
Pinging a test server, for example, will return information on how quickly data can be sent and received, as well as average round trip times. High ping times indicate higher latency in the network.
The traceroute tool can help determine if there are too many individual network connections, or hops, along the connection path. In addition, traceroute returns the time taken by each hop. A longer time on a single hop may pinpoint the source of an issue.

TTCP

TTCP measures the time it takes for data to travel from one network interface to another with a receiver on the other end. This eliminates the return trip from the calculation and may help pinpoint issues quickly. If the measured bandwidth is less than expected, further measurements can isolate the issue. Does a measurement to another interface on the same network work faster? If so, where is the difference between the two systems? By continually measuring bandwidth, administrators can target the bottlenecks in the network.

PRTG Network Monitor

With its data gathering and graphing interface, PRTG can also help troubleshoot bandwidth problems that are not related to design. For example, by measuring bandwidth usage over time, it may be determined that certain users or applications are sometimes using higher amounts of bandwidth and causing network congestion and slowing network responsiveness and internet speed for other users.