Cloud-B

Network and sites

How zones, private networks and the edge are built: what you can configure yourself, and where a support request is required.

Updated 12.11.2026Applies to API v1

Availability zones

Three zones in two Swedish regions. Within a region the zones sit in different halls with independent power feeds and uplinks; between Stockholm and Gothenburg we run dedicated 10 GbE links.

ZoneRegionHypervisorsNetworkPower
sto-1aStockholm, STO1KVM, 6.12 LTS2×25 GbE2N
sto-1bStockholm, STO1KVM, 6.12 LTS2×25 GbE2N
got-1aGothenburg, GOT1KVM, 6.12 LTS2×10 GbEN+1

Inter-zone latency (median, 95th percentile): Stockholm A ↔ B — 0.8 ms (1.4 ms); Stockholm ↔ Gothenburg — 4.5 ms (6 ms). Within a zone — 0.2 ms (0.5 ms).

Private networks

Every VPC is isolated at the hypervisor level. Subnets range from /24 to /29; addresses are assigned over DHCP, and reservations by MAC address are available through the API.

  • The DNS resolver and the metadata service live on service addresses inside the VPC; their values are returned by GET /v1/vpc/networks/{id}.
  • Security groups are stateful: return traffic is allowed automatically, with no separate rule for established connections.
  • Cross-zone routing is enabled with the inter_zone_routing flag; by default a subnet only sees its own zone.
  • The NAT gateway is a separate resource, one per VPC; the outbound address stays fixed for as long as the gateway exists.

Do not use address ranges in a VPC that overlap with your office networks if you plan a VPN or private link: routes will not overlap, and traffic will return to the office.

Public addresses

A public IPv4 address is a floating address: it belongs to the account, not to an instance, and moves between instances in the same zone within seconds. Reverse DNS (PTR) is configured through support; delegation goes through abuse@cloud-b.myftp.org.

Every instance receives a /64 IPv6 prefix. The interface address is assigned over SLAAC; the ::/0 rule in a security group must be opened explicitly, just like IPv4.

MTU and jumbo frames

The external interface is MTU 1500. Inside a VPC the default is also 1500; jumbo 9000 is enabled per network and requires support on both sides. The edge does not fragment packets: ICMP fragmentation needed is passed through, so PMTUD works.

Edge and filtering

Each site filters L3/L4 traffic at the edge and limits new connections. Inbound traffic to 25, 465, 587 and 3306 is blocked by default: this reduces spam and scanning from our addresses.

  • SYN floods and amplification attacks are dropped at the edge; legitimate traffic does not degrade.
  • The new-connection limit is 2,000/s per public IP; above that, SYNs are dropped and logged in the API.
  • ICMP is not blocked: echo-request, time-exceeded and unreachable pass through.
  • Outbound 25/tcp is opened on request, with a description of the mailing and a link to the subscription policy.

Maintenance

Maintenance windows are at night, Central European Time, one region at a time. Planned work that requires a reboot is announced five business days in advance on the status page and by email to the account administrator.

Live migration within a zone runs without stopping an instance; for databases it is done through a failover to a replica. Emergency work is only performed to resolve an incident.

Diagnostics

Inside an instance, mtr, tcpdump and ss are available. If an edge-side trace is needed, include the time, source and destination in the request and we will attach a filtered capture.

To test reachability from the outside, use curl -v --resolve with the address in question: the request then goes to a specific zone, bypassing DNS balancing.

Customers with their own autonomous system can run BGP sessions on the site edge: /24 IPv4 and /48 IPv6, prefix limit 50, MD5 password on request. RIPE objects are registered by the customer. Terms are in the agreement.

Data residency

All customer data, snapshots and backups are stored in Swedish data centres. Personal data is processed under the GDPR and the data processing agreement; transfers outside the EU/EEA do not happen without a separate agreement.