Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

Private Network Subnets

Competitor mapping for Hetzner Cloud.

This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.

Details

Provider
Hetzner Cloud
Service term
Private Network Subnets
Provider documentation
External reference

Behavioral divergences

Private Network Subnets

Quake AI concept: Subnets

  • Hetzner subnets are defined with a network_zone (e.g. eu-central) and an IP range within the parent network CIDR via POST /v1/networks/{id}/subnets; Neutron subnets are independently addressable resources not scoped to zones.
  • Hetzner private networks are limited to 100 servers per network; Neutron networks have no hardcoded server limit (quota-limited by project).
  • Hetzner SDN operates at strictly Layer 3 (no broadcast, multicast, or unknown unicast traffic); Neutron supports L2 broadcast domains with ML2 backends (OVN/OVS).
  • Hetzner subnets cannot be deleted individually while servers are attached; Neutron supports port removal and subnet deletion independently.

Related

Diverges from (incoming)

Citations

  1. Hetzner Cloud
  2. Hetzner Cloud

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.