---
title: VPC Peering - Quickstart
description: Get started quickly with Scaleway VPC Peering. Follow our step-by-step guide to configure and deploy a secure connection between your two Scaleway VPCs in minutes.
tags: vpc-peering, networking, private-connection, secure-connectivity, cross-project, cross-organization, custom-routes
dates:
  creation: 2026-05-12
  validation: 2026-05-12
---

import peeringDiag from './assets/scaleway-vpc-peering-diag.webp'

import Requirements from '@macros/iam/requirements.mdx'

Scaleway VPC Peering is a networking service that enables two Scaleway VPCs to establish a private peering connection. You can then securely route traffic between them, away from the public internet.

<Lightbox image={peeringDiag} alt="A graphic shows how two different VPCs each create a peering connector, which enables them to communicate over a peering connection." />

For full details about VPC Peering, refer to [Understanding VPC Peering](/vpc-peering/reference-content/understanding-vpc-peering/).

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- [Created a VPC](/vpc/how-to/create-vpc)
- The unique VPC ID of the VPC you want to peer with
- [Activated routing](/vpc/how-to/manage-routing/#how-to-activate-routing) on both VPC peers

## How to create a peering connector

1. Click **VPC Peering** in the **Network** section of the [Scaleway console](https://console.scaleway.com/organization) side menu.

2. Click **+ Create a peering connector**. The peering connector creation wizard displays.

3. Choose a region in which to create your peering connector.

4. Select an origin VPC from the current Scaleway Project using the drop-down menu.

5. Enter the ID of the target VPC you want to peer with. The target VPC can be in a different Project/Organization.

6. Enter a **name** for your connector, or use the automatically-generated one. Optionally, you can also add **tags** to help organize your resources. Each tag should be separated by a space.

7. Click **Create a peering connector** to finish.

        <Message type="tip">
        Both VPCs must be in the same Scaleway region. They may be in different Projects/Organizations. The target VPC must be identified by its unique VPC ID.
        </Message>

        The peering connector will be in `Orphan` status, until the next step is carried out.

8. An owner or manager of the target VPC must create a matching peering connector on their end, defining their VPC as origin and your VPC as target.

        <Message type="tip">
        They will not receive any requests or notifications prompting them to create the matching connector. They must do this autonomously and independently.
        </Message>

9. Scaleway detects that two matching peering connectors have been created, and automatically carries out a compatibility check to ensure the Private Networks of the two VPCs do not contain any overlapping CIDR blocks.

        - If the two VPCs are compatible, both connectors go into `Peered` status, and the peering connection is created.
        - If the two VPCs have overlapping CIDR blocks, both connectors go into `Conflict` status. They cannot be peered until you [resolve the conflict](/vpc-peering/troubleshooting/resolving-peering-conflicts/).

## How to create custom routes

Once both connectors are in a `Peered` status, you must add custom routes to the route table of each peered VPC to establish rules for routing traffic for the IP ranges you specify, across the peering connection.

<Message type="note">
Creating custom routes is an essential step for facilitating the flow of traffic across the peering connection. Traffic will not be routed between the peered VPCs automatically or via any auto-created, managed routes.
</Message>

1. Click **VPC** in the **Network** section of the Scaleway console side menu. A list of your VPCs displays.

2. Use the **region selector** at the top of the page to filter for the region of the VPC where you want to define a custom route, then click the VPC. A list of Private Networks in this VPC displays.

3. Click the **Routing** tab.

4. Click **Create route**. The custom route creation wizard displays.

5. Enter a **description** for your route, e.g. "Route to peered VPC".

6. Enter a **destination** for the route. The VPC will apply the route to all traffic with a matching destination IP. You must enter an IPv4 or IPv6 CIDR range with a subnet mask, e.g. `192.168.1.0/24`.

7. Choose **Peering connector** as the **next hop** for the route, then select the desired peering connector from the drop-down list. The VPC will route traffic for the destination IP to the selected entry.

8. Click **Create route** to finish.

Your new route now displays in the **Routing** tab of your VPC. A matching custom route must be added to the target VPC for traffic to flow between the peered VPCs. The destination of that return route must be a subnet that contains the IP address(es) of the resources in the origin VPC that need to reach the peered side.

## How to delete a peering connector

1. Click **VPC Peering** in the **Network** section of the [Scaleway console](https://console.scaleway.com/organization) side menu. A listing of your peering connectors displays.

2. Use the **region selector** at the top of the page to filter for the region of the peering connector you want to delete.

3. Click <Icon name="more" /> next to the peering connector you want to delete, and select **Delete** from the drop-down menu.

4. Type **DELETE** in the box to confirm, then click **Confirm**.