Network connectivity & latency • 2026 standards
Latency Measurement: Time from packet send to receipt of reply
Packet Loss Calculation: (Lost Packets / Total Packets) × 100
Jitter Calculation: Variance in packet arrival times
Quality Indicators:
Network performance affects all online activities. Consistent low latency is critical for real-time applications.
| Seq | Time (ms) | Status | TTL |
|---|---|---|---|
| 1 | 18 | OK | 56 |
| 2 | 25 | OK | 56 |
| 3 | 32 | OK | 56 |
| 4 | 25 | OK | 56 |
| Metric | Value | Quality |
|---|---|---|
| Latency | 25 ms | Excellent |
| Packet Loss | 0% | Perfect |
| Jitter | 4 ms | Low |
| Reliability | 100% | High |
Ping tests measure network latency by sending ICMP echo requests and measuring round-trip time. Lower latency indicates better network performance.
Latency: Time for packet to travel to destination and back. Jitter: Variation in latency. Packet Loss: Percentage of packets that fail to reach destination.
High latency may indicate network congestion, distance to target, or routing issues. Packet loss suggests network problems or firewall restrictions.
What protocol does the ping command primarily use?
The answer is C) ICMP. Ping uses the Internet Control Message Protocol (ICMP) to send echo requests and receive echo replies. ICMP is a network layer protocol used for diagnostic and control purposes in IP networks.
ICMP is specifically designed for network diagnostics and error reporting. Unlike TCP or UDP, it doesn't establish connections or carry application data. Ping and traceroute are common tools that use ICMP for network troubleshooting.
ICMP: Internet Control Message Protocol for network diagnostics
Echo Request: ICMP message sent by ping to test connectivity
Echo Reply: ICMP response to echo request
• Ping uses ICMP protocol
• ICMP operates at network layer
• Not all firewalls allow ICMP
• Remember: Ping = ICMP
• Some networks block ICMP
• Use alternative tools if ping blocked
• Confusing ping with TCP or UDP protocols
• Not understanding ICMP's diagnostic purpose
• Assuming all networks allow ping
A ping test returns the following round-trip times: 25ms, 30ms, 20ms, 35ms. Calculate the average latency and determine the quality level according to standard network classifications.
Average latency calculation:
(25 + 30 + 20 + 35) ÷ 4 = 110 ÷ 4 = 27.5 ms
Quality classification:
• Excellent: < 20ms
• Good: 20-50ms
• Fair: 50-100ms
• Poor: > 100ms
Since 27.5ms falls in the 20-50ms range, this is classified as "Good" network performance.
Average latency is calculated by summing all round-trip times and dividing by the number of tests. This metric provides a representative measure of network performance, though individual variations (jitter) can also be important.
Round-Trip Time (RTT): Total time for packet to travel to destination and return
Average Latency: Mean of all RTT measurements
Jitter: Variation in packet arrival times
• Average = Sum of values ÷ Count
• Lower latency = better performance
• Consistent latency = better than average
• Calculate average for multiple samples
• Look for consistency, not just average
• Consider peak values for real-time apps
• Using only single measurements
• Not considering variation in results
• Misunderstanding quality thresholds
A network engineer runs a ping test with 100 packets of 64 bytes each. 5 packets are lost during transmission. Calculate the packet loss percentage and determine if this meets the criteria for "Good" network performance. Also calculate the total data transmitted successfully.
Packet loss calculation:
(Lost packets ÷ Total packets) × 100
(5 ÷ 100) × 100 = 5%
Performance classification:
• Excellent: 0% loss
• Good: < 1% loss
• Fair: 1-3% loss
• Poor: > 3% loss
With 5% loss, this is classified as "Poor" performance.
Successful data calculation:
Successfully received packets: 100 - 5 = 95 packets
Total data: 95 × 64 bytes = 6,080 bytes
Packet loss directly impacts network reliability. Even small percentages can significantly affect performance for real-time applications. Understanding both loss percentage and total data transmitted provides a complete picture of network performance.
Packet Loss: Percentage of packets that fail to reach destination
Reliability: Measure of successful packet deliveryThroughput: Amount of data successfully transmitted
• Packet loss = (lost ÷ total) × 100
• Good networks have < 1% loss
• Data calculation = successful packets × size
• Aim for < 1% packet loss
• Multiple tests provide better averages
• Consider both percentage and absolute numbers
• Not understanding packet loss impact
• Forgetting to multiply by packet size
• Misinterpreting quality thresholds
A VoIP application requires consistent latency for quality voice calls. The ping test shows an average latency of 30ms but with significant variation: 15ms, 55ms, 20ms, 70ms. Calculate the jitter (standard deviation) and explain why this might cause poor voice quality despite the acceptable average.
Calculating jitter (standard deviation):
Mean (μ) = (15 + 55 + 20 + 70) ÷ 4 = 40ms
Variance = [(15-40)² + (55-40)² + (20-40)² + (70-40)²] ÷ 4
Variance = [625 + 225 + 400 + 900] ÷ 4 = 537.5
Standard deviation (σ) = √537.5 ≈ 23.2ms
This high jitter (23.2ms) would cause poor VoIP quality because:
• Voice packets arrive at inconsistent intervals
• Audio buffering struggles to maintain smooth playback
• Packets may arrive out of order
• Overall call quality degrades despite good average latency
For real-time applications like VoIP, video conferencing, or gaming, consistent latency (low jitter) is often more important than average latency. High jitter causes timing issues that degrade user experience even when average performance seems acceptable.
Jitter: Variation in packet arrival times
Standard Deviation: Measure of data dispersion
Real-Time Applications: Apps requiring consistent timing
• Low jitter is crucial for real-time apps
• Consistency often matters more than average
• High jitter degrades user experience
• Monitor both average and variance
• Use QoS for real-time applications
• Consider network buffering solutions
• Focusing only on average latency
• Not considering application requirements
• Underestimating jitter impact
Which of the following is the most likely cause of high ping times but 0% packet loss?
The answer is B) Target server overloaded. High ping times with 0% packet loss indicates that packets are reaching the destination and being returned, but the response time is slow. This typically happens when the target server is busy processing other requests and delays responding to ping requests.
Other options would cause different symptoms:
• Disconnected cable: 100% packet loss
• Firewall blocking: 100% packet loss
• DNS failure: Would prevent ping from starting
Understanding the difference between latency and packet loss helps diagnose network issues. High latency with no loss suggests the path exists but has performance issues, while packet loss indicates connectivity problems.
Latency: Time for packet to travel to destination
Packet Loss: Percentage of packets not reaching destination
Network Diagnostics: Process of identifying connectivity issues
• High latency ≠packet loss
• Different symptoms indicate different issues
• Correlate multiple metrics for diagnosis
• Correlate latency with packet loss
• Test multiple destinations
• Consider server-side issues
• Confusing latency with packet loss
• Not considering server-side factors
• Drawing conclusions from single metrics
Q: What is considered good ping time for online gaming?
A: For online gaming, ping times are categorized as:
Competitive gamers typically aim for < 30ms ping. Consistent latency is often more important than absolute values.
Q: Why does ping sometimes fail while websites still load?
A: Ping can fail while websites still load because:
This is normal behavior - ping is often blocked for security reasons.