The Idea: Label Instead of Lookup
On the public internet, every router a packet passes through reads its destination IP address and consults its own routing table to decide where to send it next. Each hop is an independent decision, made fresh, with no memory of what came before.
MPLS — Multiprotocol Label Switching — replaces that repeated work with a single decision made once, at the edge. When a packet enters an MPLS network, the first router classifies it and attaches a short, fixed-length label. From then on, every router along the way forwards the packet by reading just that label from a small label table — no IP lookup, no routing-table search. The path the packet follows is fixed in advance and called a label-switched path. At the far edge, the label is stripped off and the packet continues as plain IP.
The "multiprotocol" in the name reflects that MPLS sits between the link layer and the network layer — sometimes called "layer 2.5" — and can carry many kinds of traffic, not just IP.
How a Packet Travels Through MPLS
The lifecycle of a labelled packet has three clear stages, handled by two kinds of router:
- Push (ingress edge router). The packet enters the network. The edge router classifies it into a forwarding equivalence class — a group of packets that should all take the same path — and pushes the appropriate label onto it.
- Swap (core routers). Each core router along the path looks only at the incoming label, swaps it for the next label in the path, and forwards the packet. This label lookup is simple and uniform, regardless of how complex the underlying IP destination is.
- Pop (egress edge router). At the exit, the final label is removed and the packet leaves as ordinary IP, continuing to its destination.
Because core routers never inspect the IP header, the heavy classification work happens once, at the entrance, rather than at every hop.
Why Providers Use It
MPLS persists not because raw label lookup is dramatically faster on modern hardware — it largely isn't anymore — but because deciding the path up front gives operators powerful control:
- Traffic engineering. Because paths are explicitly chosen rather than left to shortest-path routing, operators can steer traffic along specific routes, balance load across links, and route around congestion deliberately.
- Quality of service. Different label-switched paths can carry different priority traffic, so latency-sensitive flows like voice get predictable treatment. This complements ordinary QoS and traffic shaping.
- Separation. Labels can keep different customers' or departments' traffic logically isolated across the same shared infrastructure, much as a VLAN does on a local network.
In short, MPLS trades the internet's flexible, hop-by-hop independence for an operator's ability to design and guarantee paths.
MPLS VPNs
The separation property is what makes MPLS the foundation of provider-managed VPNs. An MPLS VPN connects a company's branch offices, data centres, and headquarters across the carrier's network as if they were one private network, with each customer's traffic kept apart by labels. Unlike a VPN tunnel over the public internet, an MPLS VPN is a private path with consistent, contracted performance — but note that it provides separation, not encryption by default; sensitive traffic is still encrypted on top where needed.
MPLS vs the Public Internet
| Public internet | MPLS | |
|---|---|---|
| Forwarding | IP lookup at every hop | Label swap along a fixed path |
| Path | Chosen hop by hop, can change | Engineered and predetermined |
| Performance | Best-effort, variable | Predictable, with QoS guarantees |
| Scope | Global, many networks | Within one provider's network |
| Cost | Low | Higher (managed service) |
The trade-off is reach and price versus reliability and control. The internet goes everywhere cheaply with no guarantees; MPLS delivers consistency within a provider's footprint at a premium.
Is MPLS Still Relevant?
Very much so, though its role is shifting. MPLS remains central to carrier backbones and large enterprise wide-area networks where predictable latency and traffic engineering justify the cost. What has changed is that many organisations now pair it with SD-WAN, reserving MPLS for the traffic that truly needs guarantees — voice, real-time applications, critical site-to-site links — while routing everything else over cheaper ordinary internet connections. Rather than being replaced, MPLS is increasingly used selectively alongside the public internet it was once an alternative to. It still rides on the same interior routing a provider runs internally; MPLS just decides the forwarding path on top of it.
Frequently Asked Questions
What is MPLS?
Multiprotocol Label Switching — a way to forward traffic through a provider network using short fixed labels instead of an IP lookup at every router. The edge classifies and labels a packet; core routers forward by label along a fixed path; the label is removed at the exit.
How does MPLS work?
An ingress edge router pushes a label; core routers swap the label and forward without reading the IP header; the egress router pops the label and the packet continues as IP. The fixed route is a label-switched path.
Is MPLS a VPN?
Not by itself, but it is widely used to build provider-managed VPNs that link a company's sites over a shared network with predictable performance. These provide separation rather than encryption by default.
What is the difference between MPLS and the public internet?
The internet routes hop by hop by IP with best-effort delivery; MPLS uses engineered paths inside one provider's network with consistent latency and QoS. MPLS offers reliability and control; the internet offers reach and lower cost.
Is MPLS still used?
Yes — in carrier backbones and enterprise WANs needing predictable performance. Many now combine it with SD-WAN, using MPLS for critical traffic and internet links for the rest rather than replacing it.