Fly.io Postgres cluster down for 3 days, no word from them about it

I think fly.io is pretty incredible but I can't help but feeling they're doomed to follow in heroku's footsteps (unclear if good or bad). They've built some pretty wild stuff and I can't help but wonder if they're overcooking the ocean instead of just solving problems for their users.

Durable and available storage are all they really need to draw me away from big cloud providers but this combined with their answer to S3 being "use S3 or run minio" means I'll never take them seriously.

This is a bad look folks, not sure how you can walk back days of silence and hiding threads. Just open an issue and talk to your users.

> use S3 or run minio

Is using Cloudflare R2 not an option?

At least I could rely on Heroku in production. I've wanted to give Fly.io a try but this gives me pause. I really do miss the Heroku DX whenever I'm putzing around with the increasing complexity of AWS.

For hobby projects - where I dare not touch AWS for fear of going bankrupt from a misconfigured service - I found the sweet spot to be Dokku on top of a Hetzner or Digital Ocean instance. It provides a Heroku like interface on top of cheap hosting, and is fine where you don't expect to scale very much.

Backblaze even has an s3 api these days.

Backblaze B2 is much older than Cloudflare's offering. But from what I remember, they didn't have any presence outside North America.

B2 used to only have its own slightly different B2 API, but now has compact with the s3 api.

As far as their offering, one should definitely understand that there are limitations and do their research.

They do have an EU Central region (see [1]) but "it is not possible to have multiple regions under one account" - you need an account in each region (although it seems you can maybe fudge around with groups to emulate multi-region access.)

[1] https://help.backblaze.com/hc/en-us/articles/360034798433-Ca...