One dedicated IPv4 address is included with each server.
250 Mbps is included; 1 Gbps and 2 Gbps are available at an additional cost. All tiers use the same unmetered billing model. The difference is the selected port speed and monthly surcharge. Choose one tier per server; speeds are not combined.
No bandwidth surcharge
Well suited to websites, APIs and middleware. Compare the port speed included with the peak outbound rate of existing workloads to see whether it can handle everyday traffic and backend data transfers.
+$244/month
Suitable for downloads, content delivery and cross-border traffic. For sustained file transfers or multiple concurrent requests returning large responses, estimate demand from concurrent connections and target throughput per connection.
+$740/month
Suitable for high-concurrency media delivery and image synchronisation. Consider aggregate throughput across concurrent transfers and peak demand when image updates, file syncs and live traffic overlap.
These amounts are monthly bandwidth add-ons, not the monthly server price. Server models, additional drives, extra IPv4 addresses and OS licences are itemised on the pricing and configuration pages.
Bandwidth is billed by port speed, not monthly data transfer. With an unmetered tier, the key planning question is how much data needs to move at the same time—not the total transferred over a month.
| Item | What this page specifies | What to consider before configuring |
|---|---|---|
| Port speed | Choose one tier: 250 Mbps, 1 Gbps or 2 Gbps | Estimate concurrent workload traffic and choose a tier based on peak demand. |
| Monthly data transfer | Unmetered on every tier; no monthly usage charges | Ongoing distribution and sync jobs still use port capacity. |
| Multiple services on one server | The selected bandwidth is shared by workloads on that dedicated server | Account for concurrent traffic from websites, VMs, downloads and backups. |
| Measured application throughput | A port tier does not guarantee the same throughput on every route | Check receiving-end bandwidth, network routes, concurrent connections and application capacity. |
Monthly data transfer shows the total moved over time, but does not reveal the speed needed during busy periods. Review peak measurements from existing workloads and note when downloads, image updates and backups overlap.
Synchronisation and backups also consume bandwidth. When user traffic approaches the selected port speed, plan capacity by scheduling jobs, limiting background transfer rates or choosing another tier—not by looking at foreground requests alone.
Each server includes 1 dedicated IPv4 address. Additional addresses are billed individually according to the quantity selected, at $2 each per month, with up to 255 available. The included address does not count toward the additional-address limit.
Included in the monthly server price.
$2 each per month, billed individually.
1 included + 255 additional.
After payment and delivery, find the addresses and credentials in the server details in the control panel. Use SSH for Linux, FreeBSD and Proxmox VE, and RDP for Windows. If multiple addresses are configured, both connection methods use the first address in the list.
Additional address quantity and bandwidth tier are selected separately. Adding IPv4 addresses does not increase port speed or change the unmetered billing model. Current availability is shown in the control panel.
Dedicated addresses help distinguish service entry points. Base the address count on actual workloads rather than the maximum available, and plan address allocation, service bindings, firewall rules and access checks together.
Assign dedicated IPv4 addresses to different VMs to separate host management from guest workloads. Use the first address for the host's initial connection, and document the remaining addresses against their VMs and services.
Proxmox VE address planning also depends on bridge and guest network configuration. Adding addresses alone does not configure the guest operating systems.
Track host and guest addresses separatelyAllocate addresses by site or site group, and maintain a mapping between domains, addresses and service processes. Whether each site needs its own dedicated address depends on application bindings and isolation requirements.
After pointing DNS records to an address, check listener bindings, certificates and access rules to ensure the service is ready to receive requests.
Check domain and service bindingsMap APIs, downloads and other services to different addresses to identify entry points, manage access controls and investigate logs. Keep each address's purpose, owner and service name in the workload inventory.
Separate addresses do not isolate server resources. Services on the same dedicated server still share CPU, memory, storage and bandwidth, so plan their combined usage.
IP separation is not resource isolationData centre locationTokyo, Japan
Dedicated IPv4 addresses and unmetered bandwidth are suitable for websites, APIs and file services serving users worldwide. Addresses help organise entry points; bandwidth determines concurrent transfer capacity. Assess each separately.
Small API responses and large file downloads have different network demands. Track concurrent requests, response sizes and peak throughput together. Request count alone does not determine a bandwidth tier, and a dedicated IP by itself does not determine access performance.
Downloads, media delivery and image synchronisation can use bandwidth continuously. Map live traffic and background transfers on the same timeline, check their combined peak and choose a port tier accordingly. Monthly data totals are not a measure of required speed.
User access routes, receiving networks and application design all affect real-world performance. This page describes port tiers and IP billing; port speed is not a guarantee of actual throughput across every region or connection.
The technical blog covers IP allocation and bandwidth by topic. Visit the article index to explore the two subjects below. This page focuses on network configuration details rather than system commands and step-by-step tutorials.
Build an address-purpose inventory for host management, VMs and website entry points, and check reverse DNS requirements during planning.
Compare the concurrent traffic patterns of websites, downloads, image sync and API services to assess 250 Mbps, 1 Gbps and 2 Gbps tiers.
Choose one bandwidth tier, then enter the number of additional IPv4 addresses required. Billing is in USD; available payment methods are listed on the configuration page.
Amount due = monthly total × number of months; monthly bandwidth and additional IPv4 charges are included in the monthly total.