Update - Databases have been provisioned and the custom feeds are completely back to normal. (03:52 UTC — Mar 11)
This is information about the database failure that happened on 2/20/25, which resulted in everyone’s data being completely erased due to no backups.
This was a complete failure on my part; I had no backup plan and was merely relying on a single DB instance to hold through. While there was no feasibility in my project being popular, I assumed that a failsafe would not be required. I was wrong. And I apologize for that.
To make sure that something like this never happens again, I have gotten two DB instances to replicate the data across the two, so in the event of one going down, the other can handle the data until the other one comes back up. I am working on a third just in case for more redundancy. Again, I apologize about all of this, but the service should be able to continue as normal.
Last updated: March 11, 2025 at 8:53 PM UTC