Transparent traffic pricing

Traffic on private networks within the same data center is unmetered.

Inbound traffic is unmetered. Only outbound traffic is metered. All our plans includes an amount of 30 TB outbound traffic.

Outbound data traffic utilization in excess of traffic included as part of the product, is billed at the end of the month, on a per GB basis.

Outbound Traffic below 30TB

0.00 per GB

Outbound Traffic above 30TB

0.01 per GB

Data Center Interconnect

0.005 per GB

If you need to push a lot of traffic, please contact us to get a customized bandwidth plan based on your needs.

Data Center Networks

Our network holds a pivotal role in our data centers. We design our data center networks using open standards and industry-current best practices. Each data center has an identical design, meaning we can provide the same high quality and services across our three locations in Denmark and Germany.

Our network consists of an all Layer 3 spine-leaf architecture using equal-cost multipath (ECMP), enabling us to simultaneously utilize all available paths in the network. With an active/active, non-blocking infrastructure, we can provide all the available bandwidth while simultaneously benefiting from higher availability in a failure scenario.

100G Top of Rack Switches

Our racks are equipped with 100 Gbit/s Top-of-Rack switches for high availability, bandwidth intensive and low-latency applications.

Server Connectivity

We support a wide array of port options. 1 Gbit/s ports are a default and we have options for 10 Gbit/s and 100 Gbit/s ports.

Bare-metal VPC

We have built a bare-metal VPC solution to provide the optimal conditions for running multiple Kubernetes clusters while maintaining security, isolation, and interconnection between tenant and service networks.

Hardware Accelerated

Typical VPC solutions use commodity x86 servers to forward and encapsulate tenant traffic in the CPU. Our bare-metal VPC solution allocates all resources physically in the network switching and routing hardware, saving your cluster nodes from spending precious resources while achieving low latency and wire-speed forwarding capacity between nodes and services.

Increased security

Micro-segmentation of cluster networks allows finer granularity when defining network security policies. And with confinement between the servers and the network forwarding logic, we can eliminate a compromised host's risk of breaking out of its tenant isolation.

Software Defined Networks (SDN)

Our bare-metal VPC allows the provision of different network resources on-demand using your Dashboard or our Public API , including:

  • Layer 2 (VLAN)
  • Layer 3 (VRF)
  • Routing (BGP and Static)

Flexible WAN

By allowing the nodes a direct WAN interface, without NAT, we can provide extremely flexible solutions for IP, BGP and high internet bandwidth applications.

Internet Connectivity

As a LIR member of RIPE NCC with AS30736, we are running our own routed network in an N+1 redundant environment, connected to multiple powerful upstream carriers.

All our data centers run at least two independent border routers, each connected to a number of different Tier 1 IP transit providers. We are also present on several Internet Exchange points. Learn about our data centers .

We support both IPv4 and IPv6 natively in dual stack.

Transit

Having multiple Tier 1 IP transit providers ensures great Global Internet connectivity.

Peering

To achieve the best possible local and regional connectivity, we connect to local Internet Exchange (IX) points to exchange traffic directly with other local providers. Many of which are local ISPs, ensuring the shortest possible path for local businesses and homes.

We are present on the following Internet Exchange Points:

  • Netnod IX
  • NLix

Kubernetes network policies

You can control the internal network flow between applications and incoming/outgoing internet traffic by utilizing Kubernetes network policies. The official guidelines on how to work with network policies apply to our clusters too; you can find documentation on how to use it here:

Official Kubernetes Network Policies