# Packet Loss

Packet loss is the failure of transmitted network packets to reach their intended destination.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/packet-loss

> Packet loss reduces network reliability and can cause retransmissions, lower throughput, application timeouts, and degraded real-time communication. Engineers assess it using endpoint measurements, active probes, device counters, and traffic records, distinguishing actual delivery failures from monitoring artifacts or intentional filtering.

Practice exams covering Packet Loss: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key aspects of Packet Loss

Reliable packet-loss analysis requires clearly scoped measurements, application-aware thresholds, and correlated evidence from multiple points along the network path.

1. **Explicit measurement scope**: Define the endpoints, direction, protocol, packet size, timeout, and observation interval for every loss measurement. Round-trip probe loss cannot independently identify which direction failed.
2. **Application-dependent impact**: TCP recovery can turn packet loss into reduced throughput and increased latency rather than visible data loss. Real-time UDP traffic may instead exhibit audio gaps, video artifacts, or missing updates.
3. **Correlated performance signals**: Evaluate loss alongside latency, jitter, retransmissions, utilization, interface errors, and discards. Correlation helps distinguish congestion from physical errors, resource limits, and policy-driven drops.
4. **Complementary active and passive evidence**: Active probes test delivery, while flow records, host counters, device metrics, and packet captures help explain failures. No individual telemetry source provides complete visibility across an entire hybrid path.
5. **Measurement artifacts and asymmetry**: ICMP rate limiting, probe filtering, asymmetric routing, and capture drops can distort conclusions. Confirm suspected loss at the destination using traffic representative of the affected application.
6. **Burst-aware monitoring**: Short loss bursts can disrupt applications even when long-term averages appear acceptable. Select sampling intervals and alarm windows that reflect application tolerance without treating every isolated missed probe as an outage.

## Cloud services for Packet Loss

CloudWatch brings active path measurements, service metrics, and custom host telemetry into shared dashboards and alarms. When loss appears, VPC Flow Logs help investigate filtering, while EC2 counters and packet captures provide endpoint evidence. Transit Gateway drop counters expose missing-route and blackhole conditions, and Direct Connect metrics help assess hybrid-link load and health. Correlate these sources using consistent timestamps and endpoint identifiers, then compare them with on-premises router telemetry. This combination separates delivery symptoms from likely causes without assuming that flow acceptance or an available connection guarantees successful packet delivery.

- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Collect and alarm on network metrics and custom endpoint loss measurements. CloudWatch Network Monitor provides active packet-loss and round-trip latency monitoring for paths between AWS-hosted subnets and on-premises destinations.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: VPC Flow Logs provide traffic metadata and ACCEPT or REJECT decisions that help investigate filtering and connectivity issues. Traffic Mirroring can supply packet-level evidence from supported interfaces, but neither flow records nor a single capture point proves end-to-end delivery.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Endpoint tools, operating-system counters, and packet captures on EC2 instances help measure delivery and retransmissions. On supported instances, ENA metrics such as pps_allowance_exceeded and bw_out_allowance_exceeded reveal packets queued or dropped when network allowances are exceeded.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: Connection and virtual-interface metrics help correlate hybrid-network loss with traffic load and connection health. Combine these metrics with active probes and customer-router error and discard counters; connection availability alone does not establish loss-free delivery.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: CloudWatch metrics such as PacketDropCountBlackhole and PacketDropCountNoRoute identify specific routing-related drops. Correlate them with attachment traffic and route-table configuration rather than interpreting them as a complete end-to-end loss percentage.

## Packet Loss exam questions

Real practice exam questions on Packet Loss, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company sends one-way UDP monitoring traffic between two EC2 instances in different subnets of the same VPC. Each monitoring datagram contains a unique sequence number. Existing endpoint agents can record transmitted and received sequence numbers with synchronized timestamps.

A dashboard estimates packet loss by subtracting the destination network interface's VPC Flow Logs packet count from the source network interface's packet count for each wall-clock minute. It reports intermittent loss of 8%. The logs use a 1-minute maximum aggregation interval, and some destination records have log-status set to SKIPDATA. Application health checks remain successful.

A network engineer must determine whether the reported loss represents actual delivery failures and measure the one-way delivery loss for the monitoring traffic. Which approach provides the most reliable evidence?

**Correct answer:** Use the endpoint agents to record the unique sequence numbers sent during a defined interval and match them against received sequence numbers. Allow a defined arrival grace period, deduplicate received sequence numbers, and calculate the fraction of transmitted sequence numbers that were not received.

**Explanation:** Matching the same uniquely identified datagrams at both endpoints directly measures one-way delivery. A defined grace period avoids counting packets still in transit as lost, and deduplication prevents duplicate arrivals from masking missing datagrams. SKIPDATA indicates omitted flow-log records, not evidence that the corresponding application packets were dropped.

## Practice Packet Loss in a full exam

Questions on Packet Loss in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 5 questions

## What is Packet Loss

Packet loss occurs when packets transmitted by a source do not arrive at their intended destination. Causes include congestion, exhausted buffers, physical link errors, interface limits, routing failures, and intentional drops by security controls. Loss can be intermittent, sustained, or concentrated in short bursts. Its impact depends on the application: TCP normally retransmits missing data but may reduce its sending rate, while UDP applications must tolerate missing data or implement their own recovery.

A basic loss percentage is the number of missing packets divided by the number transmitted, multiplied by 100. Measurements must use matching traffic populations and account for packets still in transit, duplicates, and the observation window. For example, if 1,000 uniquely identified probes are sent and 990 arrive within the defined measurement period, measured loss is 1%. Request-and-response probes measure round-trip success, so missing responses alone do not identify whether the forward path, return path, or destination caused the failure.

In cloud and hybrid networks, monitoring should cover representative paths between workloads, Availability Zones, Regions, and on-premises locations. Collect packet-loss measurements alongside round-trip latency, jitter, throughput, interface utilization, errors, discards, and TCP retransmissions. Preserve source, destination, protocol, packet size, and timestamps so that incidents can be correlated with routing changes, deployments, or traffic spikes. Establish application-specific thresholds and retain sufficiently granular data to expose bursts that long averaging periods can hide.

Use active probes to test delivery and passive telemetry to investigate causes. Tools such as ping and mtr can reveal symptoms, but ICMP filtering or response rate limiting can make a healthy application path appear lossy. A router that fails to answer diagnostic probes may still forward transit traffic normally. Apparent loss at an intermediate hop is not proof of forwarding loss, especially when later hops and the destination respond reliably. Validate findings with application-relevant TCP or UDP tests and, where possible, measurements in both directions.

AWS telemetry provides complementary evidence rather than one universal packet-loss metric. Amazon CloudWatch Network Monitor supports active monitoring between AWS-hosted subnets and on-premises destinations. VPC Flow Logs show traffic metadata and ACCEPT or REJECT decisions, but they are not packet captures and cannot establish an end-to-end loss percentage. An ACCEPT record does not guarantee destination delivery. AWS Transit Gateway exposes counters for packets dropped because of missing routes or blackhole routes. On supported EC2 instances, ENA allowance-exceeded counters help identify instance-level bandwidth or packet-rate constraints.

For example, when a hybrid application's throughput falls during backups, compare active loss measurements with AWS Direct Connect utilization, on-premises interface discards, and host retransmissions. If a link or instance allowance is saturated, increasing capacity or shaping competing traffic may help. If only larger packets fail, investigate path MTU and blocked ICMP messages required for path MTU discovery rather than assuming congestion. Configuration analysis can identify routing or security-policy problems, but it does not measure live packet delivery.

Monitoring itself has trade-offs. More frequent probes improve detection but add traffic and cost; packet capture provides detail but introduces storage, privacy, and processing requirements. Retries can conceal loss from users while increasing latency and load. Define alarms around sustained degradation and application impact, while retaining short-window measurements for burst analysis. Do not assume that a healthy link state, an established VPN tunnel, or low average utilization proves that packets are being delivered successfully.
