zlacker

The pattern here is clear: everyone loves the CDN, everyone worries about their track record shipping anything else. A database is the worst place to test whether that changes. CDN mistakes cost you cache misses. Database mistakes cost you data. The pricing model and EU story are genuinely compelling, but if the S3 compatibility timeline is any guide, I'd let this one run quietly for a year before trusting it with anything I can't afford to lose.

>>ruhith+(OP)
Any experience with their DNS? Asking for a friend ;) only problem I've seen so far is lack of DS record support.

>>jtwale+i5
I've been using their DNS (migrating away from Cloudflare) for over a year and I've found it solid. Good latency and fast propagation. Custom nameservers are easy to setup. Migrating from CF is easy too - just export your zonefile from CF and import it to Bunny and you're good to go.

>>kolp+Jl
Cool, thank you!

>>jtwale+i5
I've been using their DNS (and CDN) for a good while. Only positive experiences - fast & rock solid. I would start a new project with them again in future.

I've also tried some of their new more experimental stuff (magic containers, edge scripting) and it's much rougher, but the core product is very good imo.

I wish they'd focus more instead there tbh, there's plenty more that could be done in terms of core content delivery, without trying to enter other (very competitive & I think much more complicated) markets like serverless hosting.