# Exoscale Documentation — Private Connect > Private Connect: connect your on-premises or hosted infrastructure to one or more private networks of an Exoscale organization. --- url: https://community.exoscale.com/product/networking/private-connect/ --- # Private Connect - [Quick Start - Private Connect](https://community.exoscale.com/product/networking/private-connect/quick-start/index.md) - Get started quickly with a guided setup to achieve your first successful use of the service, including the required steps and configuration. - [Overview - Private Connect](https://community.exoscale.com/product/networking/private-connect/overview/index.md) - Terminology and key features at a glance, learn the core concepts, capabilities, and options of this service before you dive deeper. - [How-To - Private Connect](https://community.exoscale.com/product/networking/private-connect/how-to/index.md) - Exoscale Private Connect how-to guides for configuring private networking, connections, and common setup tasks. - [Service Boundaries - Private Connect](https://community.exoscale.com/product/networking/private-connect/service-boundaries/index.md) - Service boundaries: quotas, limits, and the guaranteed service levels (SLA) for this product, including key constraints to plan and operate reliably. - [Reference - Private Connect](https://community.exoscale.com/product/networking/private-connect/reference/index.md) - Reference documentation for API, CLI, and tools, browse comprehensive details, parameters, commands, and integration notes. --- url: https://community.exoscale.com/product/networking/private-connect/quick-start/ --- # Quick Start - Private Connect You can contact our Sales team for information on Exoscale carrier partners. The connection from your WAN or MAN link to Exoscale from the carrier needs to be established via a carrier-to-carrier cross connection. Exoscale will provide a location, circuit-ID and letter of agreement (LOA) upon subscribing to Private Connect. Note that no carrier termination equipment can be hosted by Exoscale on your behalf. --- url: https://community.exoscale.com/product/networking/private-connect/overview/ --- # Overview - Private Connect Private Connect lets you connect your on-premises or hosted infrastructure with one or more private networks from a single Exoscale organization. This guide will show you how to set up Private Connect. ## Terminology MAC (Media Access Control) : A unique hardware address assigned to a network interface for communication on a local network WAN (Wide Area Network) : A network that spans a large geographic area, connecting multiple LANs MAN (Metropolitan Area Network) : A network that covers a city or campus, larger than a LAN but smaller than a WAN HSRP (Hot Standby Router Protocol) : A Cisco protocol that provides gateway redundancy by designating active and standby routers VRRP (Virtual Router Redundancy Protocol) : An open standard for assigning a virtual IP to multiple routers for gateway failover LCAP (Local Cloud Access Point) : A physical interconnect location enabling private, low-latency cloud access ## Features Your situation to start with Private Connect can differ depending on where you store your infrastructure. If your infrastructure is collocated in the __same datacenter or datacenter campus__ as the Exoscale zone: - The connection to Private Connect can be established via cross connections between Exoscale and your racks/cage within the datacenter. You are responsible for the cross connections setup and costs. Exoscale will provide a location, circuit-ID and letter of agreement (LOA) upon subscribing to Private Connect which let you order the cross connections to the datacenter operator. - The connection in Equinix-based zones can be established using Equinix Cloud Exchange to reduce cross-connection costs and Private Connect costs. After you subscribe to Private Connect, Exoscale will provide the ECX information for interconnection. If your infrastructure is located __in a separate datacenter__ from the Exoscale zone a WAN or MAN connection is required. --- url: https://community.exoscale.com/product/networking/private-connect/how-to/ --- # How-To - Private Connect Step-by-step guides to configure the service and use specific features, with clear instructions for common tasks and problem solving. - [Set Up Private Connect Network](https://community.exoscale.com/product/networking/private-connect/how-to/setup-network/index.md) - Set up Private Connect networking with single or dual links for redundancy, plus optional extra links for more capacity and failover. - [Set Up Private Connect Routing](https://community.exoscale.com/product/networking/private-connect/how-to/setup-routing/index.md) - Set up Private Connect routing to stay within MAC address limits, route Exoscale IP ranges correctly, and support link redundancy or failover. - [Set Up Private Connect Routes](https://community.exoscale.com/product/networking/private-connect/how-to/setup-routes/index.md) - Set up Private Connect routes between your servers and Exoscale instances when internet and Exoscale traffic use different routers. --- url: https://community.exoscale.com/product/networking/private-connect/how-to/setup-network/ --- # Set Up Private Connect Network When you set up the network connection, you can choose to create a single non-redundant link, or a dual link for redundancy. You can also add two additional links for more capacity. ![](private-connect-hardware.svg) When you choose the dual-link option, the link can be aggregated using LACP, or a failover can be done by using HSRP/VRRP on your routers to fail over the IP address. --- url: https://community.exoscale.com/product/networking/private-connect/how-to/setup-routing/ --- # Set Up Private Connect Routing When you send data to the Exoscale network, you have a limit of 3 MAC addresses. Any traffic coming from your network cannot originate from more than 3 MAC addresses. ![](private-connect-network.svg) Therefore, it is recommended that you **set up routing** on your end instead of using a layer 2 connection. When you set up routing, your servers **must** route your Exoscale IP range (10.0.0.0/24 in the example above) through the routers connected to Exoscale. This is especially important if your Exoscale-connected routers are not your default gateway. Also note that from a networking perspective, the Exoscale networking equipment will not be visible; it will appear as if your Exoscale private network was connected to your router on a layer 2 network without any additional routers in-between.The routing on your end is only needed to ensure compatibility and that there are never more than 3 MAC addresses visible on the Private Connect link. As mentioned before, you can opt to use LACP for link aggregation, or you can use HSRP/VRRP to fail over the IP address between the two links. It is important to note that the IP must never be visible on both links at the same time with this option as this might cause a loop or bad performance. --- url: https://community.exoscale.com/product/networking/private-connect/how-to/setup-routes/ --- # Set Up Private Connect Routes Once your connection to Exoscale is established, you need to configure your instances. If your servers use the same router for internet access and Exoscale connectivity, you do not have to do anything. However, if you use different routers, you will need to set up a route on each server to reach your Exoscale instances. On Linux, this route configuration would look as follows: ```bash ip route add 10.0.0.0/24 via 192.168.1.1 ``` > [!NOTE] > the command above will not store the route permanently and the command is specific > to your Linux distribution. Please consult your Linux distribution's manual on how > to store this route permanently. ![](private-connect-route-onprem.svg) On the Exoscale side you have two options. One option is if you send your traffic to the internet over the public Exoscale network, you will have to set up a separate route to reach your servers: ```bash ip route add 192.168.0.0/24 via 10.0.0.1 ``` ![](private-connect-route-exoscale.svg) The other option is if you send all internet traffic over your own router, the route is already in place. No further action is necessary. --- url: https://community.exoscale.com/product/networking/private-connect/service-boundaries/ --- # Service Boundaries - Private Connect - [Limits and Quotas - Private Connect](https://community.exoscale.com/product/networking/private-connect/service-boundaries/limits-and-quotas/index.md) - Private Connect Limitations and Quotas - [SLA - Private Connect](https://community.exoscale.com/product/networking/private-connect/service-boundaries/sla/index.md) - Private Connect Service Level Agreement - [Pricing ↗︎](https://www.exoscale.com/pricing/#network) --- url: https://community.exoscale.com/product/networking/private-connect/service-boundaries/limits-and-quotas/ --- # Limits and Quotas - Private Connect ## Limits The limitations for Private Connect are: - 3 MAC Addresses maximum per link - Routing element on your side - Optical connections only ## Quotas No Quotas. ## Availability Private Connect is available in all zones. --- url: https://community.exoscale.com/product/networking/private-connect/service-boundaries/sla/ --- # SLA - Private Connect These product-specific SLAs define the Service Availability Target for Private Connect. It applies to each Client using the Service. Capitalized terms used herein but not defined herein shall have the meanings set forth in the Exoscale Terms and Conditions or EUSA, whichever applies. ## SLA Definitons | Metric | Target | Definition | | -------- | -------- | ------------ | | Single port availability | >= 99.5% Monthly Uptime Percentage | The percentage of time in a calendar month that the service is available for external connectivity, for a Private Connect provisioned with a single, non-redundant link. | | Dual port availability | >= 99.99% Monthly Uptime Percentage | The percentage of time in a calendar month that the service is available for external connectivity, for a Private Connect provisioned with a redundant [dual link setup](https://community.exoscale.com/product/networking/private-connect/how-to/setup-network/index.md). | ## Product Specifications For detailed product features, technical specifications, and tutorials, please refer to the [Exoscale documentation](https://community.exoscale.com/product/networking/private-connect/index.md). ## Client Responsibilities While Exoscale is responsible for operating and maintaining the Private Connect service, Clients remain responsible for the following: - On-premises network equipment configuration - BGP session management and routing policies - Network address planning and IP allocation - Redundancy setup for dual-port configurations For a complete explanation of the shared responsibility framework between Exoscale and Clients, please see the [Exoscale Shared Responsibility Model documentation](https://community.exoscale.com/platform/compliance/shared-responsability-model/index.md). ## Exclusions For the complete list of SLA exclusions, please refer to the [General Exoscale Terms and Conditions](https://www.exoscale.com/terms/). ## Retribution The standard retribution and SLA credit schemes apply for this product as described under [General Exoscale Terms and Conditions](https://www.exoscale.com/terms/) or [EUSA](https://www.exoscale.com/eusa/) whichever applies. In the event that the Monthly Uptime Percentage for Exoscale Private Connect falls below the Service Level Objective committed for the applicable setup, the Client will be eligible for service credits as follows: | Setup | Monthly Uptime Percentage | Service Credit Percentage of Monthly Service Fees for Affected Resources | | -------- | -------- | -------- | | Single port | from 99.5% to 98.3% | 50% | | Single port | below 98.3% | 100% | | Dual port | from 99.99% to 98.3% | 50% | | Dual port | below 98.3% | 100% | ### Claim Service Credit To request a service credit, refer to the Service Unavailability Credit section of the [Exoscale Terms and Conditions](https://www.exoscale.com/terms/) or the [EUSA](https://www.exoscale.com/eusa/), whichever applies. --- url: https://community.exoscale.com/product/networking/private-connect/reference/ --- # Reference - Private Connect - [FAQ](https://community.exoscale.com/product/networking/private-connect/reference/faq/index.md) - Find answers about Private Connect bandwidth, link limits, MAC address constraints, routing requirements, and supported network setups. --- url: https://community.exoscale.com/product/networking/private-connect/reference/faq/ --- # FAQ Private Connect enables secure networking with specific constraints on bandwidth, MAC addresses, and connectivity configurations. It requires routing on the client-side. How many links can I use in an LACP setup? : You can use a maximum of 4 links at 10 Gbit/s in a single LACP group, or in two LACP groups if you use VRRP/HSRP. How much is the maximum bandwidth I can reach? : The maximum bandwidth we provide over private connect is 20 Gbit/s. How many MAC addresses can I use to send traffic over Private Connect? : Your routers can send packets originating from a maximum of 3 MAC addresses. If you use more MAC addresses, it will cause connectivity issues. Can I use a switch instead of a router on my end? : Unfortunately, we only support the routing scenario at this time. Can I terminate Private Connect directly on my server? : Yes, as long as that server is configured as a router. Can I use Spanning Tree over Private Connect? : No, and be aware that Spanning Tree over Private Connect will **immediately disable** the network port for stability reasons. Can Exoscale advertise my IP range to my routers over BGP/ISIS/OSPF? : No, Private Connect is a pure Layer 2 connection to your router. No routing is done inside of Exoscale. In fact, Exoscale doesn't even know the IP range you use in the Private Network. Can Exoscale host my server or networking equipment inside the Exoscale racks? : Sorry, no. We cannot do this due to space concerns.