OVHcloud Connect - Frequently Asked Questions (FAQ)
Find answers to the most common questions about OVHcloud Connect
General
What is OVHcloud Connect?
OVHcloud Connect (OCC) is a dedicated, private network connection between your infrastructure and OVHcloud. It bypasses the public internet, providing lower latency, higher bandwidth, and improved security compared to VPN or internet-based connections.
See What is OVHcloud Connect? for a full overview.
What is the difference between Direct and Provider?
Which providers are supported?
OVHcloud Connect Provider works with:
- Megaport — VXC and MCR (Cloud Router)
- Equinix Fabric — Virtual connections
- Console Connect (PCCW Global) — On-demand connections
See Providers for details.
Where is OVHcloud Connect available?
OVHcloud Connect is available in major PoP locations across Europe, North America, and Asia-Pacific. See PoP locations and regions for the full list.
Can OVHcloud host my router?
No. OVHcloud does not host customer networking equipment. To use OVHcloud Connect Direct, you must have your own rack space (a bay) in a data centre where OVHcloud has a point of presence, with your router installed and operated by you. You can then order an OVHcloud Connect Direct service and a cross-connect between your bay and the OVHcloud PoP within that facility.
If you do not have a presence in an OVHcloud PoP, use OVHcloud Connect Provider instead — your provider handles the last-mile connectivity on your behalf.
Ordering & billing
How do I order OVHcloud Connect?
- Direct: Order a Direct connection
- Provider: Order a Provider connection
You can order through the OVHcloud Control Panel, the API, or Terraform.
How long before my OVHcloud Connect service is delivered?
Direct:
- The Letter of Authorization (LOA) is issued within minutes of the order.
- You then have 60 days to finalise the interconnection: order the cross-connect from your data centre operator, and physically connect your equipment to the OVHcloud patch panel.
- The service is delivered as soon as OVHcloud detects light on the port. If no light is detected within 60 days, the service is nevertheless considered operational and billing starts.
Provider:
- OVHcloud generates a pairing key (service key) immediately after the order.
- The service is delivered as soon as your provider consumes the pairing key and provisions the virtual circuit — typically within minutes to hours for on-demand providers such as Megaport, Equinix Fabric, or Console Connect.
How is OVHcloud Connect billed?
OVHcloud Connect is billed monthly based on:
- Connection type (Direct or Provider)
- Bandwidth (from 50 Mbps to 100 Gbps)
- Number of services
Provider connections may also incur charges from the provider (Megaport, Equinix, etc.). Check the OVHcloud pricing page for current rates.
Can I upgrade bandwidth without downtime?
No. Bandwidth changes require ordering a new service at the desired speed and migrating traffic. Plan the migration during a maintenance window.
How do I cancel a service?
- Direct: Cancel a Direct connection
- Provider: Cancel a Provider connection
Important: Always remove the provider virtual circuit and BGP configuration before cancelling the OVHcloud service to avoid routing issues.
Technical
What BGP ASN does OVHcloud use?
OVHcloud uses ASN 35540 for OVHcloud Connect BGP peering. You must configure your side with a different ASN (typically a private ASN in the 64512–65534 range).
What is the maximum number of BGP prefixes?
OVHcloud supports a maximum of 100 prefixes per BGP session. Aggregate your routes to stay within this limit. If you need more, contact OVHcloud support.
Does OVHcloud Connect support IPv6?
Currently, OVHcloud Connect primarily supports IPv4. Check with OVHcloud support for the latest IPv6 availability.
What MTU is supported?
The default MTU is 1500 bytes. Jumbo frames (9000 bytes) may be supported on Direct connections depending on the PoP — confirm with OVHcloud support before configuring.
Can I use OVHcloud Connect with Hosted Private Cloud (VMware)?
Yes. Associate your OVHcloud Connect service with a vRack, then add your Hosted Private Cloud service to the same vRack. VMware VMs can use the private connection via vRack-attached port groups.
Can I use OVHcloud Connect with Public Cloud instances?
Yes. Attach your Public Cloud project to the same vRack as your OVHcloud Connect service. Assign a vRack private network to your instances to route traffic through the OCC link.
What happens if my BGP session goes down?
If you have a single OVHcloud Connect link, traffic between your network and OVHcloud will stop flowing until BGP is re-established. For production workloads, always use a resilient architecture with two links and BGP failover.
Can I use BFD (Bidirectional Forwarding Detection)?
BFD support depends on the OVHcloud Connect type and PoP. Contact OVHcloud support to confirm BFD availability for your service. BFD can significantly reduce failover times from ~90 seconds to under 1 second.
Multi-cloud
Can I connect AWS, Azure, and GCP to OVHcloud simultaneously?
Yes. Order separate OVHcloud Connect Provider services and bridge each to the respective cloud:
All can be associated with the same vRack, allowing traffic to flow between all clouds through OVHcloud.
Can cloud-to-cloud traffic transit through OVHcloud?
Technically, if all cloud connections share the same vRack and BGP prefixes are exchanged, traffic could transit through OVHcloud. However, this is not recommended for production — use dedicated cloud-to-cloud interconnects (e.g., AWS ↔ Azure) for direct inter-cloud traffic.
Do I need a separate vRack for each cloud connection?
No. You can associate multiple OVHcloud Connect services with the same vRack. This allows all connected networks (on-premises, AWS, Azure, GCP) to communicate through the shared vRack.
Resilience & SLA
What SLA does OVHcloud Connect offer?
SLA levels depend on your architecture:
See SLAs for full details and conditions.
How do I set up a resilient connection?
Order two OVHcloud Connect services at different PoPs, associate both with the same vRack, and configure BGP failover with Local Preference and AS-path prepending.
Tutorials:
How long does BGP failover take?
With default BGP timers (hold time = 90 seconds), failover can take 30–90 seconds. With aggressive timers or BFD enabled, failover can be under 1 second.
Troubleshooting
My connection is ordered but not active
I can see the BGP session but have no reachability
- Verify that routes are being exchanged (check
show ip bgp summaryor the OVHcloud API). - Ensure subnets are correct and non-overlapping.
- Check for firewall rules blocking traffic on either side.
- Verify VLAN tagging matches between your equipment and OVHcloud.
Traffic is slow or experiencing packet loss
- Check interface errors and CRC counts on your router.
- Verify the bandwidth of your OVHcloud Connect matches your traffic load.
- Look for MTU mismatches causing fragmentation.
- Use the monitoring guide to check link health.
How do I open a support ticket?
- Go to the .
- Click Support → Create a ticket.
- Select Network → OVHcloud Connect.
- Include your service name, error details, and any diagnostic output.
See Incident follow-up for detailed escalation procedures.
Automation
Can I manage OVHcloud Connect with Terraform?
Yes. Use the OVHcloud Terraform provider (version ≥ 2.7.0) to manage OVHcloud Connect resources. See Automation for examples.
Is there an API for OVHcloud Connect?
Yes. The OVHcloud API provides full lifecycle management:
- EU endpoint:
https://eu.api.ovh.com/v1/ovhCloudConnect/ - CA endpoint:
https://ca.api.ovh.com/v1/ovhCloudConnect/
Explore the API at api.ovh.com/console.
See Automation for SDK and API examples.
Still have questions?
- Browse the full documentation
- Check the OVHcloud Community
- Contact via the Control Panel
Go further
For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analyzed by our experts.
Join our community of users.