I'd say the blame here is 80% Railway, 10% AI, and 10% the company not having its own disaster recovery solution regardless of using a service that claims to handle backups.
The industry trend of moving from hosting stuff on servers you control to these "cloud in a box in the cloud" things has led to many such issues across all sorts of providers. Here are a couple examples:
Google Cloud: https://www.itbrew.com/stories/2024...entally-deletes-australian-customer-s-account
Supabase: https://deepstrike.io/blog/hacking-thousands-of-misconfigured-supabase-instances-at-scale
But beyond that, you really need to not put all your eggs in one basket. Even with "traditional" server providers or cloud providers things can go wrong and it's super important to have backups at a separate provider. For example, when OVH had that big datacenter fire, a bunch of people lost their data because the backups were in the same datacenter. Not very smart!
The industry trend of moving from hosting stuff on servers you control to these "cloud in a box in the cloud" things has led to many such issues across all sorts of providers. Here are a couple examples:
Google Cloud: https://www.itbrew.com/stories/2024...entally-deletes-australian-customer-s-account
Supabase: https://deepstrike.io/blog/hacking-thousands-of-misconfigured-supabase-instances-at-scale
But beyond that, you really need to not put all your eggs in one basket. Even with "traditional" server providers or cloud providers things can go wrong and it's super important to have backups at a separate provider. For example, when OVH had that big datacenter fire, a bunch of people lost their data because the backups were in the same datacenter. Not very smart!