Presenter mode

Cloudflare (anycast edge & Unimog)

Full page · Paths

Walkthrough

Anycast to a nearby PoP

Same service IPs announced from many cities; BGP delivers the client to a nearby datacenter. Illustrative PoPs — not a city inventory.

Step 1 / 3
Anycast VIPClientPoP A (anycast)PoP B (anycast)Origin (proxied)

Cloudflare announces the same anycast service IPs from many cities. BGP chooses a nearby PoP for performance and naturally distributes attack traffic.

Walkthrough

In-PoP: ECMP → XDP → Unimog

Published in-PoP data path from the architecture/BPF and Unimog posts. Teaching roles — not a rack elevation.

Step 1 / 3
PoP routerEdge serverEdge serverXDP l4dropUnimogService (e.g. DNS)

Packets hit the PoP router; ECMP spreads a VIP across many edge servers (≥16 cited in the architecture post).

Walkthrough

Open peering at the edge (AS13335)

Peering policy themes: open peering, PeeringDB, PNI thresholds. Myriagon is a historical connected-networks milestone — not a live inventory.

Step 1 / 3
Peer / IXCloudflare edge (AS13335)AS13335CDN+DNS+WAF stack

Cloudflare publishes an open peering policy for AS13335: PeeringDB required, BCP-38 / IRR filtering expected, public IX via the peering portal, PNI when traffic thresholds motivate it.