We are back online with the database from this morning 15.08.2025 at 05:20 CEST.
-
We are back online with the database from this morning 15.08.2025 at 05:20 CEST. Every local toot posted between this time and 13:45 CEST is lost so are the two registrations we saw today. Remote toots should catch up the next few hours.
The lost followings from our users to users from mastodon.social should be recovered in most cases. Sadly users from mastodon.social following our users are lost because the domain deletion process removes every existing relation between accounts. #mastoadmin
-
We are back online with the database from this morning 15.08.2025 at 05:20 CEST. Every local toot posted between this time and 13:45 CEST is lost so are the two registrations we saw today. Remote toots should catch up the next few hours.
The lost followings from our users to users from mastodon.social should be recovered in most cases. Sadly users from mastodon.social following our users are lost because the domain deletion process removes every existing relation between accounts. #mastoadmin
We are sorry this happend. As we mentioned we started a process to delete old cached instances that where offline for more than a year. Sadly in one line of over 18.000 lines was a mistake we hadn't expected. We checked the domains before but somehow didn't catch this. We currently have no explanation why exactly this single line was wrong. #mastoadmin
-
We are sorry this happend. As we mentioned we started a process to delete old cached instances that where offline for more than a year. Sadly in one line of over 18.000 lines was a mistake we hadn't expected. We checked the domains before but somehow didn't catch this. We currently have no explanation why exactly this single line was wrong. #mastoadmin
We also discussed a manual fix for the following relations by manually altering the database, but this would have cost us many hours more and we couldn't guarantee that it would work at all (and not causing new issues). Therefore we decided to use our daily backups to fix this as fast as possible. We will evaluate if we can increase the number of backups per day in the future. #mastoadmin
-
We also discussed a manual fix for the following relations by manually altering the database, but this would have cost us many hours more and we couldn't guarantee that it would work at all (and not causing new issues). Therefore we decided to use our daily backups to fix this as fast as possible. We will evaluate if we can increase the number of backups per day in the future. #mastoadmin
-
If you try to wrap you mind around how something like this could happen, please remember this is a project we run in our spare time. We aim for a good reliable service but shit like this can always happen.
#mastoadmin@ordnung@chaos.social Thanks for everything you do! You rock!