Collision Domain and Broadcast Domain

By : Bryce Leo Bryce Leo
Hours Updated

⚡ Smart Summary

Collision domain and broadcast domain describe two ways a network segment is scoped: a collision domain is where device frames can collide on shared media, while a broadcast domain is where a broadcast reaches every device.

  • 🧨 Collision domain: A collision domain is a shared segment where two frames sent at the same time collide and must be resent.
  • 📢 Broadcast domain: A broadcast domain is the set of devices that receive a Layer 2 broadcast without a router in between.
  • 🔀 Device behavior: Hubs keep one of each domain; switches split collision domains per port; routers split both.
  • 🧬 Segmentation: VLANs divide a single switch into multiple broadcast domains, cutting unnecessary broadcast traffic.
  • ⚡ Performance: Fewer devices per collision domain means fewer collisions, less retransmission, and higher throughput.
  • 🤖 AI monitoring: Machine-learning monitors flag broadcast storms and abnormal collisions before they degrade the network.
Read More

Collision domain and broadcast domain compared in a network

What is a Domain?

In general computing, a domain is a group of user computers, printers, accounts, and other devices that are registered in a central database. That database is held on one or more central servers known as domain controllers.

In networking, however, the terms collision domain and broadcast domain use the word “domain” in a different sense. They describe the scope, or reach, of certain traffic across a segment of a computer network rather than an administrative grouping of devices. The rest of this article explains both.

What is a Collision Domain?

A collision domain is the set of devices whose frames could collide with one another. It is a network segment connected by a shared medium, or joined using repeaters, where simultaneous data transmissions collide.

Collision domains apply to wireless networks and also affect earlier, half-duplex versions of Ethernet. A collision happens when two separate devices send a packet at the same time on the shared network segment. The packets collide, and both devices must resend their packets, which reduces overall network efficiency.

What is a Broadcast Domain?

A broadcast domain is a logical division of a computer network. Within this type of domain, nodes can reach one another using a broadcast at the data link layer. A broadcast domain can exist within a single LAN segment or bridge across to other LAN segments.

The domain contains every device that can reach the others at the data link layer through a broadcast. Every port on a switch or a hub is normally part of the same broadcast domain.

All ports on a router, by contrast, belong to distinct broadcast domains, and a router never forwards a broadcast from one domain to another.

Example of Collision Domains

The diagram below shows a simple collision domain built around a shared hub:

Collision domain example where frames from Computer A and Computer B collide on a shared hub

In this example, “Computer A” sends a data signal to “Computer C” while, at the same time, “Computer B” sends a data signal to “Computer D.” Because all four devices share one medium, the two transmissions collide.

As the number of devices in a collision domain rises, the chance of a collision also rises. More traffic on the segment means more collisions, and more network devices in a single collision domain make collisions more frequent still.

A high collision count produces a low-quality network, because hosts spend a large amount of time on packet processing and retransmission. Note that a collision never happens between two devices connected to different ports of a switch, since each switch port is its own collision domain.

Example of Broadcast Domains

The next diagram shows how a broadcast travels through a switched network:

Broadcast domain example where a switch floods a broadcast packet to every port

In this image, “Computer A” sends a broadcast, and the switch forwards it to all of its ports. Every connected switch receives a copy of the broadcast packet and, in turn, floods it out to all of its own ports.

A router also receives a copy of the broadcast packet, but it does not forward the packet to the next network segment. As the number of broadcast domains and broadcasts increases, more bandwidth is consumed and overall network quality falls.

RELATED ARTICLES

Difference Between Collision and Broadcast Domain

The graphic below summarizes the contrast between the two domain types at a glance:

Side-by-side summary graphic of collision domain versus broadcast domain

Here are the important differences between a collision domain and a broadcast domain:

Collision Domain Broadcast Domain
The collision domain is a network section that allows traffic to flow forward and backward. A broadcast domain is a segment in which traffic flows all over the network.
The collision domain refers to a set of devices in which a packet collision could occur. The broadcast domain refers to a logical set of reachable computer systems without using a router.
The devices may include devices from other IP subnetworks. The broadcast domain is not limited to a specific IP subnetwork for all types of IP broadcasts.
Packet collision occurs when multiple devices transmit data on a single wire link. The broadcast domain mostly uses a switched environment, so no collision occurs.
Switches break up (segment) a collision domain — each port is its own collision domain. Switches do not break up a broadcast domain — a broadcast is forwarded to every port.
Every port on a router sits in a separate collision domain. All ports on a switch or a hub are likely to be in the same broadcast domain.

KEY DIFFERENCES

  • Traffic in a collision domain moves back and forth on a shared link, while a broadcast reaches every device across the whole broadcast domain.
  • A collision domain can span devices in different IP subnetworks; a broadcast domain is bounded by routers rather than by a single IP subnet.
  • Collisions happen only when devices share one wire, whereas a switched broadcast domain avoids them because each switch port is its own collision domain.

FAQs

A hub has one collision domain and one broadcast domain. A switch places each port in its own collision domain but keeps a single broadcast domain. A router separates both, giving every interface a distinct collision and broadcast domain.

A switch creates one collision domain per active port, so a 24-port switch has 24 collision domains. By default, all of those ports share a single broadcast domain. A router or configured VLANs are required to create additional broadcast domains.

Each VLAN on a switch forms a separate broadcast domain, so only ports in the same VLAN receive a given broadcast. VLANs let one physical switch host several logical broadcast domains without adding routers, improving security and reducing broadcast traffic.

Carrier Sense Multiple Access with Collision Detection (CSMA/CD) is the method half-duplex Ethernet devices use to share one collision domain. Each device listens before sending and, if a collision is detected, waits a random time before retransmitting. Full-duplex switching makes CSMA/CD unnecessary.

Collision domains relate to the physical and data link layers, where the shared medium and framing live. Broadcast domains operate at the data link layer of the OSI model, since broadcasts are forwarded by Layer 2 devices and stopped by Layer 3 routers.

No. A full-duplex link between a device and a dedicated switch port has no shared medium, so its collision domain contains a single device and collisions cannot occur. Collisions remain only on legacy half-duplex hubs and shared Ethernet segments.

Machine-learning tools baseline normal traffic and flag anomalies such as broadcast storms, excessive collisions, or misbehaving hosts in real time. AI-assisted network monitors correlate these patterns across switches to locate the faulty segment faster than manual packet inspection.

GitHub Copilot can draft Python scripts that parse switch counters, detect broadcast storms, or simulate collision behavior from a short comment. Review the generated logic and thresholds carefully before running it against production network equipment.

Summarize this post with: