> My point was rather that I cannot imagine that a single VM that runs the low-latency service such as the proxy is also running any type of heavier weight serv

> My point was rather that I cannot imagine that a single VM that runs the low-latency service such as the proxy is also running any type of heavier weight services I encourage you to imagine harder then. Nearly all of the software is running bare metal and as I said it’s all replicated on each machine. So the same server is running the reverse proxy and the CDN and the Workers runtime and Cloudflare tunnels because the any cast routing they use intentionally means that every single inbound request always hits the nearest server which generally processes the entire request right on the machine and uses Unimog to distribute the requests within a data center [1] and Plurimog [2] to distribute load between data centers. I’ll repeat again - every server runs the proxy along with every other internal and external product and there’s no VMs or containers*. I’m not going to engage with the rest of your hypothesis that it’s not worth the effort until services are falling over or it’s the root cause for some tail latency since the team has indicated it clearly is worth their time and value to Cloudflare. [1] https://blog.cloudflare.com/unimog-cloudflares-edge-load-balancer/ https://blog.cloudflare.com/unimog-cloudflares-edge-load-bal... [2] https://blog.cloudflare.com/meet-traffic-manager/ https://blog.cloudflare.com/meet-traffic-manager/ * technically there are VMs but it’s not worth thinking about for this specific discussion since the VM is closer to being just like any other application. It’s not virtualizing the cloudflare software stack but just providing a layer of isolation.