I’m sorry to hear that.
That’s definitely something we need to work on. We have a status page, but it doesn’t include personalized information and not everybody is subscribing to its updates.
We care a lot about our user’s data. Unfortunately your volume fell between the cracks and the migration process wasn’t completed successfully when the server crashed and we migrated all volumes from it. Volumes are only as resilient as the drive they’re on, that’s a physical NVMe drive on a specific host, we do not offer redundancy automatically. Users are expected to implement their own redundancy (often that means running a PostgreSQL cluster with at least 2 nodes, other times it’s a SQLite database replicated with Litestream or LiteFS), this is harder with things that aren’t databases or don’t have built-in replication capabilities.
Still, I understand your decision. We’re going to adjust the next time this happens.