What kind of Business would need MPLS?

An MPLS Network may not be specifically right for you. If you have just one main site, and two or three remote users it could be the wrong type of network. If you find your business in multiple sites, various offices for example, then an MPLS network would fit better. If you're still using things like point to point leased lines or multiple VPNs over public internet. Then you may wish to re-budget or upgrade. Unlike certiain P2P or VPN Networks, MPLS is, scalable and more easily remotley accessed.

What makes it better than using VPNs?

VPNs are high cost, they're also more vulnerable to attack. They don't give much control about what goes on between them. An MPLS shuts off traffic in and out of the network. It then funnels all traffic into a single internet breakout. Having only a single internet breakout point drastically reduces costs. This also helps with management control. On an MPLS, you can connect multiple sites at once more easily. This allows a back and fourth between multiple locations that would be much harder to achieve in a VPN.

What is the difference between MPLS & SD-WAN?


  • Reliable packet delivery i.e. best for real-time applications – closed network therefore doesn’t traverse the Internet and ensures quality. Packet loss is less than 0.01% on the Spitfire core network, with end-to-end SLAs provided when using Spitfire Ethernet circuits
  • Network security through isolation
  • Centrally managed site-to-site connectivity
  • Quality of Service
  • What about sites or users that sit outside of the MPLS network? Doesn’t that make MPLS far less flexible than SD-WAN? Not so, we can easily incorporate these sites and users by providing access in to the network using IPSec-VPN tunnels. When creating an SD-WAN, virtual network tunnels are created from sites and users to the central software application in a similar way.


  • Uses WAN Virtulisation
  • Often uses multiple ISPs and carrier circuits to create a virtual WAN which is then centrally managed by the SD-WAN software application
  • Easy to manage bandwidth allocation for different applications, however as normally traverses the Internet the packet loss will typically be higher than 1%, making it potentially unsuitable for voice or other real time applications where delivered as a standalone SD-WAN and not over the top of e.g. an MPLS network
  • Although QoS control may be offered on the SD-WAN control software, it is impossible to provide this across the underlying network when delivered over the Internet
  • SLAs are often provided but only for the core part of the provider’s network and not the underlying circuits