Infrastructure by Region, Not by Claim
Deploy in Amsterdam or New York with published benchmarks, transparent network design, and consistent infrastructure standards.
Amsterdam
- Europe region
- Optimized for EU traffic
- Benchmarks published
New York
- US East region
- Optimized for North America
- Benchmarks published
Control panel, API, virtualization stack, and pricing structure are consistent across all regions.
Why Location Impacts Performance
The distance between locations and the quality of our routes can have a big impact on the time it takes to transmit data. The length of the path in time is a major contributor to the overall time it takes to transmit data between locations.
A wide variety of stabilizing resources are located far upstream in several sectors of the system. The various modes of transport in the system tend to act so that in the unlikely event of a failure occurring in one sector, no other failure is critical. This diversity provides an added measure of reliability.
Traffic patterns between different regions are quite different than those within a region. The long haul nature of transatlantic routes between continents means that delays and network instability are much more common than in a local network.
Match your location to your users
Ideal for: EU users, UK, Nordics, and Central Europe. Low latency for Western European traffic.
Suitable for: US East Coast, Eastern Canada and other North American destinations. Our transatlantic fibre optic network gives you a reliable connection to major hubs in the US.
For regional locations: When do you consider a location a region? You have two regions and want to know where to place your workloads. Place your workloads in the region closest to your primary audience and then create a mirror in the second region for business continuity/disaster recovery.
Infra Policy
Regional Infrastructure Standards
- AMD EPYC processors
- Single-socket design
- DDR4/5 ECC memory
- KVM virtualization
- Independent kernel per VPS
- Low-density allocation
- Memory capped below theoretical limits
- Balanced CPU scheduling
- No overselling model
Nodes are not filled to maximum theoretical capacity. Reserved headroom exists to maintain consistent performance during peak load.
Network & IP Policy
Multi-homed network design
Network Design
- Multi-homed upstream providers
- Redundant transit paths
- ASN disclosed
- IPv6 status declared
IP Policy
- Outbound email rate limits
- Abuse monitoring
- IPv4 allocation review
- rDNS available
Reliability & Operational Policy
Redundancy, maintenance, and security
- N+1 power design
- Dual power feeds
- Generator backup
- Redundant network switching
- Region-specific maintenance windows
- Advance maintenance notifications
- Location-specific status page
- Incident communication process
- Hypervisor isolation
- Segmented management access
- VLAN support
- Firewall support
- Baseline network-level DDoS mitigation
Multi-Region & Expansion Strategy
Independent regional deployment and planned expansion
Multi-Region
Deploy independently in Amsterdam and New York.
- Separate IP ranges
- Identical API and provisioning stack
- Suitable for geo-redundant architectures
- Inter-region traffic travels over public internet
- Inter-region latency ranges published
Expansion
New regions are evaluated based on:
- Customer demand
- Upstream diversity
- Network quality
- Operational sustainability
Future deployments will follow the same low-density, benchmark publication, and transparency standards.
Common Questions
Questions.
Clear answers.
The following FAQ section provides answers to typical questions users have about regional deployment, infrastructure consistency, and operational policies.