I am experiencing connectivity or routing issues with my VPC or Private Network

Reviewed on August 26, 2025

You may have problems with connectivity between resources in a VPC or Private Network, or issues with routing packets.

This page helps you solve potential errors that are related to VPC connectivity and routing.

I cannot deactivate routing on my VPC

This is standard behavior:

Once you have activated routing on a VPC, you cannot deactivate it
You do not have the option to create a new VPC where routing is deactivated

I am experiencing issues with Elastic Metal server connectivity to a Private Network

Note that some manual configuration of the network interface is required when attaching Elastic Metal servers to Private Networks. Follow the steps in our dedicated documentation.

I am experiencing issues with VM (hosted on Elastic Metal server) connectivity to a Private Network

Ensure you have correctly attached the VM to the Private Network by specifying the MAC address, and carried out the necessary configuration of the network interface for your VM, e.g. via the Proxmox interface.

Tip

Using the same MAC address on VMs in different AZs, or switching such MAC addresses between AZs, is not compatible with VPC routing. Ensure each VM has a unique MAC address.

My resources cannot communicate via their hostnames

See our dedicated documentation on resolving private DNS errors.

I am experiencing other connectivity issues

Check the Scaleway Status page, to see whether there are any ongoing incidents which could affect the connectivity or network access of your resources.

Carry out our recommended tests for thorough connectivity troubleshooting and resolution.

Still need help?

Create a support ticket