---
title: "Congestion Control and Sharing a Link"
description: "Nothing tells a sender how much of the path is free, so it probes: increase the rate while packets get through, and cut it sharply when they do not. That rule is what keeps a shared network from colla"
canonical: https://lightmysky.com/learn/computing/congestion-control-and-sharing-a-link-mt_y5hPUrdKyq
source: https://lightmysky.com/learn/computing/congestion-control-and-sharing-a-link-mt_y5hPUrdKyq.md
retrieved: 2026-09-12
---

> **Agent view.** This is the Markdown twin of the page, for tools and assistants.
> When to use this site, and the call that answers each job: https://lightmysky.com/agent-instructions.md
> API description (OpenAPI 3.1): https://lightmysky.com/openapi.json · Authentication: https://lightmysky.com/auth.md
> Pricing: https://lightmysky.com/pricing.md · Catalog: https://lightmysky.com/llms.txt · Full catalog: https://lightmysky.com/llms-full.txt
> Every machine-readable file on this domain: https://lightmysky.com/.well-known/ai-catalog.json
> Ask for Markdown with `Accept: text/markdown`, a `.md` address, or `?mode=agent`.

# Congestion Control and Sharing a Link

Nothing tells a sender how much of the path is free, so it probes: increase the rate while packets get through, and cut it sharply when they do not. That rule is what keeps a shared network from collapsing, and it makes loss a signal rather than only a fault.

Subject: Computing · Area: Networks & Security · Ages 18 to 20
Page: https://lightmysky.com/learn/computing/congestion-control-and-sharing-a-link-mt_y5hPUrdKyq

## Ready when they can

- Explain why a sender treats a lost packet as evidence about the path
- Sketch how a sending rate rises and falls over time under this rule
- Say what happens if one sender ignores the rule while others follow it

## Lesson: Sharing one link without breaking it

No sign tells a sender how much path is free, so it probes. It raises its rate while packets land, and it cuts sharply when one is lost. A lost packet is treated as news that the path is full, not only as a fault.

**Example.** Watch one sender over time and you see teeth: a steady climb while all lands, a sharp drop at the first loss, then a climb again. That sawtooth is the probe at work, always testing for fresh room.

If one sender ignores the rule and never slows, it grabs the queue while polite senders back off. Queues bloat, delays spike, and the shared link serves all of them worse. One cheat punishes the whole crowd.

**Tip.** Read every loss as a signal to slow, not as bad luck. Back off fast, then climb gently to reclaim room.

**Recap.** Probe gently, cut fast on loss, since ignoring the rule wrecks the shared link.

## Practice

8 questions on this page, each with its working shown.

## Needs first

- [Reliable Delivery over an Unreliable Network](https://lightmysky.com/learn/computing/reliable-delivery-over-an-unreliable-network-mt_kCM411CSac)

## Opens up

- [Naming: DNS and the Resolution Path](https://lightmysky.com/learn/computing/naming-dns-and-the-resolution-path-mt_omttmGkEgW)