edgeacademyCUSTOMER ENGINEERING
MODULE 03 · LESSON 2 OF 5

Routing, BGP, and anycast without magical thinking

12 min read · Sources linked below

Theory and industry practice are explained below. Cloudflare-specific behavior links to official documentation. Customer examples are hypothetical.

Learning objectives

  • Separate route learning from packet forwarding
  • Explain BGP policy and anycast
  • Interpret traceroute cautiously

The mental model

Routing decides where packets go next. Inside a network, routes may come from configuration or routing protocols. Between autonomous systems on the Internet, BGP exchanges reachability information and applies policy. It is not a universal shortest-distance algorithm. Operators care about commercial relationships, preferred paths, and reachability as well as performance. Anycast uses this routing system to make the same service prefix reachable at multiple locations. A route change can therefore change which service location receives traffic. For customers, routing is part of reliability and latency, but it cannot repair every application problem. An available path to an address does not prove the service behind it is healthy.

How it works

BGP advertises prefixes with attributes such as AS paths, allowing networks to choose and propagate routes according to policy. The control plane determines reachability information; the data plane forwards packets using installed decisions. A healthy session does not automatically mean every required prefix is advertised or accepted. Inspect the specific route, its next hop, filters, and propagation rather than stopping at session status.

Anycast deployments advertise a shared prefix from multiple sites. Networks select paths based on their own policies and topology, so a nearby physical site is not guaranteed to receive a given client's traffic. During failure, route withdrawal and convergence can redirect new traffic, but existing connections and application state still need consideration. Ask what the service does when traffic shifts and whether state is local or externally available. For troubleshooting, compare affected and unaffected source networks, route visibility, timing, and application evidence. Traceroute is useful but imperfect: intermediate routers may rate-limit or suppress probe responses, and forward and return paths can differ. A silent intermediate hop does not by itself prove packet loss for application traffic.

Applied example · hypothetical

Hypothetical example: only customers on one ISP experience connection failures after a route change. The origin is healthy and other networks succeed. You gather affected source networks, timestamps, destination prefixes, and transport outcomes. A route-policy problem becomes more plausible than an application-wide regression. Conversely, if every network reaches the edge and receives the same application error, route visibility alone will not explain the failure. The disciplined approach compares network cohorts and preserves enough detail for the routing team to investigate the exact path and prefix.

In a customer engagement

For a Cloudflare customer, describe anycast as a routing-based availability and distribution mechanism with operational tradeoffs. Ask whether the issue follows an ISP, geography, address family, or destination prefix. Bring precise evidence to network specialists. Avoid promising that anycast always chooses the physically closest location or that route convergence preserves every active connection without interruption.

Interview relevance

A strong networking answer separates control-plane reachability from data-plane forwarding and application health. You do not need to recite every BGP attribute to show senior judgment. Explain the routing decision, the uncertainty introduced by policy, and the evidence that would distinguish a prefix problem from an application failure.

Common mistakes

  • Equating BGP session up with every prefix reachable
  • Treating geographic proximity as guaranteed routing
  • Calling every silent traceroute hop an outage

Key terminology

BGP — The interdomain routing protocol used to exchange prefix reachability and routing attributes.

Autonomous system — A network or group of networks operated under a common routing policy and identified by an ASN.

Control plane — The mechanisms that learn and select forwarding information.

Explain it without the page

  • What evidence distinguishes a prefix-specific issue from a global incident?
  • How might a route change affect stateful connections?

Further reading

Sources explain the underlying concepts; examples and practice answers are original course material. Recheck current limits and plan eligibility before a real proposal.