Interesting approach. So Fastly is offloading the full routing table to their carriers&#x27; router(s). That&#x27;s because routers that can hold full BGP tables are expensive to purchase and maintain. But to retain some form of control, they&#x27;re terminating eBGP at the switch and using iBGP to disseminate (inject) the providers&#x27; route (next hop).<p>I feel (I don&#x27;t have direct experience with this setup) like they&#x27;re just offloading some compute power (therefore cost) to the hosts. So the cost is automatically spread out across their relatively massive edge nodes. A line showing a router plus support costing $100,000 looks bad in expenditures vs showing a server plus integrated routing showing $2500.<p>I&#x27;m curious about how this impacts Varnish considering how table look ups can be bus-expensive during odd route changes&#x2F;flaps (storms). %sys must go through the roof as a result.