onionvps

Solution

VPS for high-availability and multi-region failover

Cutter 8 · $34/moCutter 16 · $62/mo
Short answer

Real availability comes from independent failure domains, not from a bigger server. Three instances in three countries with different transit providers survive events that no single machine can. Budget for a load balancer or anycast entry point, synchronous replication within a region, and asynchronous replication across them — latency makes synchronous cross-region writes impractical.

What you need

Specification floor for high availability & failover
ResourceWhat you actually need
NodesThree minimum, in three jurisdictions
NetworkWireGuard mesh; anycast available in selected regions
DatabaseSynchronous within region, asynchronous across regions
DNSShort TTLs and health-checked failover records

Recommended plans

Cutter

Cutter 8

$ 34 /month
vCPU
4 × dedicated
RAM
8 GB
Storage
160 GB NVMe SSD
Transfer
10 TB
IPv4 / IPv6
1 / /64 routed
Configure
Cutter

Cutter 16

$ 62 /month
vCPU
6 × dedicated
RAM
16 GB
Storage
320 GB NVMe SSD
Transfer
15 TB
IPv4 / IPv6
1 / /64 routed
Configure
Clipper

Clipper 16

$ 92 /month
vCPU
8 × dedicated
RAM
16 GB
Storage
400 GB NVMe Gen4 SSD
Transfer
30 TB
IPv4 / IPv6
1 / /64 routed
Configure

Recommended locations

Location is usually the decision that matters most for this workload — either because latency dominates, or because jurisdiction does.

🇳🇱

Amsterdam

Netherlands 9 Eyes

🇩🇪

Frankfurt

Germany 14 Eyes

🇺🇸

Ashburn

United States 5 Eyes

🇸🇬

Singapore

Singapore No alliance

🇧🇷

São Paulo

Brazil No alliance

Why OnionVPS for this

  • Locations in 40+ countries and 8 regions make genuine geographic diversity practical.
  • Different transit mixes per region, so a single upstream outage cannot take everything.
  • Anycast-capable regions for a single entry IP that survives a region loss.
  • A published 99.99% SLA with credits per location, not an aggregate marketing figure.

How to set it up

  1. Pick three regions with independent transit

    Amsterdam, Ashburn and Singapore is the classic triangle.

  2. Build a private mesh

    WireGuard between all nodes, with the application listening only on the mesh.

  3. Replicate the database appropriately

    Synchronous within a region, asynchronous across; know your RPO.

  4. Health-check at the DNS layer

    Short TTLs plus a health-checked failover record, or anycast if available.

  5. Run a failure drill

    Kill a region on purpose, on a weekday, while you are watching.

Frequently asked questions

How many servers do I need for high availability?

Three is the practical minimum: two gives you a split-brain problem rather than a quorum. Put them in three separate failure domains — different countries, ideally different transit providers.

Does multi-region hosting reduce latency?

Only if you route users to their nearest region. Multi-region for availability and multi-region for latency are different designs that happen to share hardware.

What uptime should I expect from a single VPS?

Our SLA is 99.99% per instance, which is about 4.4 minutes of downtime a month. Anything beyond that requires redundancy you build yourself.