I'm sure they have multiple data centers in each location. Especially if it's a high traffic interconnect.

Netlify is also like this. You have to be in their "Enterprise" tier which they do not advertise a price for (Custom pricing).

https://docs.netlify.com/manage/monitoring/log-drains

It has benefits to use them, but yes they are not a CDN in a traditional sense, they do much more.

So since magecdn is built on top of Cloudflare, how do they guarantee low latency?

> With a traditional CDN, if you set cache-control header, you can be sure that your files will be cached on the edge according to the header.

I’ve got a decade and a half of experience with Fastly, Akamai, and CloudFlare serving 100s of gigabits/sec of traffic. I can assure you this is not true at all. Cache-Hit ratio and Cache-Hit/Miss access time are highly situational and cache-control is best effort for every provider. No CDN will guarantee these values.

> With a traditional CDN, you can pick a hostname (Origin) and the file will be fetched from there. So, you can run a CDN directly over, say, a S3 Cloud bucket. Cloudflare works at your website domain level, and doing this is something like that is not possible.

“Cloudflare works at your website domain level.” This is poorly written, confusing, and fortunately, not at all true. You can CNAME i.example.com to an S3 bucket hostname and use i.example.com links on example.com. This also comes with some http/1.1 pipelining advantages and is a preferable way to architect.

<begins describing all the things that make it a CDN>

The fact that certain features are not available on the free tier, that infrequently-accessed content is evicted from the cache sooner than one would like, and having other minor nits doesn't make it not a CDN.

- workers (a sort of lambda on edge) - page (a sort of fastifly) - R2 (S3 compliant storage) - kv (a database) - load balancing (an elastic LB) - an entire set of cybersecurity services

Then lists why it's a CDN.