Cloudflare cut transit traffic by replicating analytics later

Cloudflare reports a net 36 GB/s reduction in wide-area traffic for migrated analytics datasets by delaying replication. Instead of sending every raw event to two regions, producers send one copy; centralized processing samples and batches data before making the second copy. Both database regions still receive their required data. The saving depends on this pipeline’s sampling and improved compression, not simply eliminating redundancy.

Cloudflare · Oct 13, 2026

Why it matters

Reducing data before replication can preserve resilience while changing bandwidth economics.

More context

Read the failure-handling design alongside the savings. A surviving region accepts incoming traffic during an outage, and remote inserters catch up from retained buffers after inter-region connectivity recovers.

Keep in mind

The measured savings concern the migrated datasets, not every Cloudflare stream.

Original read