A MAN, or metropolitan area network, is a computer network that interconnects multiple local area networks across a city, metropolitan region or large campus, typically over distances of about 5 to 50 kilometers. In networking fundamentals, the MAN occupies the middle of the scale classification: larger than a LAN, smaller and usually faster per dollar than a WAN.
A MAN is defined less by a single protocol than by its geographic reach and ownership model. It may belong to a municipality, a university, a utility or a telecommunications carrier, and it is usually built on optical fiber rings that deliver high bandwidth with fast failure recovery.
How a metropolitan area network is built
A modern MAN follows a hierarchical design with three layers. The access layer connects buildings, offices or cell sites; the aggregation layer collects that traffic at central points of presence; and the metro core links those points with high-capacity fiber, often arranged in rings so that a single cut does not isolate any site.
The physical foundation is almost always single-mode fiber, either leased as dark fiber or owned outright. Operators multiply capacity with wavelength-division multiplexing: coarse WDM carries up to 18 wavelengths cheaply over shorter spans, while dense WDM packs dozens of channels of 100 Gbit/s or more onto one fiber pair. Packet transport on top typically uses Carrier Ethernet, MPLS or segment routing.
The table below lists the main building blocks and their roles in a metro design.
| Component | Role in the network | Typical technology |
|---|---|---|
| Fiber plant | Physical transmission medium across the city | Single-mode fiber in ducts or poles |
| Optical layer | Multiplies capacity per fiber pair | CWDM, DWDM, optical transport network |
| Metro core routers | Forward and protect aggregated traffic | MPLS, segment routing |
| Aggregation switches | Collect traffic from access sites | Carrier Ethernet, link aggregation |
| Access devices | Hand off service to each customer site | Network interface devices, optical terminals |
| Ring protection | Restores traffic after a fiber cut | ITU-T G.8032, SONET or SDH protection |
MAN technologies and their evolution
MAN technology has changed several times, and the term outlived most of its original standards. The IEEE created the IEEE 802.6 standard, Distributed Queue Dual Bus, specifically for metropolitan networks, but it saw little deployment and was withdrawn. FDDI dual rings at 100 Mbit/s and later SONET and SDH rings carried most metro traffic in the 1990s.
Since the 2000s, Metro Ethernet has dominated, standardized as services by the MEF Forum with defined service types and performance attributes. Wireless metropolitan access appeared with IEEE 802.16, marketed as WiMAX, although mobile broadband largely replaced it. The following table summarizes this progression.
| Technology | Era of wide use | Typical capacity | Current status |
|---|---|---|---|
| IEEE 802.6 DQDB | Early 1990s | Up to about 155 Mbit/s | Withdrawn, historical |
| FDDI | Late 1980s to 1990s | 100 Mbit/s | Obsolete |
| SONET and SDH rings | 1990s to 2010s | 155 Mbit/s to 40 Gbit/s | Legacy, being retired |
| Metro Ethernet | 2000s to present | 1 to 400 Gbit/s | Dominant service model |
| IEEE 802.16 WiMAX | Late 2000s | Tens of Mbit/s per sector | Largely displaced by LTE |
| DWDM optical transport | 2000s to present | Terabits per fiber pair | Standard metro core layer |
MAN compared with LAN, WAN and PAN
The scale classes overlap, and the boundary between them is a matter of convention rather than strict definition. A MAN differs from a LAN mainly in reach and ownership, and from a WAN mainly in distance, latency and the number of carriers involved.
| Network type | Typical reach | Usual owner | Typical latency |
|---|---|---|---|
| PAN | A few meters | Individual user | Microseconds |
| LAN | A building or floor, up to about 1 km | Single organization | Well below 1 ms |
| MAN | About 5 to 50 km | Municipality, campus or carrier | About 1 ms or less |
| WAN | Countries and continents | Carriers and large enterprises | Tens to hundreds of ms |
Latency in a MAN stays low because light in fiber travels at roughly 5 microseconds per kilometer, so even a 50 km ring adds only about a quarter of a millisecond of propagation delay. That property makes metro networks suitable for synchronous storage replication and real-time applications that a long-haul WAN cannot support.
When organizations choose a MAN
A MAN is the right design when several sites within one city need LAN-like performance between them. Organizations either build a private MAN on owned or leased fiber or buy managed metro services from a carrier, trading control against capital cost.
| Situation | Recommended approach | Reason |
|---|---|---|
| City government with many buildings | Municipal fiber MAN | Long-term savings over leased circuits |
| University with distant campuses | Private dark fiber ring | Full control and very high capacity |
| Two data centers in one metro | DWDM data center interconnect | Low latency for synchronous replication |
| Small company with three offices | Carrier Metro Ethernet service | No need to manage fiber or optics |
| Mobile operator backhaul | Carrier Ethernet with timing support | Aggregates many cell sites efficiently |
In MEF terminology, a point-to-point service is an E-Line, a multipoint service that behaves like one large LAN is an E-LAN, and a hub-and-spoke service is an E-Tree. Many enterprises extend VLANs across these services, so the remote offices appear on the same Layer 2 segment.
Limitations and common design mistakes
The largest obstacle is fiber cost and access: digging trenches, securing permits and obtaining rights of way can dominate a MAN budget. Physical routes also matter, because two fibers in the same duct share the same risk of a single backhoe cut.
- Assuming ring diversity: a logical ring may run through one physical path, so verify route maps.
- Stretching Layer 2 too far: large flat broadcast domains across a city amplify loops and broadcast storms.
- Ignoring protection timing: applications need failover within about 50 milliseconds, which requires proper ring protection.
- Undersizing optics: traffic growth often outpaces plans, so leave spare wavelengths and fiber strands.
A plain-language summary
A home or office network connects the devices in one place. A metropolitan area network connects many such places across a whole city, such as all the schools, hospitals or offices of one organization.
It works like a private highway system for data inside the city. Thick fiber cables run between buildings, often in a loop, so if one cable is cut, traffic simply travels the other way around. The result is speed close to that of a single office, spread over many kilometers.
An example from practice
A city of about 300,000 people operates 40 public buildings, including the town hall, libraries, fire stations and schools, each previously connected through separate leased lines of 100 Mbit/s. Monthly circuit fees keep rising, and the schools need far more capacity for online teaching.
The city lays a 96-strand fiber ring of about 35 km along existing utility ducts and connects each building with a short lateral. Aggregation switches at four points of presence run Carrier Ethernet with G.8032 ring protection, giving every site a 10 Gbit/s link. When a construction crew later cuts the ring, traffic reroutes in under 50 milliseconds and no service notices the outage.
Within about seven years, the avoided leased-line fees cover the construction cost, and the city leases spare strands to local internet providers to generate additional income.