Geo-Replication Calculator
Size cross-region replication bandwidth, storage and transfer cost from a daily change rate and compression.
Inputs
Cross-region transfer is usually cheaper than internet egress but far from free.
Monthly Replication Cost
$448.80
Replica Storage Charge
$276.00
Inter-Region Transfer Charge
$172.80
Data Shipped per Day
96.00GB
Sustained Replication Bandwidth
26.67Mbps
Link Utilisation at Peak
16.0%
Data Stored Across All Regions
16,000.00GB
Catch-Up After the Outage
3.4 minutes
Step by step
Values used
Primary dataset = 4,000 GB; Replica regions = 3 regions; Data changed per day = 4 %; Compression achieved on the wire = 40 %; Replica storage price = 0.0230 USD/GB-month; Inter-region transfer price = 0.0200 USD/GB; Replication link capacity = 500 Mbps; Change-rate peak factor = 3 ×; Replication outage to recover from = 60 minutes
Geo-Replication
shipped per day = primary × daily change rate × (1 − compression); sustained Mbps = shipped × regions × 8,000 ÷ 86,400; catch-up = backlog ÷ (link capacity − sustained rate).
Monthly Replication Cost
= 448.80
Replica Storage Charge
= 276.00
Inter-Region Transfer Charge
= 172.80
Data Shipped per Day
= 96.00 GB
Sustained Replication Bandwidth
= 26.67 Mbps
Link Utilisation at Peak
= 16.0
How it works
Replication traffic tracks the change rate, not the dataset size, so a 4 TB store that churns 4% a day ships about 160 GB before compression. Each additional replica multiplies both the storage bill and the egress, and the link only recovers from an outage using the capacity left above the steady change rate — which is why a link at 90% utilisation never catches up. Sizing a replication link on average throughput guarantees permanent lag during the daily write peak, and lag is the same thing as data loss when the primary region fails. Inter-region transfer prices differ per region pair, so confirm the current rate with your provider.
Formula
Geo-Replication
shipped per day = primary × daily change rate × (1 − compression); sustained Mbps = shipped × regions × 8,000 ÷ 86,400; catch-up = backlog ÷ (link capacity − sustained rate).
- daily change rate
- Share of the dataset rewritten each day, which is what replicates
- compression
- Reduction achieved on the replication stream, not on stored data
- drain rate
- Link capacity left over above the sustained change rate
Frequently Asked Questions
How is Geo-Replication calculated?
shipped per day = primary × daily change rate × (1 − compression); sustained Mbps = shipped × regions × 8,000 ÷ 86,400; catch-up = backlog ÷ (link capacity − sustained rate). Replication traffic tracks the change rate, not the dataset size, so a 4 TB store that churns 4% a day ships about 160 GB before compression. Each additional replica multiplies both the storage bill and the egress, and the link only recovers from an outage using the capacity left above the steady change rate — which is why a link at 90% utilisation never catches up.
Why does Geo-Replication matter?
Sizing a replication link on average throughput guarantees permanent lag during the daily write peak, and lag is the same thing as data loss when the primary region fails. Inter-region transfer prices differ per region pair, so confirm the current rate with your provider.
What values do I need to enter?
This calculator takes 9 inputs: Primary dataset, Replica regions, Data changed per day, Compression achieved on the wire, Replica storage price, Inter-region transfer price, Replication link capacity, Change-rate peak factor, Replication outage to recover from. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
You might also need
- Edge Storage CalculatorCommonly used together
- Regional Traffic Distribution CalculatorCommonly used together
- Regional Failover CalculatorCommonly used together
- CDN Cache Hit Ratio CalculatorAlso in CDN, Edge & DNS
- Global Latency CalculatorAlso in CDN, Edge & DNS
- CDN Bandwidth CalculatorAlso in CDN, Edge & DNS