The quick download:
ECN lets networks signal congestion without dropping packets, delivering faster, smoother data.
-
Classic TCP only detects congestion after packets are lost, slowing transmission once the damage is done.
-
ECN marks packets during congestion instead of dropping them, improving throughput and cutting retransmissions and latency.
-
ECN bleaching, where routers strip ECN markings, quietly limits these gains across many Internet paths.
-
Track ECN hop by hop with Internet Performance Monitoring to find bleaching culprits and test your L4S readiness.
No one likes traffic congestion.
That’s why no one pines for the days before Google Maps.
Using navigation apps on our phones and cars, we can see traffic updates that help us avoid busy roads during rush hour and reach our destinations faster.
The same logic applies to content delivered over the Internet.
Congestion on the web happens when data packets flood the network, causing delays and packet loss. Imagine if there was a way to be informed of congested paths, or even reduce the amount of traffic along a route altogether. By doing so, we could significantly enhance the end-user experience, ensuring faster, smoother, and more reliable data delivery.
Before looking at the solution, let’s start with how congestion has traditionally been managed.
How traditional TCP manages congestion
TCP (Transmission Control Protocol) is like a smart postal service that ensures all your messages get to the right place, in the right order, without any missing or messed up parts. This makes communication over the Internet reliable and accurate.
However, classic TCP has its problems. Ironically, it relies on congestion to detect and control the flow of data.
Here’s a breakdown:
- Congestion window size: Classic TCP increases the congestion window size (the amount of data it sends) until it detects congestion.
- Detection through packet loss: It detects congestion when packets are lost, which means the network is already congested.
- Recovery mechanisms: When congestion is detected, TCP uses mechanisms like slow start to recover, which slows down data transmission.
The issue is that classic loss-based TCP typically discovers the available capacity by increasing its sending rate until congestion results in packet loss, then reducing the congestion window in response. To build networks with low latency, low loss, and scalable throughput (L4S), it is better to signal congestion early and keep queues shallow rather than waiting for packet loss.
Enter Explicit Congestion Notification (ECN)
ECN introduces a more sophisticated approach to managing network congestion.
It’s an extension to the Internet Protocol (IP) and to the Transmission Control Protocol, as defined in RFC 3168. ECN enables devices to communicate about network congestion without losing packets, as long as components in the path support ECN and the network infrastructure is compatible.
Before understanding how ECN works, let’s checkout its operation within TCP and IP.
How ECN works with TCP and IP
ECN with IP
ECN uses two reserved bits in the Traffic Class field of the IPv4 or IPv6 header. These bits can be set in different combinations to represent four distinct code points:
- 00 – Not ECN-Capable Transport, Not-ECT
- 01 – ECN Capable Transport(1), ECT(1)
- 10 – ECN Capable Transport(0), ECT(0)
- 11 – Congestion Experienced, CE.
These combinations indicate whether the data is ECN-capable and if congestion is experienced.
ECN with TCP
TCP uses two flags in its header to implement ECN.
The first flag, ECN-Echo (ECE), signals the sender to slow down by echoing back the congestion indication.
The second flag, Congestion Window Reduced (CWR), confirms that the congestion indication was received.
ECN step-by-step
Step 1: Negotiation.
The sender and receiver agree to use ECN during their initial TCP handshake.

When the sender transmits a data packet, it sets the ECT (ECN-Capable Transport) code in the IP header to signal the router that both sender and receiver support ECN and have agreed to use it. The ECT value can be either ECT(0) or ECT(1), both indicating that, in case of congestion, the router should mark the packet instead of dropping it. If ECN negotiation fails, the sender sets the Non-ECT code point in the packet.
Step 2: Detecting congestion.
An Internet router typically manages a set of queues, often one or more per interface, which store packets awaiting transmission on that interface. Traditionally, these queues may drop packets when congestion builds. If a packet is ECN-capable and the router detects congestion, it can mark the packet CE instead of dropping it. Packet loss can still occur, particularly during severe or persistent congestion.
The router changes ECT(0) or ECT(1) to CE in the IP header and forwards the packet

The modified packet is then forwarded to the receiver. An ECN-capable network node can change an ECT(0) or ECT(1) codepoint to CE when it signals congestion. Once CE is set, routers must not reset it back to ECT.
Step 3: Notifying the sender.
The receiver detects the CE mark in the IP header, which indicates congestion. The receiver must then notify the sender about this congestion. To do this, the receiver marks the ECE (ECN-Echo) bit in the TCP header instead of the IP header to ensure this information isn’t altered by intermediary devices.

The ECE bit has two purposes. During the initial handshake (when SYN/ACK bits are set), it signifies ECN negotiation. When set in the acknowledgement (ACK) packet, it informs the sender that the router is experiencing congestion.
Step 4: Reducing the congestion window.
When the sender receives the ECE mark, it reduces its congestion window (cwnd) by 50%. If the ACK packet carrying the ECE information is dropped due to congestion, the receiver continues to send the ECE flag in subsequent packets until it gets acknowledgement from the sender.

The receiver is programmed to keep sending the ECE mark until the sender acknowledges it. This ensures that at least one ACK will reach the sender, informing it about the congestion.
Step 5: Confirming the reduction.
The sender then notifies the receiver that it has reduced the congestion window by setting the CWR (congestion window reduced) flag in the TCP header. If the packet encounters congestion again, the router can change the ECT to CE. Upon receiving a packet with the CWR flag, the receiver stops setting the ECE flag in subsequent ACKs for that congestion indication.

The sender will reduce the congestion window by half only once per ECE mark, not for each ECE. It verifies if the ECE pertains to the current congestion window; if it’s a new ECE, the sender will then reduce the cwnd. This approach mirrors NewReno’s cwnd reduction during the fast recovery phase. The receiver stops sending ECE in subsequent ACK packets after it received CWR from the sender.
Why you should be implementing ECN
Using ECN offers several key advantages for improving network performance and user experience:
#1 – Improved throughput
ECN enhances application throughput by preventing the inefficiency of discarding data that has already made it across part of the network path.
#2 – No retransmission of lost packets
Some latency-sensitive applications, like UDP-based VoIP, interactive video, or real-time data, don’t retransmit lost packets but can adjust their sending rate in response to congestion. These applications degrade significantly with packet loss and use methods like error correction, data duplication, or codec error concealment to counteract congestion effects. However, these methods add complexity, consume extra network capacity, and increase path latency during congestion.
ECN helps by decoupling congestion control from packet loss, allowing transports to reduce their rate before the application encounters loss. This minimizes the negative impact of loss-mitigation methods, improving user experience.
#3 – Decreased likelihood of RTO expiration
Reducing the likelihood of packet loss is crucial for reliable transport in applications that send bursts of segments and then go idle, either due to no more data or network constraints like flow or congestion control.
Standard transport recovery methods, such as Fast Recovery, often fail to handle the loss of the last segment(s) of a burst, known as “tail loss.” The receiver, unaware of the missing segments, provides no feedback, so retransmission depends on a transport retransmission timer. This timer expiry results in the loss of network path state, resetting path estimates like RTT and reinitializing the congestion window, which degrades transport performance until it readapts to the path.
When congestion occurs at the end of a burst, an ECN-capable network device can mark the packet(s) with CE instead of dropping them. This prevents a retransmission timeout, reducing application latency and improving throughput for applications that send intermittent bursts and rely on timer-based recovery.
#4 – Minimized head-of-line blocking
With ECN, an application can keep receiving data during incipient congestion, avoiding the extra reordering delay in reliable transport. When a transport receives a CE-marked packet, it prompts the sender to appropriately reduce the maximum transmission rate for future traffic.
Monitoring ECN Across the Network
As lag-sensitive applications like AR/VR, streaming, gaming, Metaverse, and autonomous vehicles continue to grow in popularity, the demand for seamless performance increases. To ensure a superior network experience for your end users, LogicMonitor Digital Experience includes traceroute with the ability to track ECN settings. If a router on the network bleaches ECN during congestion, increased latency could occur. As an Internet service provider or a partner to one, you can monitor your infrastructure and track the ECN bleaching culprits. This allows you to test your L4S readiness with ECN traceroute. Additionally, this capability is available as open source on GitHub to support the broader community.
Traceroute provides hop-by-hop visibility into the path a probe takes from source to destination, including latency, packet loss, IP addresses, hostnames (where available), ASNs, countries, and ECN status. When ECN is enabled end to end, it becomes possible to identify where ECN markings are preserved, modified, or reset to Non-ECT, helping pinpoint congestion and ECN bleaching across the network.
The example below shows a single traceroute run and the exact hop where ECN was bleached.

ECN traceroute data can also be analyzed over time to identify trends and measure how frequently ECN bleaching occurs across different paths and locations.
The example below shows that approximately 32% of traceroute requests experienced ECN bleaching during a one-hour sample period.

Comparing traceroute results with and without ECN support provides additional insight into network performance. When ECN is supported end to end, congestion can be signaled without dropping packets, helping reduce retransmissions and latency while identifying exactly where congestion occurs.
The example below compares traceroute trends with and without ECN support.

In this dataset, overall round-trip time was approximately 47% lower on paths where ECN was supported end-to-end.
From ECN Visibility to Better Network Performance
As applications like AR/VR, streaming, gaming, and autonomous vehicles continue to push the limits of network performance, low latency and high reliability have become essential. ECN offers a more efficient way to manage congestion by signaling it without dropping packets, helping improve throughput, reduce latency, and deliver a better user experience.
LogicMonitor Digital Experience takes this a step further by providing full visibility into traffic routing decisions around network congestion. With advanced traceroute capabilities, network administrators can identify and address congestion points, ensuring smoother and faster data delivery. As part of the broader LogicMonitor platform, these capabilities connect network-level insights with infrastructure and application telemetry, giving teams the full picture they need to deliver exceptional real-time experiences.
Research on global ECN bleaching rates shows that a significant portion of Internet paths still strip ECN markings, limiting the protocol’s effectiveness. Understanding where ECN bleaching occurs across your network is a critical step toward L4S readiness and better congestion management overall.
Pinpoint ECN bleaching before it slows your users down.
Get hop-by-hop ECN visibility to identify where ECN markings are stripped, validate L4S readiness, and troubleshoot network paths with confidence.
FAQs
What is ECN bleaching?
ECN bleaching happens when a router along the path strips or resets ECN markings during congestion instead of preserving them. This limits ECN’s effectiveness and can drive up latency. Tracking traceroute with ECN status lets you identify the exact hop responsible for the bleaching.
How is ECN different from traditional TCP congestion control?
Classic TCP detects congestion only after packets are lost, then slows transmission to recover. ECN signals congestion by marking packets before they are dropped, so the sender can reduce its rate without triggering packet loss and retransmissions. The result is higher throughput and lower latency.
Why does ECN matter for latency-sensitive applications?
Applications like AR/VR, streaming, gaming, and autonomous vehicles depend on low latency and high reliability. ECN reduces retransmissions and the chance of retransmission timeouts, which keeps throughput steady and real-time experiences smooth even as congestion builds.




