Skip to content

Connecting to OVHcloud Connect

Megaport makes it easy to provision fast, secure, and private connections to OVHcloud Connect through our global software defined network (SDN). Megaport is an OVHcloud partner providing direct private access to the OVHcloud infrastructure. You can quickly provision connectivity from hundreds of Megaport-enabled locations to OVHcloud Connect regions and OVHcloud Connect Points-of-Presence (PoPs) across North America, Europe, and Asia Pacific.

OVHcloud Connect connection

The benefits of direct connectivity to OVHcloud Connect through Megaport include:

  • Secure, private connectivity throughout Megaport’s redundant network infrastructure. Your traffic will not transit the public internet.
  • High performance and predictability of your network.
  • Improved data and operational security.
  • Flexible and scalable cloud networking options.
  • Consistent connectivity while scaling bandwidth to OVHcloud Connect. This means no downtime when you need to change your Virtual Cross Connect (VXC) speed.
  • Connect to multiple regions from a single interconnection point, which leverages multi-region redundancy at a fraction of the cost.

How it works

OVHcloud Connect consists of a physical network connection at a number of OVHcloud locations. OVHcloud locations reside within facilities operated by co-located data centers where Megaport is enabled.

Physical fiber connections (NNIs) at each location between Megaport and OVHcloud are established to OVHcloud routers. These physical connections are maintained between OVHcloud and Megaport. Connecting to OVHcloud follows these general steps through the Megaport Portal:

  1. Order Ports in Megaport locations of your choice.
    Two Ports are required for redundancy.
  2. Order VXCs to OVHcloud. Bandwidth is available in fixed increments of 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, or 5 Gbps.
    VXCs to OVHcloud are established as a Layer 2 service between OVHcloud and the Port. One VXC from each Port is required for resilience.
  3. After you deploy VXCs in the Megaport Portal, establish Layer 3 BGP peering between your routing equipment and OVHcloud.


OVHcloud Connect is available in these locations:

  • Europe
    • Frankfurt
    • London
    • Paris

You can connect to multiple regions from a single interconnection point (which lets you leverage multi-region redundancy at a fraction of the cost).

For more information on OVHcloud locations, see OVHCloud Connect.


Before you begin, notify OVHcloud. If you are an existing OVHcloud customer, contact your OVHcloud Account Manager and establish an agreement for OVHcloud services. If you are a new customer, you can order from the OVHcloud Connect website. OVHcloud will provide you with a service key that is unique for each cloud peering location interface: one for the primary and one for the secondary cloud peering location interface. The key includes the OVHcloud VLAN ID, speed, and OVHcloud location.

After you notify OVHcloud, ensure you have a Port on the Megaport network. The Port is your interface to the Megaport network, and you will need to deploy a Port wherever you want to direct traffic. For more information, see Creating a Port.

Setting up OVHcloud Connect

The easiest way to create a connection between Megaport and OVHcloud is with a service key. A service key includes the essential configuration details for your business and automates much of the configuration process. After obtaining the service key from OVHcloud, you can create a VXC from the Port to OVHcloud Connect.

To request a connection to OVHcloud in the Megaport Portal

  1. Contact OVHcloud to obtain a service key.


    When you use the service key created by OVHcloud, you are responsible for any VXC charges.

  2. In the Megaport Portal, go to the Services page.
    If you don’t have a Megaport account, see Setting Up a Megaport Account.

  3. Select the Port for the connection and click +Connection.
  4. Click Enter Service Key and click Next.
    New connection
  5. Enter the service key provided by OVHcloud in the Megaport Service Key ID field.
    Enter Service Key
    Megaport validates the key. Data including VLAN ID, speed, and OVHcloud location are included in the key and populate automatically. For more information on using a service key, see Creating a VXC with a service key.
  6. Click Next.

  7. Specify the connection details:

    • Connection Name – The name of your VXC to be shown in the Megaport Portal. Enter a name for the VXC using the label provided by OVH.

    • Service Level Reference (optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.


      Partner-managed accounts can apply a Partner Deal to a service. For more information, see Associating a Deal With a Service.

    • Rate Limit – The speed of your connection in Mbps. The rate limit for the VXC is capped at the maximum allowable based on the OVHcloud Connect service key speed.

    • VXC State – Select Enabled or Shut Down to define the initial state of the connection. For more information, see Shutting Down a VXC for Failover Testing.


      If you select Shut Down, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.

    • Preferred B-End VLAN – This field populates automatically based on the value defined in the service key.

    • Minimum Term – Select No Minimum Term, 12 Months, 24 Months, or 36 Months. Longer terms result in a lower monthly rate. 12 Months is selected by default.
      Take note of the information on the screen to avoid early termination fees (ETF). See VXC Pricing and Contract Terms and VXC, Megaport Internet, and IX Billing for more information.

    OVHcloud connection details

  8. Click Next.
    A summary page appears that includes the monthly cost.
    OVHcloud connection details

  9. Click Add VXC to move this configuration to your cart.
  10. Repeat these steps to provision your secondary OVHcloud interface.
  11. Click Order to continue through the checkout process.
    OVHcloud connection details
  12. Review the Order Services agreement and click Order Now.

Once the VXC connection is deployed to OVHcloud, a single VLAN is assigned from your Megaport Portal account, with Layer 3 networking routing established using BGP between your physical network device and OVHcloud. Connections are private peering types, and will use private IPv4 addresses.


To establish full redundancy between your data center and OVH, we recommend deploying redundant VXCs between two different OVHcloud locations with two corresponding Ports at each Megaport-enabled data center.

Redundant solution

OVHcloud redundant connection

Fully redundant solution

OVHcloud fully redundant connection

Updating the service bandwidth

You can scale the service speed up to the OVHcloud Connect speed rate at any time. If you require additional capacity, you must place an order for a new connection speed on the website.

To change the OVHcloud Connect speed, you must delete the Cloud Connect and VXC connections, and then recreate them.

OVHcloud Frequently Asked Questions (FAQs)

Are there any OVHcloud port fees?
OVHcloud Connect doesn’t charge for data transfer. Customers pay a flat, auto-renewable monthly rate.

What services are available using OVHcloud?
OVHcloud offers Private Cloud based on VMware platform, Bare Metal servers, Public Cloud based on Openstack and PaaS services as Kubernetes Managed, and Databases as a Service.

What if I’m not located within an OVHcloud PoP?
You don’t have to be located within the same facility as OVHcloud; you can establish a VXC to the closest OVHcloud Connect location of your choice. Each VXC is carried across Megaport’s redundant network to OVHcloud.

Does OVHCloud Connect support public or private ASNs?
OVHcloud Connect supports public and private autonomous system numbers (ASNs). If you are using a public ASN, you must own it. If you are using a private ASN, it must range from 64512 to 65535. AS path prepending does not work if you are using a private ASN for your public VIF. When you place your order, you can specify your preference for private or public ASNs. The OVHcloud connection is private, but customers can peer with their private or public ASN and an OVHcloud private ASN of their choosing.

Helpful references

Last update: 2024-04-15