> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCR Overview

> This help topic describes the functionality and specifications of the Megaport Cloud Router (MCR).

The MCR is a managed virtual router service that establishes Layer 3 Glossary Layer 3 Layer 3 of the OSI model is the network layer. It translates logical network address into physical machine address (IP addressing). Layer 3 routers analyze traffic based on address details and forward appropriately, requiring knowledge of the details generally exchanged in BGP sessions for routing table exchanges. connectivity on the worldwide Megaport software-defined network (SDN). MCR instances are preconfigured in data centers in key global routing zones. An MCR enables data transfer between multicloud Glossary multicloud The use of multiple cloud computing services in a single heterogeneous architecture. For example, an enterprise might use multiple cloud providers for infrastructure (IaaS) and software (SaaS) services. One of Megaport's core value propositions is enabling multicloud connectivity. or hybrid cloud networks, network service providers, and cloud service providers.

An MCR instance is not physically cross-connected like a Port in the Megaport network. However, it can host Layer 2 Glossary Layer 2 Layer 2 of the OSI model is the data link layer. This provides node-to-node data transfer (a link between two directly connected nodes). Most Megaport Virtual Cross Connects (VXCs) operate at this layer. Layer 2 is divided into Media Access Control (MAC) layer (controls how devices in a network gain access to medium and permission to transmit), and Logical Link Control (LLC) layer (responsible for identifying network layer protocols and then encapsulating them and controls error checking and frame synchronization). VXC connections just like a physical Port and it can extend to any other Port in the Megaport network or another MCR.

## How it works

An MCR joins two or more independent Virtual Cross Connect (VXC) services into a single routing domain, providing connectivity between all the VXCs attached to the MCR.

Without physical infrastructure, you can use cloud-to-cloud networking, private peering between leading public Cloud, IaaS Glossary IaaS Infrastructure as a Service (IaaS) is a cloud computing model that delivers virtualized computing resources over the internet. IaaS abstracts users from managing physical infrastructure, handling compute, storage, networking, scaling, security, and backup. It is the most foundational cloud service model for providers offering cloud computing infrastructure, as defined by the Internet Engineering Task Force (IETF)., and SaaS Glossary SaaS Software as a Service (SaaS) is a form of cloud computing in which the provider offers the use of application software to a client and manages all the physical and software resources used by the application. SaaS is sometimes referred to as “on-demand software” and is usually priced on a pay-per-use basis or using a subscription fee. providers, and direct connectivity to any provider on the Megaport software-defined network (SDN). There is no need to own and maintain equipment. MCR removes the complexity of getting connected at Layer 3 and opens up new possibilities for virtualized networking.

![MCR overview](https://docs.megaport.com/images/mcr/multicloud.png)

You can use an MCR instance either with or without a physical Port in the Megaport network. If you want to configure multi-region deployments with a single Cloud Service Provider (CSP), or a multicloud deployment with multiple CSPs, MCR can enable both functionalities. Combining MCR functionality with a physical Port in the Megaport network has added benefits:

* Reduced latencies by enabling direct connections among cloud providers.
* Inter-region or inter-cloud connectivity to control and localize traffic.

For more information, see [Configuring an MCR](https://docs.megaport.com/mcr/configuring-mcr.md).

## Speed tiers

The MCR speed options are consolidated into these tiers:

| **Speed Tier** | **Symmetric Throughput** | **Asymmetric Throughput** |
| - | - | - |
| 1 Gbps | 0.5 Gbps/0.5 Gbps | 1 Gbps |
| 2.5 Gbps | 1.25/1.25 Gbps | 2.5 Gbps |
| 5 Gbps | 2.5/2.5 Gbps | 5 Gbps |
| 10 Gbps | 5/5 Gbps | 10 Gbps |
| 25 Gbps | 12.5 Gbps / 12.5 Gbps | 25 Gbps |
| 50 Gbps | 25 Gbps / 25 Gbps | 50 Gbps |
| 100 Gbps | 50 Gbps / 50 Gbps | 100 Gbps |

> [!NOTE]
>
> If higher throughput multicloud connectivity is required, please contact your Megaport Account Manager or Customer Success Manager to discuss alternative or early adopter options.

## Helpful references

* [Creating an MCR](https://docs.megaport.com/mcr/creating-mcr.md)
* [Enabling Cloud-Native VPN/Encryption Options Over Dedicated Cloud Connectivity Paths](https://docs.megaport.com/encryption/cloud-native-vpn-encryption.md)
* [Using IPsec with Megaport](https://docs.megaport.com/encryption/ipsec.md)
* [Using MACsec with Megaport](https://docs.megaport.com/encryption/macsec.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.