To op­ti­mize the per­for­mance met­rics of this blog, I re­lied on Ama­zon CloudFront to serve the as­sets,1 and Route 53 for the geo-aware DNS2 to di­rect read­ers to the clos­est host serv­ing the con­tent. But Route 53 is ex­pen­sive: US$0.50 per zone per month, US$0.70 per mil­lion ge­olo­ca­tion queries, and US$0.75 per healthcheck per month[1], plus US$1 per month for the KMS key[2] needed to sign zones with DNSSEC. When I dis­cov­ered that Bunny DNS is al­most free[3] for up to 500 do­mains and fea­tures script­able an­swers, I made the jump! Plus, it’s a Eu­ro­pean com­pany based in Slovenia.

Bunny.net[4] started as BunnyCDN in 2015[5]. They added IPv6 sup­port in 2017[6]. Switch­ing was un­event­ful. I don’t bring a cus­tom do­main: I serve the con­tent from the b-cdn.net do­main. As I de­pend on con­tent ne­go­ti­a­tion to serve AVIF and WebP im­ages[7], I con­fig­ure the CDN to cache each im­age for­mat sep­arately[8].