Backup restores from Supabase can corrupt projects, a claim that surfaced in a Hacker News post. The dashboard error makes it plain: "Something went wrong while restoring your project. Your project's data is intact, but your project is inaccessible due to a restoration failure." [1]
What went wrong: Backups are described as potentially corrupt or unavailable, which means data loss and inaccessible projects for users. The thread compiles numerous reports from the Discord channels about restore failures, including paying customers, with messages piling up as responses lag or don’t come at all. [1]
Impact on users and support: This reads like a worst‑case scenario for managed cloud services. A single restore flaw can ripple through an entire project and shake trust in hosted databases, with real data loss and prolonged outages cited by complainants. [1]
Transparency demands: The post argues for clear communication when incidents occur and even suggests actions like disabling the restore function until recovery is assured. The expectation is that providers own incident timelines and share what happened to users’ data. [1]
Closing thought: The episode underscores that backup integrity and open incident reporting aren’t optional in hosted databases—they’re essential as teams rely more on managed services. [1]
References
Tell HN: Supabase database restore from backup corrupting projects
Reports indicate Supabase backups restoration corrupts projects; errors show; backups may be corrupt; data loss; calls for action and transparency.
View source