Overview

Private Networking connects instances over an isolated Layer 2 LAN that is not reachable from the public internet. Traffic inside a private network is unmetered. The network interface is configured automatically when an instance joins a network.


Availability

ProductPrivate Networking
VPS (Core, Performance, Storage)Add-on per instance
VDS (Max Performance VPS)Provisioned manually by support on request (support ticket)
GPU VPSAdd-on per instance

Specifications

AspectDetails
IsolationLayer 2 LAN, fully isolated from other customers and the public network
TrafficUnlimited and unmetered within the private network
Network sizeUp to /22 (1,024 addresses) per network
Networks per instanceAn instance can belong to multiple private networks
Networks per accountNo stated limit
ScopeOne region per network; only instances in the same region can be added
IP assignmentPrivate IP addresses assigned automatically
ManagementControl Panel, API and CLI

Activation

  1. Enable the Private Networking add-on on each instance that should join.
  2. Create a network in the Control Panel with a name and region.
  3. Select the instances to add.
  4. Restart each instance to activate the network interface — data is preserved.

For VDS, private networks are not self-service: request them via a support ticket, and support provisions them manually.


Limitations & Notes

  • Not offered as a Control Panel add-on for Dedicated Servers; a Dedicated Private Network is available on request.
  • Private networks are limited to one region; instances in other regions cannot join.
  • There is no built-in firewall for private networks; restrict access with the firewall inside the OS. The Contabo Firewall applies to public traffic only.
  • If the instance runs on a host that does not support Private Networking, activation requires an OS reinstall — all data is erased and the public IP address changes. Contact support if an instance does not appear in the network after the restart.