This is really important to me. I'm currently looking to move all sites I'm responsible for to carbon-neutral (ideally directly renewable-powered) infrastructure. Obviously speed, efficiency, and cache proximity to the user are super -important factors as Phil outlined above, so any research Netlify can produce on the impact of this on power efficiency would be incredibly useful. In the meantime, it would be really helpful if an estimate could be made available of approximately how much of Netlify's resources are provided by which providers, so that the energy sources used by those providers can be taken into account. (Or better still, if Netlify wanted to do the maths based on those figures and publish a total carbon estimate as a percentage of total power usage.)

When a site is deployed, is it pushed straight away to all your edge servers – so that each visitor will always get a fast page load from their nearest edge server? Or is it stored on a single node, and the edge cache filled on demand, as with a typical CDN (eg Cloudflare) – meaning requests for uncached resources (most requests for a low-trafic site) need to be fetched across the net for many/most visitors? Maybe this is in your docs or marketing somewhere but I didn't find a clear answer straight off. :-)