[viraptor]

This is all cool, but:

> BunnyCDN was pretty consistently returning my blog post a few hundred milliseconds faster than Cloudflare

Makes me think that author's CF was misconfigured. Unless you're in a zone with really bad interconnects, like Brazil, or African locations, multiple hundreds of milliseconds shouldn't be possible as the baseline, much less as the difference in the saved latency. (I'm assuming the author talks about a single blog post request)

So, don't expect a 100ms+ improvement.

[fspoettel]

There is a long-standing dispute between Cloudflare and Germany's biggest ISP, Telekom, which results in terrible peering for Cloudflare free traffic for Telekom customers here. Sites on the Cloudflare Pro plan are not affected by this somehow.

If the author is a Telekom customer, then they would absolutely see 100ms+ improvements.

[oynqr]

DTAG is just terrible. Having a whitelist of allowed mail providers they deal with? Check. Abusing peering to squeeze more cash? Check. Advocating for censorship on the Internet? Check.

[lwde]

https://netzbremse.de/

[VladVladikoff]

>Sites on the Cloudflare Pro plan are not affected by this somehow.

This has been my general experience with cloudflare. Their free plan is abysmally slow. And even their Pro plans add significant (30ms+) overhead to requests.

[DeepSeaTortoise]

Seems like they upgraded their abysmal 40Gbps peering, tho.

https://www.peeringdb.com/net/196

[MrJohz]

Hi, author here, that could absolutely be the case for me. I'll add a note about that when I next get to a computer.

[MrJohz]

And, looking again, the issue seems to no longer be there, and both CDNs produce results that are within a few tens of milliseconds from each other.

[re-thc]

> Sites on the Cloudflare Pro plan are not affected by this somehow.

i.e. Cloudflare is paying and needs you (the customer) to cover the cost.

[MortyWaves]

I was surprised by that too: typically I’ve only seen such high latency on Netlify based sites which exclusively uses aws-east for the whole world.

[arnorhs]

This is not accurate. I do not know the details but netlify served things from a CDN by default if you set things up correctly with a CNAME entry in your DNS record.

People often misconfigure things by pointing their domain to netlify's IP with an A entry, but this is a user problem, not a netlify problem.

I'm sure their builds/functions run in a single region but not static files

[iJohnDoe]

Based on my limited knowledge, you have to point your root domain (e.g. example.com) to their IP address because it’s an A record.

For the a CNAME record (e.g. wwww) it can be pointed to their CDN.

I think if you use Netlify DNS for your domain, then you can point A records to their CDN because it’s an alias at that point. Like, A record aliases on AWS Route53.

[MortyWaves]

I found all of Netlify particularly confusing and honestly a bit scary. Now I’m on CF and it couldn’t be simpler.

[MortyWaves]

The Netlify docs are quite bad so I can see this happening. Also, the Netlify Functions ate locked to one AWS region too.

[salviati]

In my experience bunny has lower latency than cloudflare. I can confirm.

[throwaway63467]

Hundreds of milliseconds though? Seems highly doubtful, Cloudflare has latency in the range of 10-20 ms for most metropolitan areas, that they would that ten times that much for returning a blog post seems unlikely unless caching or other things are misconfigured.

[bobmcnamara]

Cloudflare routes most Arabian traffic through US or Europe first.

[koakuma-chan]

My browser shows 250ms of waiting when accessing this article.